AF brief
/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation — e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision.
/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake.
As a process F 57/100 · Will not run — References files that are not bundled: ../../agents/cs-chief-of-staff.md, ../../../c-level-advisor/skills/context-engine/SKILL.md, ../../../c-level-advisor/skills/board-meeting/SKILL.md
How to improve
- 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
missing-refreference to a missing file: ../../agents/cs-chief-of-staff.md - warning
missing-refreference to a missing file: ../../../c-level-advisor/skills/context-engine/SKILL.md - warning
missing-refreference to a missing file: ../../../c-level-advisor/skills/board-meeting/SKILL.md
Process rating: all ten parameters 57/100
- 0Tools and files. 3 referenced file(s) missing: ../../agents/cs-chief-of-staff.md, ../../../c-level-advisor/skills/context-engine/SKILL.md, ../../../c-level-advisor/skills/board-meeting/SKILL.md
- 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 16 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 879 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 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)
- +1No license
- +2Single-language instructions
- +3Description length 314: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.