AC paprika-recipe-importer
Convert recipe text (pasted text, video transcript, image description, or any raw content) into a .paprikarecipes file that can be imported directly into the Paprika Recipe Manager app. Use when the user shares a recipe in any format (text, transcript, image) and wants a Paprika import file. Triggers on phrases like "create a Paprika file", "import into Paprika", "save this recipe to Paprika", or when a recipe is shared and export to Paprika is implied.
As a process C 57/100 · Has gaps — weak spots: result and completion, 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: 3. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 595 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 457: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.