CtrlK
BlogDocsLog inGet started
Tessl Logo

digoal-read-think-writer

以 digoal/德哥 的第一人称口吻重写一篇文章。流程是:先吃透原文(必要时用 mcp__MiniMax__web_search 拓展资料库),再用德哥的语气重新讲一遍,输出 markdown 到当前项目的 `markdown/` 目录(SVG 图存到 `markdown/svg/`,文中以 `![描述](svg/xxx.svg)` 引用)。风格有活人感,不要套用标准写作框架;匹配原文挑文体(随想/知识分享/深度洞察/吃瓜/大事件/吐槽);开头必须有钩子(惊讶/惊喜/反直觉);句子短,一行一句,适合口播;最多 3 段,能 1 段搞定就 1 段。类比时优先用数据库、AI、PG 内核、向量搜索、RAG、PG 运维这些德哥熟悉的领域。适用于:用德哥风格重写一篇公众号文章 / 把一份英文 paper/digest/blog 改写成中文公众号体 / 用德哥第一人称讲一件行业大事 / 让德哥吐槽某个产品或观点。

75

Quality

94%

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.

The body is a strongly actionable, well-sequenced workflow with explicit validation and a self-check feedback loop, and it delegates voice/style detail to two clearly signaled reference files. The main gaps are minor: duplicated trigger and web-search rules that could be merged, and style constraints inlined in the body that partly duplicate the reference files.

Suggestions

Merge 「触发词速查」 into 「何时触发」 (or vice versa) and state the mcp__MiniMax__web_search rule once — both currently appear twice in the body.

Move the inlined hook-candidate list, sentence-length rules, and analogy priority list into references/digoal-voice.md or references/style-blueprints.md, keeping only the top-level rule plus a pointer in SKILL.md.

Trim the repeated analogy-domain enumeration in Step 2 to a pointer at section 3.4's priority list.

DimensionReasoningScore

Conciseness

The body stays on non-obvious material (voice rules, genre selection, hook types, a worked style sample) and never explains things Claude already knows, which is above the score-3 anchor. But there is trimmable redundancy: trigger examples appear in both 「何时触发」 and 「触发词速查」, the "必须用 mcp__MiniMax__web_search / 禁止 WebSearch" rule is stated twice in the body, and the analogy-domain list repeats across Step 2 and 3.4 — minor over-explanation rather than the lean score-5 fit.

4 / 5

Actionability

Guidance is concrete and executable throughout: exact thresholds ("单句尽量 ≤ 25 字", "最多搜 3-5 个关键词", "最多 3 段"), exact paths (`markdown/`, `markdown/svg/`), a literal reference format `![描述](svg/xxx.svg)`, a ready Mermaid snippet, a worked style example, and example filenames. For an instruction-only writing skill this matches the score-5 'fully executable, covers common cases' anchor.

5 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced (get source → decide on supplementary search → digest → write → save file → self-check), each with explicit decision criteria (four concrete conditions for opening a search) and gates ("消化不充分,不要动笔", "不要覆盖已有同名文件"). Step 5 is an explicit validate-and-fix feedback loop ("跑完下面这份清单,不通过就改"), matching the score-5 anchor including error recovery.

5 / 5

Progressive Disclosure

Two real, one-level-deep references (`references/digoal-voice.md`, `references/style-blueprints.md`) are listed under 「资源」 with what each contains and when to read it — well signaled. However, the body still inlines substantial style detail that overlaps the delegated material (genre→文体 mapping, hook candidate list, sentence/paragraph rules, the full analogy priority list), so placement is good but not the cleanly split score-5 fit.

4 / 5

Total

18

/

20

Passed

Description

100%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 is explicit about both capability and trigger conditions, with concrete output paths, style constraints, and a list of natural user phrasings that make it highly distinguishable from adjacent skills. Its only weakness is density: it packs many style rules into the description, which makes it long even though every clause is concrete.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with specifics: "以 digoal/德哥 的第一人称口吻重写一篇文章", "必要时用 mcp__MiniMax__web_search 拓展资料库", "输出 markdown 到当前项目的 `markdown/` 目录(SVG 图存到 `markdown/svg/`…)", plus concrete constraints (hooks, ≤25-char sentences, ≤3 paragraphs, PG-domain analogies). Coverage of the skill's behavior is comprehensive; it is not below the score-4 anchor, which allows 'minor gaps in coverage'.

5 / 5

Completeness

Both 'what' and 'when' are explicit: the opening sentence states the full pipeline (吃透原文 → 德哥语气重写 → 输出 markdown), and the "适用于:…" clause gives concrete trigger scenarios, matching the score-5 anchor that requires both answers with concrete trigger phrases. The 'when' is explicit, not weakly implied as at score 4.

5 / 5

Trigger Term Quality

The trailing "适用于:" list gives natural user phrasings — "用德哥风格重写一篇公众号文章", "把一份英文 paper/digest/blog 改写成中文公众号体", "用德哥第一人称讲一件行业大事", "让德哥吐槽某个产品或观点" — covering synonyms across the persona-rewrite space (重写/改写/讲/吐槽, 公众号/paper/digest/blog). This matches the score-5 anchor for comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — rewriting source material in digoal's first-person WeChat-column voice — and every trigger phrase names 德哥/digoal explicitly, so it cannot fire for generic writing, translation, or technical Q&A skills. This fits the score-5 'clear niche with distinct triggers' anchor.

5 / 5

Total

20

/

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: 2 missing

Warning

Total

15

/

16

Passed

Repository
digoal/blog
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.