CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-review-report

编写产品评测报告的 skill。流程:询问被评测产品名、资料/链接、评测功能点、目标使用场景、竞品 → 网络核实最新状态 → 站在决策者(买不买)和使用者(好不好用)双视角 → 输出图文并茂的 markdown 评测报告到当前项目的 markdown/ 目录。报告包含:TL;DR、双视角结论、维度评分、竞品对比、选型决策树、实操指南、依据与参考。适用于"评测 XX 产品"、"对比 X 和 Y"、"XX 工具选型"等需求。

71

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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-structured instruction-only skill body: lean, sequenced workflow with a validation checklist and clean one-level-deep reference and asset files. The main gaps are the absence of a retry/fix loop after the self-check and the lack of concrete example artifacts (search queries, question option sets, scoring tables).

Suggestions

Add a feedback loop to Step 7: state what to do when a checklist item fails (e.g. which step to revisit and re-run the check before writing the file).

Include one small concrete example — e.g. a sample 竞品对比 1-5 星 table row or a sample AskUserQuestion options block — so the common output cases are copy-paste ready.

Replace the personal absolute path example with a generic one (e.g. <project>/markdown/) to keep the guidance portable.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout: short bullet steps, 何时使用/何时不要使用 lists, concrete rules (SVG 字体、文件名、mkdir 命令), and no explanations of concepts Claude already knows (no "what is mermaid/markdown" padding). One slightly noisy detail — the personal absolute path example "/Users/digoal/new/markdown/" — is a concrete path template, not padding.

5 / 5

Actionability

Guidance is largely executable: named tools ("AskUserQuestion", "mcp__MiniMax__web_search"), exact output paths and naming rules, "mkdir -p markdown/svg", an 8-section report structure, and a pre-output self-check checklist. Not level 5 because there are no concrete examples of the actual artifacts (e.g. a sample search query pair, a sample AskUserQuestion option set, or a scoring-table snippet) that would make the common cases copy-paste ready.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with an explicit Step 7 自检 checklist (7 checkboxes) as a validation checkpoint before output, and skip-conditions in Step 1. It falls short of the level-5 anchor because the checklist has no feedback loop — there is no 'if a check fails, go back and fix X' recovery guidance.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview; detailed material is split into one-level-deep, clearly signaled bundle files — "读 references/evaluation-framework.md" (load timing stated in the file header) and "参考 assets/report-skeleton.md" — both verified to exist, and each is listed again in a Resources section with a one-line description of when to use it.

5 / 5

Total

18

/

20

Passed

Description

88%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 description: concrete capabilities, explicit 'use when' trigger guidance, and natural trigger phrases. The only weaknesses are slightly incomplete synonym coverage for triggers and mild overlap risk with generic comparison requests.

Suggestions

Add one or two more natural trigger variations to the 适用于 clause (e.g. "XX 值不值得买"、"推荐用哪个") to broaden keyword coverage.

Qualify the 对比/选型 triggers slightly (e.g. "对比 X 和 Y 这类产品/工具选型") to reduce conflict with generic code or data comparison requests.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions ("询问被评测产品名、资料/链接、评测功能点、目标使用场景、竞品", "网络核实最新状态", "输出图文并茂的 markdown 评测报告到当前项目的 markdown/ 目录") plus a full inventory of report sections (TL;DR、双视角结论、维度评分、竞品对比、选型决策树、实操指南、依据与参考). It is written in an impersonal, descriptive voice, so no person-voice penalty applies.

5 / 5

Completeness

It explicitly answers 'what' (编写产品评测报告, with workflow arrow chain and report contents) and 'when' ("适用于"评测 XX 产品"、"对比 X 和 Y"、"XX 工具选型"等需求"), matching the anchor for both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrases are present and quoted directly: "评测 XX 产品", "对比 X 和 Y", "XX 工具选型", plus conversational framings "买不买" and "好不好用". Not level 5 because a few common synonyms users would say (e.g. 评价/测评/推荐哪个/值不值得买) are missing, though coverage is well above the 'some relevant keywords' anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — dual-perspective (decision-maker/user) product evaluation reports with competitor comparison — with distinct trigger phrasing. Minor overlap risk remains: "对比 X 和 Y" could also fire on generic non-product comparisons (e.g. code or data comparisons), so it does not fully meet the 'minimal conflict risk' anchor.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

digoal/blog

Path

skills/product-review-report/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.