AC librarian
Ingest any media link or file into a personal Obsidian library. Use when a user drops a URL (YouTube, article, tweet, podcast, PDF, image) or file and wants to save it, understand it, or do something creative with it (write a script, remix it, extract a framework). The Librarian ingests, tags, asks intent if unclear, and stores a structured note in the library/ folder. Triggers on: any URL drop, "save this", "add this to my library", "I want to make my own version of this", "file this", or similar. Does NOT write scripts or generate content — that's downstream agents (Screenwriter, Remixer). The Librarian only ingests, tags, and stores.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Ingest any media link or file into a personal Obsidian library. Us… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (librarian) differs from the folder (digital-librarian)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 26 steps
- 100Execution cost. Instruction body is 770 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 644: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.