SKILLEMALL.ai

CF office-docx

Create, read, edit, and validate Word documents (.docx).

The skillemall take

Promises to create, read, edit, and validate Word documents with tables and formatting. One instruction file at 1436 tokens, no critical issues found. Quality score 81, safety 100. Process score 33 is low, but that's likely just simple logic without complex workflows.

No broken references or unsafe patterns detected. Supports multiple platforms including Claude and Cursor. Uses bundled LibreOffice by default—sensible for automation. Downside: no actual model runs logged, sandbox untested. Install if you need basic docx operations without complications.

deepseek-ai/deepseek-harness Agent Skills author: deepseek-ai MIT 1 file body ≈ 966 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Create, read, edit, and validate Word documents (.docx).

As a process F 28/100 · No process to follow — weak spots: steps, result and completion, when it triggers

AnalyzerWordSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
F
28/100
No process to follow
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 28/100

  • 0Steps. Prose only: no discrete steps
  • 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. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 966 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)
  • +3Description length 56: 120–800 characters recommended
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 3 headings
  • +4Has examples (1 code blocks)

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