SKILLEMALL.ai

BC problem-framing-canvas

Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.

deanpeters/Product-Manager-Skills Claude Code author: deanpeters NOASSERTION 3 files body ≈ 4 189 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Guide teams through MITRE's Problem Framing Canvas.

As a process C 51/100 · Has gaps — References files that are not bundled: ../workshop-facilitation/SKILL.md

GeneratorData and analyticsAI and agentsOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
51/100
Has gaps
References files that are not bundled: ../workshop-facilitation/SKILL.md
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../workshop-facilitation/SKILL.md
  • note frontmatter-key unknown frontmatter key "intent"
  • note frontmatter-key unknown frontmatter key "type"
  • note frontmatter-key unknown frontmatter key "best_for"
  • note frontmatter-key unknown frontmatter key "scenarios"
  • note frontmatter-key unknown frontmatter key "theme"
  • note frontmatter-key unknown frontmatter key "estimated_time"

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: ../workshop-facilitation/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../workshop-facilitation/SKILL.md
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 4 mutating operations with no state check
  • 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
  • 70Execution cost. Instruction body is 4189 tokens
  • 100Steps. 73 steps
  • 100Consistency. Name and required fields are in place
  • low 10 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 126: enough signal without eating the budget
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 73 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)

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