SKILLEMALL.ai
GitHub ↗ RU Sign in

AF tool-design-sprint-readiness

Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, customer recruiting plan, and pre-sprint activities. Use when a team is considering starting a Design Sprint and wants a fast yes/no diagnosis before committing five days of team time and customer recruiting cost.

product-on-purpose/pm-skills Agent Skills author: product-on-purpose Apache-2.0 4 files body ≈ 2 567 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first.

As a process F 40/100 · Will not run — References files that are not bundled: ../../docs/reference/skill-families/design-sprint-skills-contract.md

AnalyzerOperations and projectstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
F
40/100
Will not run
References files that are not bundled: ../../docs/reference/skill-families/design-sprint-skills-contract.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/reference/skill-families/design-sprint-skills-contract.md

Process rating: all ten parameters 40/100

Will not run. References files that are not bundled: ../../docs/reference/skill-families/design-sprint-skills-contract.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/reference/skill-families/design-sprint-skills-contract.md
  • 0Result and completion. Does not say what the result is
  • 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
  • 30Running it twice. 8 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2567 tokens

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)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 446: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 33 items
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.