Agent skill

Product Review Report

by digoal in digoal/blog

编写专业产品评测报告,站在用户决策者与使用者双重视角深度评测产品。输入产品名称(以及可选的产品资料/链接、功能点、使用场景、竞品),自动搜集产品信息、竞品对比数据与行业数据,生成结论清晰、逻辑严谨、有理论依据与数据支撑、图文并茂的 Markdown 评测报告(SVG 图以外挂文件形式引用),输出到项目 markdown/…

GPL-2.0Auto-check passedDocuments & Office

Install Product Review Report

skills CLI
$ npx skills add digoal/blog --skill product-review-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install digoal/blog product-review-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills_for_claude_web/product-review-report .claude/skills/product-review-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-review-report
GitHub stars
8.6k
Token cost
~889 tokens
SKILL.md length
144 words
Files
3 (incl. references)
Skills in repo
98
Repo updated
First seen
Licence
GPL-2.0

At a glance

编写专业产品评测报告,站在用户决策者与使用者双重视角深度评测产品。输入产品名称(以及可选的产品资料/链接、功能点、使用场景、竞品),自动搜集产品信息、竞品对比数据与行业数据,生成结论清晰、逻辑严谨、有理论依据与数据支撑、图文并茂的 Markdown 评测报告(SVG 图以外挂文件形式引用),输出到项目 markdown/…

  • Works in 6 steps: 结论前置:每个章节先给结论,再展开论据,不要"先铺垫、后点题" → 数据说话:每个重要判断必须有数据或事件支撑,不接受"据说""可能""一般来说"等模… → 双视角标注:决策者与使用者关心的点不同时,用 🎯 决策者 和 🛠 使用者… → …
  • Tasks that involve Markdown
  • SKILL.md covers 第一步:收集评测信息, 第二步:信息搜集与研究, 第三步:评测维度框架 and 第四步:竞品对比, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Review Report is an agent skill from digoal/blog. 编写专业产品评测报告,站在用户决策者与使用者双重视角深度评测产品。输入产品名称(以及可选的产品资料/链接、功能点、使用场景、竞品),自动搜集产品信息、竞品对比数据与行业数据,生成结论清晰、逻辑严谨、有理论依据与数据支撑、图文并茂的 Markdown 评测报告(SVG 图以外挂文件形式引用),输出到项目 markdown/ 目录。触发条件:用户提到"产品评测"、"写评测报告"、"帮我评测XX"、"product review"、"产品对比报告"、"帮我写XX的评测"、"功能评测"、"这个产品怎么样"、"XX和YY哪个更好"、"帮我做个产品调研"、"竞品分析"、"选型报告"。即使用户只提供了产品名称和希望"帮我看看这个产品",也应立即使用本 skill。

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/report-examples.md` and `references/scoring-rubric.md`).

It sits in Documents & Office, covering Markdown. The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.

When your agent uses it

  • Tasks that involve Markdown

Example prompts

  • “帮我评测XX”
  • “product review”
  • “产品对比报告”
  • “/product-review-report”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 结论前置:每个章节先给结论,再展开论据,不要"先铺垫、后点题"
  2. 数据说话:每个重要判断必须有数据或事件支撑,不接受"据说""可能""一般来说"等模糊表述
  3. 双视角标注:决策者与使用者关心的点不同时,用 🎯 决策者 和 🛠 使用者 标签区分
  4. 不粉饰缺点:缺点和风险要如实写出,报告的价值在于帮助用户做出正确决策,而不是为产品做广告
  5. 量化优先:能量化的就量化(节省 X 小时/周、错误率降低 Y%),不能量化的要说明原因
  6. 中文为主:除专有名词外,报告全程使用中文,专有名词首次出现时提供中文解释

What it can do on your machine

Read from SKILL.md and the folder at commit ad6fcb7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Review Report loads about 889 tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 144 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~889
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from digoal/blog at commit ad6fcb7, republished under its GPL-2.0 licence (© digoal). 144 words, ~889 tokens.

Download SKILL.mdSave it as .claude/skills/product-review-report/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
product-review-report
description
编写专业产品评测报告,站在用户决策者与使用者双重视角深度评测产品。输入产品名称(以及可选的产品资料/链接、功能点、使用场景、竞品),自动搜集产品信息、竞品对比数据与行业数据,生成结论清晰、逻辑严谨、有理论依据与数据支撑、图文并茂的 Markdown 评测报告(SVG 图以外挂文件形式引用),输出到项目 markdown/ 目录。触发条件:用户提到"产品评测"、"写评测报告"、"帮我评测XX"、"product review"、"产品对比报告"、"帮我写XX的评测"、"功能评测"、"这个产品怎么样"、"XX和YY哪个更好"、"帮我做个产品调研"、"竞品分析"、"选型报告"。即使用户只提供了产品名称和希望"帮我看看这个产品",也应立即使用本 skill。

Product Review Report Skill

站在 用户决策者(采购/管理层) 与 用户使用者(一线操作人员) 双重视角,撰写专业、可落地的产品评测报告。


第一步:收集评测信息

在开始评测前,先向用户询问必要信息(已在对话中提供的直接使用,不必重复询问):

必填项:
1. 产品名称(带版本号更佳)

可选项(有则更完整,无则自行搜集):
2. 产品相关资料或链接(官网、文档、Demo、白皮书等)
3. 要评测的功能点(如:搜索效率、API 接口、数据安全等)
4. 目标使用场景(如:中型电商日均万单履约、医院HIS系统集成等)
5. 要对比的竞品名称(1~3 个)

收到信息后,直接进入评测流程,不要等用户再次确认。


第二步:信息搜集与研究

使用 web_search / web_fetch 充分搜集:

  • 产品官方文档、更新日志、发布说明
  • 真实用户评价(G2、Capterra、知乎、少数派、36kr、ProductHunt 等)
  • 行业分析报告(Gartner、IDC、艾瑞等)
  • 竞品官网、功能列表、定价页、对比测评
  • 相关事故、bug 记录、用户投诉(如有)

搜集到的数据要注明来源和时间,不要捏造数据。若无法查到某项数据,在报告中如实说明。


第三步:评测维度框架

评测须覆盖以下维度,根据产品类型适当取舍或扩充:

决策者维度(采购/管理层关心的)
  • 总拥有成本(TCO):采购价、实施成本、年维护费、隐性费用
  • ROI 预期:效率提升量化估算、同类案例数据
  • 厂商可靠性:融资情况、客户规模、存续年限、服务 SLA
  • 合规与安全:数据合规(GDPR/等保/SOC2)、安全认证、审计支持
  • 战略契合度:与现有技术栈的集成难度、供应商锁定风险、未来路线图
使用者维度(一线操作人员关心的)
  • 核心功能表现:用户提供的关键功能点,逐项评测
  • 易用性:学习曲线、UI/UX、操作步骤数
  • 性能稳定性:响应速度、并发处理、已知故障记录
  • 集成与扩展性:API 质量、插件生态、与主流工具的兼容性
  • 文档与支持:文档完整度、社区活跃度、客服响应速度

第四步:竞品对比

若有竞品,逐项对比,输出评分矩阵(1~5 分制)。重点说明:

  • 被评产品相对竞品的核心优势(至少 2 条有数据支撑)
  • 被评产品相对竞品的核心劣势(不要粉饰,诚实说明)
  • 推荐选择被评产品的场景 vs 推荐选择竞品的场景

第五步:生成报告

文件结构
markdown/
├── product-review-{产品名}-{YYYYMMDD}.md     # 主报告
└── assets/
    ├── score-radar.svg                         # 评分雷达图
    ├── tco-comparison.svg                      # TCO 对比图(如有竞品)
    └── feature-matrix.svg                      # 功能矩阵图
报告结构模板

严格按以下结构输出,每个 H2 章节均需有实质内容:

markdown
# {产品名} 产品评测报告
> 评测日期:{date} | 评测版本:{version} | 对比竞品:{competitors}

## TL;DR — 一句话结论
[决策者版本:3 行以内,给出"买"或"不买"的明确建议和核心理由]
[使用者版本:3 行以内,给出"好用"或"难用"的明确判断和核心理由]

## 被评产品概览
[产品定位、目标用户、核心卖点、市场地位]

## 评分总览
[引用雷达图 SVG]
[各维度评分表格]

## 决策者视角深度评测
### 总拥有成本(TCO)分析
### ROI 预期
### 厂商可靠性
### 合规与安全
### 战略契合度与风险

## 使用者视角深度评测
### 核心功能逐项评测
[针对用户指定的功能点,逐一评测]
### 易用性体验
### 性能与稳定性
### 集成与扩展性
### 文档与技术支持

## 竞品横向对比
[引用 TCO/功能矩阵 SVG]
[何时选择被评产品 vs 何时选择竞品]

## 风险与注意事项
[已知缺陷、历史事故、需关注的合同条款等]

## 简明实操指南
### 决策者行动清单
- [ ] ...
### 使用者快速上手要点
- [ ] ...

## 综合结论与推荐
[再次明确给出"强烈推荐 / 条件推荐 / 不推荐",说明适用条件]

## 数据来源
[列出所有引用来源,含访问日期]

图表规范

SVG 图(外挂式)

所有 SVG 图 必须 保存为独立文件到 markdown/assets/ 目录,然后在 Markdown 中用图片引用格式引用:

markdown
![评分雷达图](assets/score-radar.svg)

不要 将 SVG 代码内嵌在 Markdown 正文中。

SVG 图要求:

  • 使用 viewBox 确保自适应宽度
  • 颜色方案:主色 #2563EB(蓝),辅色 #10B981(绿),警示色 #EF4444(红),中性 #6B7280(灰)
  • 字体:font-family="'PingFang SC', 'Helvetica Neue', Arial, sans-serif"
  • 必须包含图例和数值标注
  • 雷达图维度数量:6~8 个
  • 评分满分统一为 5 分
Mermaid 图(内嵌式)

适合流程图、时序图、架构对比图,内嵌在 Markdown 中:

markdown
```mermaid
flowchart LR
  ...
