BC ocas-look
Converts user-provided images into validated, decision-ready action drafts. Routes images by inferred intent across domains: events from flyers, macros from meal photos, places to save, products to price, receipts to log, documents to file, civic issues to report. Supports reverse image search via Yandex and Google. NOT for generic OCR, computer vision research, or surveillance.
Converts user-provided images into validated, decision-ready action drafts.
As a process C 51/100 · Has gaps — weak spots: result and completion, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 381 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "warning" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "includes" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 85Steps. 71 steps, 2 vague phrases
- 100Execution cost. Instruction body is 2657 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 25 top-level sections: this looks like several domains in one skill
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 381: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 71 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (14 of 14)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.