SKILLEMALL.ai

CC product-sense-interview-answer

Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.

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

Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs.

As a process C 50/100 · Has gaps — References files that are not bundled: ../problem-statement/SKILL.md, ../proto-persona/SKILL.md, ../customer-journey-map/SKILL.md

GeneratorYouTubeAI and agentsMedia and videotype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
C
50/100
Has gaps
References files that are not bundled: ../problem-statement/SKILL.md, ../proto-persona/SKILL.md, ../customer-journey-map/SKILL.md
Tools and files w 18
0
Result and completion w 14
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../problem-statement/SKILL.md
  • warning missing-ref reference to a missing file: ../proto-persona/SKILL.md
  • warning missing-ref reference to a missing file: ../customer-journey-map/SKILL.md
  • warning missing-ref reference to a missing file: ../opportunity-solution-tree/SKILL.md
  • note frontmatter-key unknown frontmatter key "intent"
  • note frontmatter-key unknown frontmatter key "type"
  • note frontmatter-key unknown frontmatter key "theme"
  • note frontmatter-key unknown frontmatter key "best_for"
  • note frontmatter-key unknown frontmatter key "scenarios"
  • note frontmatter-key unknown frontmatter key "estimated_time"

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: ../problem-statement/SKILL.md, ../proto-persona/SKILL.md, ../customer-journey-map/SKILL.md
  • 0Tools and files. 4 referenced file(s) missing: ../problem-statement/SKILL.md, ../proto-persona/SKILL.md, ../customer-journey-map/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 4 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 88 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2682 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 192: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 88 items
  • +4Has examples (0 code blocks)

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