AF deepvista-recipe-import-files
Recipe: Import files from the current directory (recursively) as context cards in DeepVista. TRIGGER when: user wants to import files as cards, "index this folder", "add files to DeepVista", "import codebase as context", "upload files as knowledge cards", "add all files in this directory to my knowledge base", or any request to bulk-import local files into DeepVista. DO NOT TRIGGER when: user wants to create a single note or card manually; or when working with non-file card types.
As a process F 55/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
Process rating: all ten parameters 55/100
- 0Tools and files. 3 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
- 30Running it twice. 7 mutating operations with no state check
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1089 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 5 example trigger phrases
- +3Description length 485: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.