CtrlK
BlogDocsLog inGet started
Tessl Logo

trading-manual-writer

为"全品种操盘手册"系列撰写单个章节/小节。面向投资小白和散户,每次写一小节。输入小节标题和参考信息,输出图文并茂(含SVG插图)的Markdown文件,保存到项目markdown/目录。触发条件:用户提到"写操盘手册"、"写一节"、"写章节"、"散户操盘"、"金融工具讲解"、"写投资小白教程"、"帮我写操盘手册的XX章节",或提供了一个金融品种/操盘主题名称并希望生成教学内容。即使用户只说"帮我写黄金操盘那一章"或"可转债怎么讲给小白听",也应使用本skill。

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 detailed, highly actionable writing-process skill with concrete templates and a validation checklist, weakened by a ~250-line inlined book outline that hurts both conciseness and progressive disclosure. No bundle files are provided despite the skill being a strong candidate for reference splitting.

Suggestions

Move the 全书章节结构 outline (lines ~183–435) into a separate reference file (e.g. references/chapter_outline.md) and link to it with a one-line pointer; this would improve both conciseness and progressive_disclosure.

Convert the final 执行检查清单 into an inline validation step within the workflow (e.g. a 'Step 8: Validate' with a fix-and-recheck loop) so checkpoints are embedded in the sequence rather than only post-hoc.

Tighten redundant restatements between Step 2's 论证链 principles and the checklist's 论证链完整性 items to reduce token overlap.

DimensionReasoningScore

Conciseness

The core writing methodology (Steps 1–7, 论证链 template, SVG rules, 禁忌) is efficient and tight, but the inlined 全书章节结构 outline (~250 lines, over half the body) is bulk reference material that inflates token count and could be trimmed or moved. Not a 2 because it does not explain concepts Claude already knows; not a 4 because the chapter outline is a notable padded section.

3 / 5

Actionability

Provides copy-paste-ready templates (论证链 template, 框架 template, compliance statement text), concrete file-path/length/SVG specifications, and a worked output example — fully actionable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced and the closing 执行检查清单 provides explicit validation items ('必须全部通过'). Not a 5 because validation is a post-completion self-check rather than an inline validate→fix→retry checkpoint embedded within the steps.

4 / 5

Progressive Disclosure

Section structure is clear (## / ### headers), but no bundle files exist and the large chapter outline is inlined reference content that belongs in a separate file; references are absent rather than clearly signaled. Not a 2 because the document is well-sectioned, not a monolithic wall.

3 / 5

Total

15

/

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.

A highly specific, well-triggered description that clearly states what the skill does and when to use it, with concrete natural-language trigger phrases. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '撰写单个章节/小节', '输入小节标题和参考信息', '输出图文并茂(含SVG插图)的Markdown文件', '保存到项目markdown/目录' — with comprehensive coverage of inputs, outputs, and file handling.

5 / 5

Completeness

Explicitly answers both 'what' (write one section of a trading manual, output SVG-illustrated Markdown to markdown/) and 'when' (a dedicated '触发条件' clause with concrete trigger phrases plus an 'even if users only say...' extension).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say — '写操盘手册', '写一节', '写章节', '散户操盘', '帮我写黄金操盘那一章', '可转债怎么讲给小白听' — including synonyms and informal variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (per-section authoring of a retail-investor trading manual) with distinctive triggers; minimal overlap risk with generic writing or finance skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 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.