CF rea-tool-design
Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
The skill promises a tool for designing and modifying REA investigation utilities, CLI/MCP contracts, and Evidence semantics. In reality—one file with 202 tokens of description. No critical errors, but a quality score of 46 signals a draft: logic unchecked, examples missing. Broken references, no sandbox runs. Multi-platform support is listed across major models, but without actual tests it's just a claim.
The folder contains no working scripts, only description. Install only if you're prepared to patch it on the fly or treat it as a template for your own work. Too raw for production use.
Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
As a process F 20/100 · No process to follow — References files that are not bundled: ../../../docs/tool-design.md, ../../../docs/testing.md, ../../../CONTRIBUTING.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../../../docs/tool-design.md - warning
missing-refreference to a missing file: ../../../docs/testing.md - warning
missing-refreference to a missing file: ../../../CONTRIBUTING.md
Process rating: all ten parameters 20/100
- 0Tools and files. 3 referenced file(s) missing: ../../../docs/tool-design.md, ../../../docs/testing.md, ../../../CONTRIBUTING.md
- 0Steps. Prose only: no discrete steps
- 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
- 20When it triggers. No condition that starts the skill
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 202 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 107: 120–800 characters recommended
- +4Structure: 1 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
Quality base 70; lint remarks subtract, signals add up to 100. Result: 46.