product-manager-toolkit

Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./product-team/skills/product-manager-toolkit/SKILL.md

Quality

Content

67%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.

A well-organized, actionable skill body with clear multi-step workflows, validation checklists, and properly signaled one-level-deep references to real bundle files. It leans verbose in places — the Best Practices, Common Pitfalls, and Quick Reference sections duplicate guidance already present in the workflows.

Suggestions

Trim or move 'Best Practices' and 'Common Pitfalls' into a reference file; they restate workflow guidance and inflate the body without adding new executable detail.

Replace the repeated command block in 'Quick Reference' with a one-line pointer to the Tools Reference section to cut redundancy.

Tighten the interview-analyzer command documentation so the positional 'json' output argument is explicit rather than only shown by example.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but sections like 'Best Practices', 'Common Pitfalls', and the repeated command blocks in 'Quick Reference' restate guidance already covered in the workflows, adding padding Claude could infer.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands and a real CSV input example are provided for both tools, with only minor gaps (e.g., the interview analyzer's positional 'json' argument is shown but not documented as a flag).	4 / 5
Workflow Clarity	Each core workflow is a clearly sequenced multi-step process with explicit validation checklists ('Before finalizing the roadmap', 'Before building'), but the checkpoint actions are checklist items rather than executable validate-then-fix feedback loops.	4 / 5
Progressive Disclosure	Good structure overall: SKILL.md stays an overview with clearly signaled one-level-deep references (references/frameworks.md, prd_templates.md, input-output-examples.md), all of which are real files; minor gaps are the inlined pitfalls/best-practices tables that could live in a reference.	4 / 5
	Total	15 / 20 Passed

Description

83%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.

A strong, third-person description that clearly states what the toolkit does and when to use it, with concrete capability enumeration and explicit trigger guidance. Its main weakness is trigger-term breadth — it misses synonyms and natural phrasings a user might actually say.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies' — each a specific action domain, with only minor coverage gaps (e.g., go-to-market is named but not unpacked).	4 / 5
Completeness	Explicitly answers both 'what' (the enumerated toolkit capabilities) and 'when' via a clear 'Use when...' clause with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy'), but it lacks synonyms/file extensions and common variations users might say.	4 / 5
Distinctiveness Conflict Risk	The product-management niche is clear and the triggers are fairly specific, but the breadth ('product strategy', 'go-to-market') creates minor overlap risk with adjacent strategy/marketing skills rather than a fully distinct niche.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: product-team/skills/product-manager-toolkit/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

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.