product-manager-toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill product-manager-toolkit81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its product management domain with specific, actionable capabilities. It uses appropriate third-person voice, includes natural trigger terms that PMs would use, and explicitly states both what the skill does and when to use it. The description effectively distinguishes itself from generic business or document skills through PM-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies' along with specific use cases like 'feature prioritization, user research synthesis, requirement documentation.' | 3 / 3 |
Completeness | Clearly answers both what (comprehensive toolkit with specific capabilities) and when ('Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords product managers would use: 'RICE prioritization', 'customer interview', 'PRD', 'feature prioritization', 'user research', 'requirement documentation', 'product strategy', 'go-to-market' - these are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting product management specifically with distinct PM-specific triggers like 'RICE', 'PRD', 'discovery frameworks', 'go-to-market' that are unlikely to conflict with general document or analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionable guidance with executable commands and clear script documentation, making it immediately usable. However, it suffers from verbosity by including generic PM knowledge Claude already possesses (interview tips, stakeholder management, common pitfalls) and lacks validation steps in its workflows for verifying script outputs or handling edge cases.
Suggestions
Remove generic PM advice sections (Best Practices, Common Pitfalls, Stakeholder Management) that Claude already knows - focus only on project-specific tooling and workflows
Add validation steps to workflows: e.g., 'Verify RICE output shows expected features before proceeding' or 'Check analyzer extracted at least 3 pain points; if not, review transcript format'
Move detailed framework explanations (MoSCoW, Opportunity Solution Tree, Funnel Analysis) to a separate FRAMEWORKS.md reference file to keep SKILL.md as a lean overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what RICE stands for, basic interview techniques, stakeholder management tips). The 'Best Practices' and 'Common Pitfalls' sections contain generic PM advice that doesn't add unique value. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear examples, specific CSV formats, and concrete script usage patterns. The quick start section is copy-paste ready, and script documentation includes multiple usage examples with flags. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (Feature Prioritization, Customer Discovery, PRD Development), but validation checkpoints are missing. There's no guidance on verifying script outputs, handling errors, or feedback loops for when analysis results seem incorrect. | 2 / 3 |
Progressive Disclosure | References external files (prd_templates.md, scripts) appropriately, but the main document is quite long with content that could be split out (frameworks, best practices, common pitfalls). The integration points and generic PM advice sections bloat the overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.