CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-manager-toolkit

产品经理必备利器!当面临海量需求排期、用户调研分析和PRD撰写等场景时,使用此工具可一键计算RICE得分、自动提炼访谈洞察并快速生成标准PRD文档,大幅提升需求决策与产品交付效率,让规划更科学。

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/product-manager-toolkit/product-manager-toolkit/SKILL.md
SKILL.md
Quality
Evals
Security

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 script-centric half of the body is strong — executable commands, documented flags, and clear step-by-step workflows. The overall quality is dragged down by severe padding: a ~250-line speculative agent-collaboration section and re-explanations of well-known PM frameworks that inflate token cost without adding skill-specific value.

Suggestions

Move the entire "与智能体协作框架集成" section (roughly lines 362-611) into a separate reference file (e.g., references/agent-integration.md) and keep a 2-3 line pointer — it is ~40% of the body and documents other skills rather than this one, including references to files not in this bundle.

Cut or compress the generic PM frameworks (RICE formula, MoSCoW, Value vs Effort matrix, North Star Metric, funnel analysis) that Claude already knows; retain only the script-specific conventions such as the impact/confidence/effort enums and the CSV format.

Add validation checkpoints to the workflows — e.g., after running rice_prioritizer.py, check its output for unmapped or out-of-range impact/confidence/effort values before generating the roadmap, and re-run with corrected data.

DimensionReasoningScore

Conciseness

The ~250-line "与智能体协作框架集成" section is speculative cross-skill integration content with non-executable pseudocode, and sections like the RICE formula, MoSCoW, Value vs Effort matrix, North Star Metric, and funnel analysis re-explain standard PM concepts Claude already knows. Not 1 because the script-usage sections (Quick Start, Key Scripts) are lean and genuinely useful.

2 / 5

Actionability

Copy-paste-ready commands with concrete flags are provided ("python scripts/rice_prioritizer.py features.csv --capacity 20", "--output json", "python scripts/rice_prioritizer.py sample" to create sample data), plus the CSV schema (name,reach,impact,confidence,effort). Not 5 because PRD workflow steps are vague ("Fill in sections based on discovery work") and the Chinese section contains non-executable pseudocode ("self.call_tool(\"rice_prioritizer\", ...)").

4 / 5

Workflow Clarity

Three multi-step workflows (Feature Prioritization, Customer Discovery, PRD Development) are clearly sequenced with embedded commands and review steps ("Review quick wins vs big bets", "Validate against strategy", "Measure actual vs expected behavior"). Not 5 because there are no explicit validation checkpoints or error-recovery loops (e.g., nothing on handling malformed CSV input or unmapped impact/confidence values); not 3 because sequences include concrete commands rather than bare step lists.

4 / 5

Progressive Disclosure

Real bundle files are referenced one level deep and clearly signaled ("Choose template from `references/prd_templates.md`", both scripts under `scripts/`), and prd_templates.md exists in the bundle. However, ~40% of the body — the agent-integration section and the generic frameworks/metrics/best-practices material — is inlined in SKILL.md when it belongs in separate reference files, and the Chinese section points to external skill paths ("agent-team/references/agent-registry.md", "multi-agent-meeting/assets/meeting-templates/...") that are not part of this bundle.

3 / 5

Total

13

/

20

Passed

Description

75%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 answers both what and when with three concrete capabilities and natural PM trigger terms. Its main weakness is marketing fluff ("必备利器!", "大幅提升…让规划更科学") and missing common trigger synonyms such as 优先级排序 and 竞品分析.

Suggestions

Remove marketing fluff ("产品经理必备利器!", "大幅提升需求决策与产品交付效率,让规划更科学") — these tokens add no trigger or capability information.

Add missing natural trigger synonyms such as "优先级排序", "需求评审", and "竞品分析" so the description matches how users actually phrase these requests.

DimensionReasoningScore

Specificity

"一键计算RICE得分、自动提炼访谈洞察并快速生成标准PRD文档" lists several concrete actions (RICE scoring, interview insight extraction, PRD generation), though coverage gaps exist (roadmap/capacity planning done by the scripts are unmentioned) and marketing padding ("必备利器!", "大幅提升需求决策与产品交付效率,让规划更科学") dilutes it. Not 5 because of the fluff and gaps; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Both parts are explicit: what ("计算RICE得分、提炼访谈洞察、生成标准PRD文档") and when ("当面临海量需求排期、用户调研分析和PRD撰写等场景时"). Not 5 because the when-clause relies on the open-ended "等场景" rather than concrete trigger phrases users would say; not 3 because the when is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Natural PM terms are present — "需求排期", "用户调研分析", "PRD撰写", "RICE得分", "访谈" — which users would plausibly say. Not 5 because common variations like "优先级排序" (prioritization, arguably the primary trigger), "竞品分析", and "路线图" are missing; not 3 because keyword coverage is genuinely good.

4 / 5

Distinctiveness Conflict Risk

The PM-specific niche (RICE scoring, interview analysis, PRD documents) is clearly distinguishable, with distinct triggers like "RICE得分" and "PRD撰写". Not 5 because broader phrases ("需求决策", "产品交付效率") create minor overlap with general prioritization or writing skills.

4 / 5

Total

16

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (611 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

anbeime/skill

Path

skills/product-manager-toolkit/product-manager-toolkit/SKILL.md

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.