AF deepvista-recipe-analyze-notes
Recipe: Analyze, summarize, and find patterns across notes in your DeepVista knowledge base. TRIGGER when: user asks to analyze notes, summarize notes, find patterns or themes in notes, review notes, get insights from notes, "what have I been thinking about", "what are common topics in my notes", "synthesize my notes", or any request to make sense of multiple notes at once. DO NOT TRIGGER when: user wants to create, update, or delete a single note (use deepvista-notes instead); or when the request is about a specific known note by ID.
As a process F 52/100 · Will not run — References files that are not bundled: ../deepvista-shared/SKILL.md, ../deepvista-vistabase/SKILL.md, ../deepvista-notes/SKILL.md
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../deepvista-shared/SKILL.md - warning
missing-refreference to a missing file: ../deepvista-vistabase/SKILL.md - warning
missing-refreference to a missing file: ../deepvista-notes/SKILL.md - warning
missing-refreference to a missing file: ../deepvista-recipe-research-to-recipe/SKILL.md
Process rating: all ten parameters 52/100
- 0Tools and files. 4 referenced file(s) missing: ../deepvista-shared/SKILL.md, ../deepvista-vistabase/SKILL.md, ../deepvista-notes/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 651 tokens
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 3 example trigger phrases
- +3Description length 540: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.