CtrlK
BlogDocsLog inGet started
Tessl Logo

retail-trading-manual-writer

Write and save Chinese beginner-friendly paid manual subsections for "全品种操盘手册", a retail-investor education/subscription product covering the full 17-chapter + appendix outline from digoal's 2026-05-28 article. Use when the user provides a subsection title or asks to continue/complete the manual for 投资小白/散户, especially with triggers like 每次写一小节, 全品种操盘手册, 操盘手册, 知识付费, SVG图解, 第一性原理, markdown目录, 进度跟踪, or 散户金融工具.

68

Quality

82%

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

75%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 content is a well-structured, highly actionable instruction skill with a clear workflow, validation checkpoints, and proper use of a one-level reference file. Its main weakness is conciseness — the reasoning-chain method and a few load-the-outline instructions are repeated across sections and could be consolidated.

Suggestions

Consolidate the first-principles reasoning-chain method into one location (e.g., Workflow step 3) and reference it from Core Contract, Required Markdown Structure, and Evidence Rules instead of restating it each time.

Merge the adjacent "Always load references/manual-outline.md" and "Treat references/manual-outline.md as the source-of-truth chapter map" lines into a single instruction.

Add an explicit error-recovery loop in the Save-and-verify step (e.g., "If a referenced SVG path is missing, recreate it before re-saving the Markdown") to lift workflow clarity to 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining finance basics Claude already knows, but the first-principles reasoning-chain method is restated across Core Contract, Workflow step 3, Required Markdown Structure, and Evidence Rules, and adjacent lines like "Always load references/manual-outline.md" and "Treat references/manual-outline.md as the source-of-truth chapter map" are redundant.

3 / 5

Actionability

Guidance is highly concrete and executable for an instruction-only skill: explicit file layout, a copy-paste markdown structure template, named SVG file conventions, a progress-file table format, and crisp do/don't compliance lists with specific examples.

5 / 5

Workflow Clarity

A clear six-step workflow with a dedicated Save-and-verify step containing checkpoints ("Check every referenced SVG path exists", "Check the Markdown contains only one subsection") plus a Quality Bar checklist; held back from 5 because error-recovery feedback loops are implicit rather than explicit (no "if check fails, redo" path).

4 / 5

Progressive Disclosure

Structure is clean with clearly signaled one-level-deep references ("Always load references/manual-outline.md before drafting") and the outline correctly offloaded to a real bundle file; the body is fairly long (~250 lines) and could push some templates to references, keeping it just below 5.

4 / 5

Total

16

/

20

Passed

Description

90%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 strong: it clearly states both what the skill does and when to invoke it, with a rich set of natural Chinese trigger terms and a distinctive niche. The only minor weakness is specificity — the action list in the description itself is limited to write/save while richer capabilities are described only in the body.

DimensionReasoningScore

Specificity

Phrases like "Write and save Chinese beginner-friendly paid manual subsections" name the domain and two concrete actions (write, save), but the action list is not comprehensive — finer-grained operations (diagramming, progress tracking, sourcing) live in the body rather than the description.

3 / 5

Completeness

It explicitly states what ("Write and save Chinese beginner-friendly paid manual subsections...") and when ("Use when the user provides a subsection title or asks to continue/complete the manual..."), with concrete trigger phrases attached.

5 / 5

Trigger Term Quality

An extensive, natural trigger list ("每次写一小节, 全品种操盘手册, 操盘手册, 知识付费, SVG图解, 第一性原理, markdown目录, 进度跟踪, 散户金融工具") plus "投资小白/散户" covers synonyms and the exact phrases a user would say.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined (a specific Chinese retail-investor paid manual product tied to a named article) with distinctive triggers, making conflict with unrelated skills minimal.

5 / 5

Total

18

/

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: 1 missing, 1 deeper-than-1-level

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.