C temp-skill
(no description)
C
60/100
Overall score
- Safety 60%
- Quality 40%
- Tests bonus
How to improve
- Add a description to the frontmatter: without it the skill can never trigger.
- Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
- Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.
Guard findings · 0
✓ No critical or high findings
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Lint
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process maturity 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 705 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Structure: 25 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: clean
This is a local portfolio backtesting skill that reads a user-selected CSV and writes reports and charts, with privacy and overwrite caveats but no evidence of hidden access, exfiltration, or destructive intent.
LLM: benign (high) · VirusTotal: suspicious · 28 May 2026