CC ai-shaped-readiness-advisor
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Assess whether your product work is AI-first or AI-shaped.
As a process C 66/100 · Has gaps — References files that are not bundled: ../context-engineering-advisor/SKILL.md, ../workshop-facilitation/SKILL.md, ../problem-statement/SKILL.md
How to improve
- 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.
- 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
body-longSKILL.md body ≈ 10463 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../context-engineering-advisor/SKILL.md - warning
missing-refreference to a missing file: ../workshop-facilitation/SKILL.md - warning
missing-refreference to a missing file: ../problem-statement/SKILL.md - warning
missing-refreference to a missing file: ../epic-hypothesis/SKILL.md - warning
missing-refreference to a missing file: ../pol-probe-advisor/SKILL.md - warning
missing-refreference to a missing file: ../discovery-process/SKILL.md - warning
missing-refreference to a missing file: ../positioning-statement/SKILL.md - note
frontmatter-keyunknown frontmatter key "intent" - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "theme" - note
frontmatter-keyunknown frontmatter key "best_for" - note
frontmatter-keyunknown frontmatter key "scenarios" - note
frontmatter-keyunknown frontmatter key "estimated_time"
Process rating: all ten parameters 66/100
- 0Tools and files. 7 referenced file(s) missing: ../context-engineering-advisor/SKILL.md, ../workshop-facilitation/SKILL.md, ../problem-statement/SKILL.md
- 30Running it twice. 21 mutating operations with no state check
- 40Execution cost. Instruction body is 10463 tokens: crowds the task out of the window
- 60Steps. 385 steps, 4 vague phrases
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 8 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
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
- -225 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 138: enough signal without eating the budget
- +4Structure: 45 headings
- +3Step-by-step instructions: 385 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.