CC strategic-reading
Read a book, article, transcript, or case study through the lens of a specific strategic problem you're facing. Produces an applied playbook that maps the source onto the problem and gives short/medium/long-term recommendations. NOT for general book summaries.
Read a book, article, transcript, or case study through the lens of a specific strategic problem you're facing.
As a process C 55/100 · Has gaps — References files that are not bundled: ../conventions/quality.md, ../_brain-filing-rules.md, ../conventions/agent-operator-protocol.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: ../conventions/quality.md - warning
missing-refreference to a missing file: ../_brain-filing-rules.md - warning
missing-refreference to a missing file: ../conventions/agent-operator-protocol.md - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "mutating" - note
frontmatter-keyunknown frontmatter key "writes_pages" - note
frontmatter-keyunknown frontmatter key "writes_to" - note
frontmatter-keyunknown frontmatter key "brain_first"
Process rating: all ten parameters 55/100
- 0Tools and files. 3 referenced file(s) missing: ../conventions/quality.md, ../_brain-filing-rules.md, ../conventions/agent-operator-protocol.md
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1609 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 260: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.