SKILLEMALL.ai

AB docx-processing-superdoc

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface. Use when the user asks to read, search, modify, comment, or review changes in .docx files.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 3 files body ≈ 1 292 tokens Open the sourcegithub.com↗ analyzed 89 min ago

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface.

As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice

IntegrationWordtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 5, 134, 136, 140): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 65/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 14 mutating operations with no state check
    • 40Consistency. Frontmatter name (docx-processing-superdoc) differs from the folder (word-editor-superdoc)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 35 steps
    • 100Execution cost. Instruction body is 1292 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (5 tags): a typed call is more reliable

    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)
    • +2Single-language instructions
    • +3Description length 176: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 35 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.