SKILLEMALL.ai
GitHub ↗ RU Sign in

AB docx-operational-integrity-check

Reviews whether an AI-assisted Word or DOCX workflow preserves the original, tracked changes, comments, numbering, sections, edit identity, document structure, save/verify cycles, and professional review. Use before relying on a DOCX that an AI tool read, edited, redlined, reformatted, or generated. Do not use as a legal review of the document's substance or as proof that every rendering defect was detected.

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

Reviews whether an AI-assisted Word or DOCX workflow preserves the original, tracked changes, comments, numbering, sections, edit identity, document…

As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting

ProcedureWordAI and agentsLegalResearchtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
B
71/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Consistency w 8
40
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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 71/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 40Consistency. Frontmatter name (docx-operational-integrity-check) differs from the folder (docx-operational-integrity-check-adrian-lerer)
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 20 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Execution cost. Instruction body is 838 tokens
    • 100Running it twice. Mutating operations check current state

    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
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 411: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 20 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

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