SKILLEMALL.ai

AC docx

Read, create, or edit Microsoft Word .docx files — extract/summarize text and tables, generate reports/letters/memos with headings, tables, images, TOC and page numbers, do find-and-replace, or apply tracked changes (redlines) and comments. Use whenever the user has a .docx or wants a Word deliverable. Not for PDF, .xlsx, .pptx, or Google Docs.

HKUDS/DeepTutor Agent Skills author: HKUDS Apache-2.0 1 file body ≈ 2 435 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Read, create, or edit Microsoft Word .docx files — extract/summarize text and tables, generate reports/letters/memos with headings, tables, images, TOC and…

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorWordExcelPowerPointGoogle DocsData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "requires"
    • note edit-residue the text marks something as outdated (lines 139): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 4 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 100Steps. 14 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2435 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 346: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 14 items
    • +4Has examples (10 code blocks)

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