AD ooxml-lookup
Query the ECMA-376 (Office Open XML) schema offline to find out what is legal in a .docx, .xlsx or .pptx file. Use when writing, reading or debugging OOXML markup by hand: what may go inside an element and in what order, what attributes it takes, what values those attributes accept, which namespace or prefix to write, and what the difference is between the Transitional and Strict profiles. Also resolves a schema validation error into "here is what would have been legal at that position". Covers wordprocessingml, spreadsheetml, presentationml, drawingml and vml. Does NOT validate files (that is ooxml-validate), does not generate documents, and has no specification prose, behaviour notes or semantic search — it answers from the XSD schema graph only.
Query the ECMA-376 (Office Open XML) schema offline to find out what is legal in a .docx, .xlsx or .pptx file. Use when writing, reading or debugging OOXML…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1693 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -35 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 758: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.