CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/product-sense-interview-answer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, actionable coaching scaffold with per-step quality bars and recovery guidance. Its main weaknesses are conceptual padding across overlapping sections and references to bundle files that are not present.

Suggestions

Trim or merge 'What Product Sense Interviews Actually Test', 'Why This Works', 'Anti-Patterns', and 'Common Pitfalls' to remove conceptual background Claude already knows and reduce overlap.

Provide the referenced template.md and examples/improve-youtube.md as real bundle files, or inline the minimal template so the skill is self-contained.

Add an explicit validation checkpoint (e.g. 'before moving to Solution, confirm the top pain point is a user friction, not a missing feature') to harden the per-step quality bars into gates.

DimensionReasoningScore

Conciseness

Mostly efficient with genuine step-specific guidance, but sections like 'What Product Sense Interviews Actually Test', 'Why This Works', 'Anti-Patterns', and 'Common Pitfalls' overlap and include conceptual background Claude already knows, so it could be tightened.

3 / 5

Actionability

Provides concrete executable guidance — the 'Help [user] [achieve outcome], so that [broader impact]' goal format, per-step quality bars, and good/bad examples — with minor gaps since the full worked example lives in an external file.

4 / 5

Workflow Clarity

The six-part spine is clearly sequenced as Steps 1-6 with a 'Quality bar' checkpoint per step and 'Fix it by...' recovery guidance in Common Pitfalls, meeting the 4 anchor though validation is implicit rather than a hard gate.

4 / 5

Progressive Disclosure

Sections are well organized and references are clearly signaled as markdown links, but the referenced bundle files (template.md, examples/improve-youtube.md) do not exist in the bundle, so navigation is broken and content stays inline.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-crafted: it states concrete capabilities, gives explicit 'Use when' trigger guidance tied to real prompt archetypes, and occupies a distinct niche. Minor keyword synonyms could broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete answer components ('assumptions, segmentation, pain-point prioritization, and MVP tradeoffs') in third-person imperative form, though these are answer parts rather than discrete operations, leaving minor coverage gaps versus the 5 anchor.

4 / 5

Completeness

Explicitly answers both what ('Structure a spoken PM product-sense answer with...') and when ('Use when practicing design, improve, or build-next interview questions') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases 'design, improve, or build-next interview questions' map directly to the three common product-sense prompt archetypes, with good keyword coverage though synonyms like 'product sense' or 'mock interview' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PM product-sense interviews) with distinct triggers unlikely to fire for unrelated skills, satisfying the 5 anchor for minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 4 missing, 4 suspicious

Warning

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.