Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

verify-docs

Estrelas0

Forks1

Atualizado30 de março de 2026 às 11:01

Verify generated Office documents (DOCX, PPTX, XLSX, ODT, ODP, ODS, HTML) are valid and open correctly. Use when: user asks to verify generated files, check document output quality, validate Office files, run the verification loop, test generated documents, check if files open in Keynote/Word/Numbers, or after changing any generator code (docx_generator, pptx_generator, xlsx_generator, odt_generator, odp_generator, ods_generator, html_generator). Also use when user says "verify", "check the files", "do they open", "run verification", or "test the output".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

sunholo-data

sunholo-data/ailang-parse

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	verify-docs
description	Verify generated Office documents (DOCX, PPTX, XLSX, ODT, ODP, ODS, HTML) are valid and open correctly. Use when: user asks to verify generated files, check document output quality, validate Office files, run the verification loop, test generated documents, check if files open in Keynote/Word/Numbers, or after changing any generator code (docx_generator, pptx_generator, xlsx_generator, odt_generator, odp_generator, ods_generator, html_generator). Also use when user says "verify", "check the files", "do they open", "run verification", or "test the output".
user-invokable	true

Verify Generated Documents

Run the document generation verification loop to check that generated Office files are structurally valid, open in Python libraries, and roundtrip through AILANG Parse correctly.

What This Does

Three levels of verification on all files in data/examples/:

L1 Structure — ZIP well-formedness, required entries present, XML validity
L2 Library — python-docx, python-pptx, openpyxl open without errors
L4 Roundtrip — Parse through AILANG Parse, verify blocks are preserved

Usage

Run the verification script:

uv run --with python-pptx --with openpyxl --with python-docx benchmarks/verify_generated.py

With Regeneration

If generator code has changed, regenerate demo files first, then verify:

bash .claude/skills/verify-docs/scripts/regen_and_verify.sh

Quick Verify Only (no regen)

bash .claude/skills/verify-docs/scripts/verify_only.sh

Instructions

When this skill is invoked:

Check if the user passed --regen or asked to regenerate files
If regenerating: run scripts/regen_and_verify.sh which generates fresh demo files across all formats then verifies
If verify only: run scripts/verify_only.sh
Report results clearly — highlight any FAIL or WARN items
If there are failures, investigate the specific XML/structure issue and suggest fixes
After fixing generator code, re-run verification to confirm the fix

Interpreting Results

PASS — File is valid at that level
WARN — Minor issue (e.g., ODF mimetype compression — AILANG stdlib limitation, not fixable by us)
FAIL — File won't open correctly in target applications. Needs a fix in the generator code.

Known Limitations

ODF files (ODT/ODP/ODS) have compressed mimetype entries — this is an AILANG createArchive limitation (no store/no-compress flag). Shows as WARN, not FAIL.
Level 3 (native app smoke test) is manual — open files in Keynote/Word/Numbers to verify visually.

Mais deste repositório

mesmo repositório

add-format

sunholo-data/ailang-parse

End-to-end checklist for adding a new input or output format to AILANG Parse (docparse). Use when the user says 'add support for X format', 'wire up a new parser', 'add .foo format', 'add a parser for .bar', 'support .baz files', 'ship format X', 'can we parse .qux', 'new format rollout', or mentions a file extension that isn't yet supported (e.g. 'what about RTF', 'add Jupyter notebooks'). Covers parser code, ailang.toml exports, WASM demo, vendor-wasm-packages.sh, homepage, workbench, all format-list surfaces across the docs site, SDK READMEs, release tag, registry publish, and the ailang messages send docparse downstream notification. Use even when only part of this is requested — the skill tells you which surfaces you'd otherwise miss.

2026-04-140

landing-page

sunholo-data/ailang-parse

