SKILLEMALL.ai

CC lean-ux-canvas

Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

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

Guide teams through Lean UX Canvas v2.

As a process C 59/100 · Has gaps — References files that are not bundled: ../workshop-facilitation/SKILL.md, skills/problem-statement/SKILL.md, skills/problem-framing-canvas/SKILL.md

AnalyzerDesignOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
95
Quality 40%
63
Run on models
none yet
Process rating
C
59/100
Has gaps
References files that are not bundled: ../workshop-facilitation/SKILL.md, skills/problem-statement/SKILL.md, skills/problem-framing-canvas/SKILL.md
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Obfuscation medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.

For the author

Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Obfuscation obf-base64-blob SKILL.md:570
    Long base64-looking blob
    - **Lean UX Canvas PDF** — [Download v2 PDF](https://stat…com/static/5e02…9e1/t/5e10…8fa/1578112737021/Lean…pdf)

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5907 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../workshop-facilitation/SKILL.md
  • warning missing-ref reference to a missing file: skills/problem-statement/SKILL.md
  • warning missing-ref reference to a missing file: skills/problem-framing-canvas/SKILL.md
  • warning missing-ref reference to a missing file: skills/proto-persona/SKILL.md
  • warning missing-ref reference to a missing file: skills/jobs-to-be-done/SKILL.md
  • warning missing-ref reference to a missing file: skills/epic-hypothesis/SKILL.md
  • warning missing-ref reference to a missing file: skills/discovery-interview-prep/SKILL.md
  • warning missing-ref reference to a missing file: skills/pol-probe-advisor/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 59/100

Will not run. References files that are not bundled: ../workshop-facilitation/SKILL.md, skills/problem-statement/SKILL.md, skills/problem-framing-canvas/SKILL.md
  • 0Tools and files. 8 referenced file(s) missing: ../workshop-facilitation/SKILL.md, skills/problem-statement/SKILL.md, skills/problem-framing-canvas/SKILL.md
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 15 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5907 tokens
  • 100Steps. 137 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place

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
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 131: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 137 items
  • +4Has examples (3 code blocks)

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