CtrlK
BlogDocsLog inGet started
Tessl Logo

book-note-writer

生成深度读书笔记的专用 Skill。输入书籍的豆瓣链接(或书名+作者),自动搜索书籍信息、高质量书评、学术评价等素材,结合 Claude 的深度思考,生成图文并茂、观点鲜明、适合分享的读书笔记,以 Markdown 格式保存到项目 markdown/ 目录。触发条件:用户提供豆瓣链接、提到"读书笔记"、"书评"、"帮我分析这本书"、"写一篇XX书的笔记",或任何希望深度理解一本书的场景。即使用户只说"帮我写一下这本书的感悟",也应使用本 skill。

73

Quality

90%

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

85%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-engineered writing-workflow skill: highly actionable instructions, explicit checkpoints, and strong fallback handling for sparse-material books. Its main structural flaw is that the one bundled reference file is never referenced from the body, and its inlined source-priority list duplicates it.

Suggestions

Replace or augment the §1.2 优先级 list with an explicit pointer, e.g. 「完整来源列表见 [high-quality-sources.md](references/high-quality-sources.md)」, so the bundled file is actually loaded.

Trim the 「Skill 定位」 preamble and collapse the three similar 检查点 blocks into one reusable checkpoint format to reduce token weight.

Consider moving the ~100-line note template (§3.2) into references/ as a template file, keeping only a section outline plus a link in SKILL.md.

DimensionReasoningScore

Conciseness

The body is largely task-specific guidance (copy-paste search queries, a full note template, writing formulas) with almost no explanation of concepts Claude already knows, but sections like 「Skill 定位」("这不是书籍摘要…而是**一次思想的重建与对话**") and the three near-identical 检查点 blocks add prose that could be trimmed. Not a 5 because there is genuine tightening headroom; not a 3 because nearly every line carries skill-specific instruction.

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact search query strings ("{书名} {作者} 书评", "{BookTitle} {Author} review"), concrete tool calls (`web_fetch(url=豆瓣链接)`), a complete 10-section markdown template with word counts, explicit file-naming examples (markdown/sapiens_2024.md), and worked formulas with examples for the 「批判与反思」 and 「举一反三」 sections. This matches the 'fully executable, specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

Steps 0–8 are clearly sequenced with three explicit validation checkpoints (素材确认, 分析完成确认, 初稿确认 before saving), a final 质量检查清单, and genuine feedback loops for error recovery (ambiguous-input confirmation, 冷门书 handling, English-keyword fallback, 豆瓣抓取失败 fallback). This is the anchor-5 pattern of clear sequence + explicit validation + error recovery.

5 / 5

Progressive Disclosure

The bundle contains references/high-quality-sources.md, but the body never mentions or links it — the source guidance is instead inlined as the 优先级 list in §1.2 ("学术评论… 知名媒体书评… 豆瓣长评…"), so the reference file is undiscoverable dead weight. Structure and section organization are good, but the reference is not clearly signaled and content that already lives in a separate file is duplicated inline, which matches the 'references present but not clearly signaled; content that should be separate is inline' anchor.

3 / 5

Total

17

/

20

Passed

Description

96%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.

An excellent description: concrete third-person capabilities, an explicit trigger clause with natural user phrasings and edge-case guidance, and a clearly scoped niche. The only weakness is mild over-breadth in the catch-all 'any scenario wanting to deeply understand a book' phrasing, which slightly raises conflict risk.

DimensionReasoningScore

Specificity

It lists multiple concrete actions with comprehensive coverage in third person: 「自动搜索书籍信息、高质量书评、学术评价等素材」, 「生成图文并茂、观点鲜明…的读书笔记」, 「以 Markdown 格式保存到项目 markdown/ 目录」, plus input handling (豆瓣链接 or 书名+作者). This matches the 'multiple specific concrete actions; comprehensive coverage' anchor; it is not a 4 because no meaningful capability is left unnamed.

5 / 5

Completeness

It explicitly answers both questions: the 'what' (search materials, generate an illustrated opinionated note, save as Markdown to markdown/) and the 'when' via an explicit 「触发条件:」 clause listing concrete trigger phrases. It even adds boundary guidance (「即使用户只说…也应使用本 skill」), which exceeds the anchor-5 example.

5 / 5

Trigger Term Quality

It includes the natural phrases a Chinese-speaking user would actually say: 「读书笔记」「书评」「帮我分析这本书」「写一篇XX书的笔记」and even the edge case 「帮我写一下这本书的感悟」, plus the concrete trigger of providing a 豆瓣链接. Coverage including synonyms is comprehensive, matching the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (deep reading notes for a specific book, anchored by 豆瓣/书名 triggers), so it won't collide with unrelated skills. However the fairly generic phrases 「帮我分析这本书」 and 「任何希望深度理解一本书的场景」 create minor overlap risk with general book-analysis or summary skills, matching 'mostly distinct; minor overlap risk' rather than the fully distinct anchor-5 pattern.

4 / 5

Total

19

/

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
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.