SKILLEMALL.ai

BD code-documentation

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.

bytedance/deer-flow Agent Skills author: bytedance MIT 1 file body ≈ 3 328 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides.

As a process D 43/100 · Unfinished process — References files that are not bundled: link

GeneratorWriting and documentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
D
43/100
Unfinished process
References files that are not bundled: link
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

How to improve

  1. 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 missing-ref reference to a missing file: link

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: link
  • 0Tools and files. 1 referenced file(s) missing: link
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 4 mutating operations with no state check
  • 60Steps. 53 steps, 4 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3328 tokens
  • 100Progress reporting. Reports progress

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 465: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 53 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)

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