AB second-brain-ingest
Turn raw source material in a second-brain vault into linked wiki pages: read the source, split it into concepts and entities, write or update pages, connect them to existing pages, and record the run in the log. Use this skill whenever the user drops a file into raw/, pastes an article, transcript or PDF and asks to add it to the vault, says "ingest this", "add this to my second brain", "process raw", or asks to catch up on unprocessed sources, even if they do not name the ingest command. Do NOT use for answering questions from an existing vault, for linting or repairing pages, or for editing notes the user wrote by hand.
Turn raw source material in a second-brain vault into linked wiki pages: read the source, split it into concepts and entities, write or update pages, connect…
As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, failures and branches
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 73/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 7 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 698 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 630: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 7 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.