```
ASCII 文本图

适合简单的表格对比或示意图,直接内嵌。


写作风格要求

  1. 结论前置:每个章节先给结论,再展开论据,不要"先铺垫、后点题"
  2. 数据说话:每个重要判断必须有数据或事件支撑,不接受"据说""可能""一般来说"等模糊表述
  3. 双视角标注:决策者与使用者关心的点不同时,用 🎯 决策者 和 🛠 使用者 标签区分
  4. 不粉饰缺点:缺点和风险要如实写出,报告的价值在于帮助用户做出正确决策,而不是为产品做广告
  5. 量化优先:能量化的就量化(节省 X 小时/周、错误率降低 Y%),不能量化的要说明原因
  6. 中文为主:除专有名词外,报告全程使用中文,专有名词首次出现时提供中文解释

输出后的提示

报告生成后,告知用户:

  1. 文件路径(主报告 + SVG 资源文件)
  2. 提示用户可以进一步询问:"哪个章节需要深入展开?"或"是否需要补充某个竞品对比?"

参考文件

详见 references/ 目录:

  • scoring-rubric.md — 各维度评分细则(1~5分标准)
  • report-examples.md — 示例报告片段(雷达图 SVG 模板、功能矩阵模板)

© digoal, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/skills_for_claude_web/product-review-report of digoal/blog.

  • SKILL.md
  • references/report-examples.md
  • references/scoring-rubric.md

Open the folder on GitHubat commit ad6fcb7

Compare with similar skills

Product Review Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Review Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Review Report this skilldigoal/blog8.6k—~889Automated safety check: PassGPL-2.0
Markdown Article FormatterJimLiu/baoyu-skills27k6 repos~3.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Obsidian MarkdownAtmosphere/atmosphere3.8k20 repos~1.3kAutomated safety check: PassApache-2.0
Crosspostingwasp-lang/wasp19k—~1.1kAutomated safety check: PassMIT
Gzh Designisjiamu/gzh-design-skill4k—~2.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    27k GitHub starsUsed in 6 repos~3.5k tokens
    Documents & OfficeAuto-check passed
  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Obsidian Markdown

    Atmosphere/atmosphere

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

    3.8k GitHub starsUsed in 20 repos~1.3k tokens
    Documents & OfficeAuto-check passed
  • Crossposting

    wasp-lang/wasp

    Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.

    19k GitHub stars~1.1k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Gzh Design

    isjiamu/gzh-design-skill

    微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…

    4k GitHub stars~2.2k tokensUpdated 2 days ago
    Documents & OfficeAuto-check passed
  • Review The Docs

    supabase/supabase

    Official

    Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).

    111k GitHub stars~4.6k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from digoal/blog

All 98 skills in this repo
  • 三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…

    8.6k GitHub stars~939 tokensUpdated 2 days ago
    Auto-check passed
  • Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…

    8.6k GitHub stars~4k tokensUpdated 2 days ago
    Auto-check passed
  • Digoal

    digoal/blog

    Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…

    8.6k GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed
  • 从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读,并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…

    8.6k GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…

    8.6k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed
  • Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.

    8.6k GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

Questions about Product Review Report

What does Product Review Report do?

编写专业产品评测报告,站在用户决策者与使用者双重视角深度评测产品。输入产品名称(以及可选的产品资料/链接、功能点、使用场景、竞品),自动搜集产品信息、竞品对比数据与行业数据,生成结论清晰、逻辑严谨、有理论依据与数据支撑、图文并茂的 Markdown 评测报告(SVG 图以外挂文件形式引用),输出到项目 markdown/…. Product Review Report is an agent skill from digoal/blog.

When should I use Product Review Report?

Product Review Report fits situations like: tasks that involve Markdown.

How do I install Product Review Report in Claude Code?

Run `npx skills add digoal/blog --skill product-review-report -a claude-code`. Or copy the skill folder (skills/skills_for_claude_web/product-review-report in digoal/blog) into .claude/skills/product-review-report in your project. Claude Code loads it when a task matches its description.

How do I install Product Review Report in Codex?

Run `npx skills add digoal/blog --skill product-review-report -a codex`. Or copy the skill folder (skills/skills_for_claude_web/product-review-report in digoal/blog) into .agents/skills/product-review-report in your project. Codex loads it when a task matches its description.

Can I use Product Review Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add digoal/blog --skill product-review-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-review-report, .gemini/skills/product-review-report, .github/skills/product-review-report and .opencode/skills/product-review-report in your project.

What does Product Review Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Review Report is instructions for the agent only.

Does Product Review Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Review Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Review Report use?

Product Review Report is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Review Report use?

About 889 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.4k tokens, read only when the agent opens those files.

What are the alternatives to Product Review Report?

Skills that share tags, products or a category with Product Review Report: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and Crossposting (wasp-lang/wasp, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Review Report?

digoal (a GitHub user) maintains it in digoal/blog, which has 8,588 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on October 9, 2026.

Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.