SKILLEMALL.ai
GitHub ↗ RU Sign in

DC update-docs

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.

NeoLabHQ/context-engineering-kit Agent Skills author: NeoLabHQ 1 file body ≈ 5 594 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents.

As a process C 50/100 · Has gaps — References files that are not bundled: docs/api/, docs/guides/, CONTRIBUTING.md

ProcedureWriting and documentstype 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
D
77/100
safety, quality, tests
Safety 60%
100
Quality 40%
43
Run on models
none yet
Process rating
C
50/100
Has gaps
References files that are not bundled: docs/api/, docs/guides/, CONTRIBUTING.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: update-docs (NeoLabHQ/context-engineering-kit)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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")
  • warning body-long SKILL.md body ≈ 5594 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: docs/api/
  • warning missing-ref reference to a missing file: docs/guides/
  • warning missing-ref reference to a missing file: CONTRIBUTING.md
  • warning missing-ref reference to a missing file: ../docs/

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: docs/api/, docs/guides/, CONTRIBUTING.md
  • 0Tools and files. 4 referenced file(s) missing: docs/api/, docs/guides/, CONTRIBUTING.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5594 tokens
  • 85Steps. 162 steps, 3 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • low 14 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (6 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)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -215 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 169: enough signal without eating the budget
  • +4Structure: 37 headings
  • +3Step-by-step instructions: 162 items
  • +4Has examples (14 code blocks)

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