BC second-brain-metrics
Record a dated snapshot of the vault's health numbers and compare against previous snapshots so trends are visible. Use this skill for a monthly or quarterly check, when the user asks whether the vault is improving, or asks to track its numbers over time. Do NOT use for a one-off graph analysis, which is second-brain-graph, or for structural repairs.
Record a dated snapshot of the vault's health numbers and compare against previous snapshots so trends are visible.
As a process C 53/100 · Has gaps — References files that are not bundled: scripts/vault_stats.py, scripts/link_check.py
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 · 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-refreference to a missing file: scripts/vault_stats.py - warning
missing-refreference to a missing file: scripts/link_check.py
Process rating: all ten parameters 53/100
- 0Tools and files. 2 referenced file(s) missing: scripts/vault_stats.py, scripts/link_check.py
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 5 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 321 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
- +5Description has no quoted example phrases that should trigger the skill
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 352: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 5 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.