CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-neutral-advisor

以第三方中立顾问身份,围绕某个产品近1个月内的最新动态,撰写适合公众号发布的简短深度文章(不超过4屏)。 触发条件:用户输入产品名称并希望生成顾问视角的分析文章,提到"帮我写篇XX的文章"、"分析一下XX最近的动态"、"以顾问角度写XX"、"产品影响力文章"、"公众号文章"、"帮我写XX的点评"、"XX最近怎么样"等。 即使用户只说"帮我写一篇关于XX的文章",只要意图是产品评析,也应使用本 skill。 输出为 Markdown 文件,保存到当前项目 markdown/ 目录,适合手机端阅读,第一人称,中立有据,无AI生成痕迹。

73

Quality

92%

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

88%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-crafted writing skill: the workflow is a clearly sequenced five-step process with a gating self-check checklist, and the guidance is unusually concrete (exact search strings, word budgets, output path template, style do/don't examples). The only notable gaps are minor — a couple of decorative blocks to trim and some auxiliary content (chart guide, style examples) that could live in a separate reference file for progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — word budgets per section, a standards table, and literal search templates — with no explanation of concepts Claude already knows. It falls short of level 5 because a few blocks are decorative and could be trimmed: the '顾问的价值 = 独立判断…' aphorism and the trivial Mermaid/ASCII demo snippets in the chart guide; it is well above level 3's 'some unnecessary explanation'.

4 / 5

Actionability

Guidance is copy-ready and covers the common case: exact search queries ('[产品名] 最新动态 2025', an English variant, competitor and controversy searches), per-section word counts, a writing-standards table, an output path pattern './markdown/[产品名]-advisor-[YYYYMMDD].md', and a worked wrong/right style contrast. As an instruction-only skill with no code, the rubric's code penalty does not apply and the guidance fully matches the level-5 anchor.

5 / 5

Workflow Clarity

A clear five-step sequence (理解产品 → 搜索 → 构建顾问视角 → 撰写 → 保存) with an ordered search strategy and an explicit validation gate: a pre-output self-check checklist ('在输出前,逐项确认… 全部 ✅ 才可输出') that blocks output until every item passes. This matches the level-5 anchor's checklists and checkpoints; the operation is not destructive/batch, so no cap applies.

5 / 5

Progressive Disclosure

The skill is a single well-organized file (~130 lines) with clear section headers and no nested references; no bundle files exist, so nothing dangles. It is not level 5 under the rubric's short-skill guidance (over 50 lines), and minor content such as the chart-usage guide and style examples could be split into a separate reference file — matching level 4's 'good structure; minor organization gaps' rather than level 5's ideal split.

4 / 5

Total

18

/

20

Passed

Description

91%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: it explicitly answers both what and when with abundant natural trigger phrases in the user's language, and specifies concrete output constraints (length, format, save path, voice). The main gap is that it omits the search/verification capability and its broad claim on generic 'write me an article' requests slightly raises overlap risk with general writing skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions and outputs: writing a third-party neutral consultant article on a product's last-month news (≤4 screens), outputting a Markdown file saved to the markdown/ directory, mobile-friendly formatting, first person, and evidence-backed neutrality. It is not level 5 because capabilities exercised in the body (web search for verification, chart generation) are not mentioned; it clearly exceeds level 3's 1-2 concrete actions.

4 / 5

Completeness

Both 'what' (writes a short, deep, neutral product-analysis article for 公众号 publication) and 'when' are explicitly answered, with a dedicated '触发条件' clause listing concrete trigger phrases — mirroring the rubric's level-5 good example. It is not level 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Seven natural user phrasings ('帮我写篇XX的文章', '分析一下XX最近的动态', '以顾问角度写XX', '公众号文章', '帮我写XX的点评', 'XX最近怎么样') plus an explicit catch-all for the vague case ('即使用户只说"帮我写一篇关于XX的文章"…也应使用本 skill') give comprehensive natural-term and synonym coverage, matching the level-5 anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (product-review article for 公众号, neutral consultant voice), so conflict risk is low, but the trigger '帮我写篇XX的文章' and the explicit claim on vague article-writing requests create minor overlap with generic writing skills — matching level 4 rather than level 5's 'minimal conflict risk', and clearly above level 3's overlap with similar skills.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

digoal/blog

Path

skills/skills_for_claude_web/product-neutral-advisor/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.