cs-product-manager

Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework. Use when a product decision needs structure and evidence — e.g., RICE-scoring a backlog of 20 feature requests before quarterly planning, or drafting a PRD from raw customer-interview notes.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-product-manager/SKILL.md

Quality

Content

56%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 highly actionable and well-sequenced across seven PM workflows, but it is padded by heavy command repetition and inlined cross-skill descriptions that belong behind links. Tightening repetition and leaning more on references would materially improve token efficiency and navigation.

Suggestions

Define each tool's command once in the Python Tools table and reference it from workflows/examples instead of repeating the full path and invocation in every section.

Replace the inlined Knowledge Base and Success Metrics sections with brief one-line pointers to the referenced files, keeping only what Claude cannot derive.

Consolidate the three Integration Examples (which re-run the same rice_prioritizer/interview_analyzer commands) into a single representative example or move them to a referenced file.

Dimension	Reasoning	Score
Conciseness	The ~675-line body is noticeably verbose: the same full-path commands are repeated verbatim across Python Tools, Workflows, and Integration Examples, and aspirational Success Metrics plus per-workflow Time Estimates add padding without aiding execution.	2 / 5
Actionability	Concrete, copy-paste-ready commands with real arguments and CSV schemas (e.g. 'python .../rice_prioritizer.py features.csv --capacity 20'); minor gaps from relative paths assuming a fixed repo layout.	4 / 5
Workflow Clarity	Seven workflows each have a numbered sequence, goal, and Expected Output; review steps act as checkpoints. These are non-destructive planning workflows, so the missing explicit validate→fix→retry loops are a minor rather than disqualifying gap.	4 / 5
Progressive Disclosure	Section/table structure is reasonable and references are signaled via paths, but the Python Tools and Knowledge Bases sections inline descriptions of other skills' content and repeat the command catalog instead of linking one level deep.	3 / 5
	Total	13 / 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 capabilities and provides explicit, concrete 'Use when' triggers with realistic examples. It is specific and distinguishable, with only minor coverage gaps relative to the full body.

Dimension	Reasoning	Score
Specificity	Names the product domain plus several concrete actions ('feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework'); minor gaps since personas, competitive analysis, and OKRs covered in the body are absent here.	4 / 5
Completeness	Explicitly answers both what ('feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework') and when ('Use when a product decision needs structure and evidence — e.g., RICE-scoring a backlog of 20 feature requests before quarterly planning, or drafting a PRD from raw customer-interview notes').	5 / 5
Trigger Term Quality	Natural PM phrases a user would actually say appear ('RICE-scoring a backlog', 'quarterly planning', 'drafting a PRD', 'customer-interview notes'); a few common synonyms (user stories, OKRs, personas) are missing.	4 / 5
Distinctiveness Conflict Risk	Clear PM niche with distinct RICE/PRD triggers and minimal conflict risk; minor overlap with the orchestrated sub-skills (agile-product-owner, product-strategist, ux-researcher) it coordinates.	4 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (685 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing, 3 suspicious	Warning

	Total	13 / 16 Passed

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

Reviewed: ~5 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.