CF agency-os
(no description)
As a process F 55/100 · Will not run — References files that are not bundled: url, <corpus-url>, <guidance-url>
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- 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 - warning
body-longSKILL.md body ≈ 12176 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url - warning
missing-refreference to a missing file: <corpus-url> - warning
missing-refreference to a missing file: <guidance-url> - warning
missing-refreference to a missing file: <parent-url> - warning
missing-refreference to a missing file: <url> - warning
missing-refreference to a missing file: <task-url> - warning
missing-refreference to a missing file: <notion-url> - warning
missing-refreference to a missing file: dep-url - warning
missing-refreference to a missing file: <result-link> - warning
missing-refreference to a missing file: references/resources.md
Process rating: all ten parameters 55/100
Will not run. References files that are not bundled: url, <corpus-url>, <guidance-url>
- 0Tools and files. 10 referenced file(s) missing: url, <corpus-url>, <guidance-url>
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 12176 tokens: crowds the task out of the window
- 100Steps. 107 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 18 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (35 tags): a typed call is more reliable
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 107 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This skill is not clearly malicious, but it can change a live Notion task board from loose chat phrases, so users should review its scope before installing.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026