BF developer-onboarding-doc
Write a developer onboarding document for a service, codebase, or team. Use when asked to write a developer guide, service README, onboarding doc for a new engineer, codebase orientation, or getting-started guide for a technical team. Produces a structured doc covering service overview, architecture, local setup, key patterns, testing, deployment, and who to ask for what.
Write a developer onboarding document for a service, codebase, or team.
As a process F 55/100 · Will not run — References files that are not bundled: docs/decisions/, docs/api/, docs/runbooks/
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvSKILL.md:114Reads a .env filecp .env.example .env
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: docs/decisions/ - warning
missing-refreference to a missing file: docs/api/ - warning
missing-refreference to a missing file: docs/runbooks/ - warning
missing-refreference to a missing file: docs/cicd/ - warning
missing-refreference to a missing file: docs/team/ - note
frontmatter-keyunknown frontmatter key "homepage" - note
edit-residuethe text marks something as outdated (lines 82): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 55/100
- 0Tools and files. 5 referenced file(s) missing: docs/decisions/, docs/api/, docs/runbooks/
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 14 mutating operations with no state check
- 60Steps. 73 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2801 tokens
- 100Progress reporting. Reports progress
- low 15 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)
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 374: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 73 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.