Create a new AILANG Parse documentation/landing page targeting a specific keyword or topic. Use when user says 'new landing page', 'new page for X', 'create a page about X', 'landing page for keyword X', or wants to add a documentation page to the docs/ site. Also use when the user references long-tail keywords, SEO pages, or competitor comparison pages.

2026-04-070

benchmark

sunholo-data/ailang-parse

Run OfficeDocBench evaluation and refresh benchmark scores across the AILANG Parse website. Use when the user says 'run benchmarks', 'rerun the benchmark', 'refresh benchmark numbers', 'update bench scores', 'regenerate summary.json', mentions OfficeDocBench, asks to evaluate parsers, asks why scores are out of sync on the docs, or after any change to docparse/services/*.ail or benchmarks/officedocbench/scoring.py — even if they don't explicitly say 'benchmark'. Also use after editing any AILANG parser to verify no regression.

2026-04-070

audit-design-docs

sunholo-data/ailang-parse

Audit the design_docs/ folder structure against the current project version. Use when user says 'audit design docs', 'check design docs', 'are design docs organized', 'verify design doc placement', 'tidy design docs', or asks about misplaced/stale design documents. Also use when the user asks to reorganize planned vs implemented docs, or after a version bump.

2026-04-030

fix-parser-gap

sunholo-data/ailang-parse

Fix a parser gap identified in the spec coverage audit. Use when user says 'fix a gap', 'implement X parsing', 'improve parser coverage', 'close a gap', 'next P1', or references a specific ECMA-376 spec section like '§17.9'. Also use when the user asks to improve DOCX/XLSX/PPTX parsing quality, add support for a missing Office feature, or mentions numbering, styles, hyperlinks, formatting, fields, merged cells, equations, or speaker notes in the context of parser improvement.

2026-04-030

name	verify-docs
description	Verify generated Office documents (DOCX, PPTX, XLSX, ODT, ODP, ODS, HTML) are valid and open correctly. Use when: user asks to verify generated files, check document output quality, validate Office files, run the verification loop, test generated documents, check if files open in Keynote/Word/Numbers, or after changing any generator code (docx_generator, pptx_generator, xlsx_generator, odt_generator, odp_generator, ods_generator, html_generator). Also use when user says "verify", "check the files", "do they open", "run verification", or "test the output".
user-invokable	true

Verify Generated Documents

Run the document generation verification loop to check that generated Office files are structurally valid, open in Python libraries, and roundtrip through AILANG Parse correctly.

What This Does

Three levels of verification on all files in data/examples/:

L1 Structure — ZIP well-formedness, required entries present, XML validity
L2 Library — python-docx, python-pptx, openpyxl open without errors
L4 Roundtrip — Parse through AILANG Parse, verify blocks are preserved

Usage

Run the verification script:

uv run --with python-pptx --with openpyxl --with python-docx benchmarks/verify_generated.py

With Regeneration

If generator code has changed, regenerate demo files first, then verify:

bash .claude/skills/verify-docs/scripts/regen_and_verify.sh

Quick Verify Only (no regen)

bash .claude/skills/verify-docs/scripts/verify_only.sh

Instructions

When this skill is invoked:

Check if the user passed --regen or asked to regenerate files
If regenerating: run scripts/regen_and_verify.sh which generates fresh demo files across all formats then verifies
If verify only: run scripts/verify_only.sh
Report results clearly — highlight any FAIL or WARN items
If there are failures, investigate the specific XML/structure issue and suggest fixes
After fixing generator code, re-run verification to confirm the fix

Interpreting Results

PASS — File is valid at that level
WARN — Minor issue (e.g., ODF mimetype compression — AILANG stdlib limitation, not fixable by us)
FAIL — File won't open correctly in target applications. Needs a fix in the generator code.

Known Limitations

ODF files (ODT/ODP/ODS) have compressed mimetype entries — this is an AILANG createArchive limitation (no store/no-compress flag). Shows as WARN, not FAIL.
Level 3 (native app smoke test) is manual — open files in Keynote/Word/Numbers to verify visually.