BF project-analyzer-generate-doc
Java Maven multi-module project documentation generator. Supports MyBatis SQL mapping, Maven dependency analysis, generates L3(file-level) to L2(module-level) to L1(project-level) hierarchical docs. Features task monitoring, auto-retry, checkpoint resume, and health checks.
As a process F 41/100 · Will not run — References files that are not bundled: references/l3-template.md, references/l2-template.md, references/l1-template.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityCHANGELOG-v2.1.4.md:15Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ❌ Removed all references to "elevated permissions" or privilege escalation
-
low Dangerous commands
cmd-execpolicy-bypasspackage.json:22Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)"generate-l3": "powershell -ExecutionPolicy Bypass -File scripts/gene…ps1",
quoted -
low Risky intent
intent-offensive-securitySECURITY_FIXES.md:72Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Rationale**: Privilege escalation attempts are security risks and outside the scope of documentation generation.
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5238 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/l3-template.md - warning
missing-refreference to a missing file: references/l2-template.md - warning
missing-refreference to a missing file: references/l1-template.md
Process rating: all ten parameters 41/100
- 0Tools and files. 3 referenced file(s) missing: references/l3-template.md, references/l2-template.md, references/l1-template.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 5238 tokens
- 100Steps. 55 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
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
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 274: enough signal without eating the budget
- +4Structure: 44 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (37 code blocks)
- +4Reference files are cited in the instructions (5 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.