CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 散户金融工具.

69

Quality

87%

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

81%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 highly actionable, well-structured skill body: concrete templates, named files, explicit validation steps, and correct use of a single one-level-deep reference for the bulk outline. The main cost is redundancy — several rule sets (progress tracking, SVG standards, verification) are repeated or split across sections, inflating token cost without adding information.

Suggestions

Consolidate the progress-file rules currently spread across Core Contract, Output Files, Workflow step 1, and Progress File Format into a single section, and state the outline-loading rule once instead of the back-to-back 'Always load' / 'Treat as source-of-truth' pair.

Merge Workflow step 4's SVG design requirements into the 'SVG Standards' section (or reference it from the workflow) so diagram rules live in one place.

Trim the Quality Bar to only items not already enforced in Workflow step 6 (e.g., compliance and reasoning-chain checks), since most verification bullets currently duplicate the save-and-verify step.

DimensionReasoningScore

Conciseness

The body is almost entirely actionable instruction (no explanations of concepts Claude already knows), but it is noticeably redundant and could be tightened: the outline-loading rule is stated twice back-to-back ('Always load references/manual-outline.md' / 'Treat references/manual-outline.md as the source-of-truth'), SVG guidance is duplicated between Workflow step 4 and 'SVG Standards', progress-file rules are spread across Core Contract, Output Files, Workflow, and 'Progress File Format', and the Quality Bar checklist largely restates step 6's verification. This fits the level 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') better than level 4's 'minor instances', since the redundancy spans several sections of a ~250-line body.

3 / 5

Actionability

Guidance is fully concrete and copy-paste ready: an exact output file layout, slug-derivation rules, the complete markdown article template with all required headings, named SVG files ('01-logic-map.svg', '02-decision-tree.svg', ...), SVG technical constraints (xmlns, viewBox, no foreignObject, no remote fonts), and a fully specified progress-file table with example rows. This matches level 5's 'copy-paste ready' with common cases covered; there are no pseudocode or vague directives.

5 / 5

Workflow Clarity

The six-step workflow is clearly sequenced with explicit validation checkpoints: title-to-outline matching with a clarification-question fallback, evidence verification before drafting, save-SVGs-then-Markdown ordering, path-existence checks, and 'Do not mark a subsection done until its Markdown file exists and its SVG references have been checked'. A separate Quality Bar checklist and error-recovery paths (ambiguous title -> ask; already-written title -> ask whether to revise) match the level 5 anchor with feedback loops and a final checklist.

5 / 5

Progressive Disclosure

The bundle is used well: the 17KB chapter outline is correctly externalized to references/manual-outline.md (verified to exist and match the described 17-chapter map), the reference is one level deep and clearly signaled ('Always load ... before drafting'), and the always-needed templates (article structure, progress table) are appropriately inline. It falls short of level 5 because organization has gaps: the same rules (progress tracking, SVG standards, verification) are scattered across multiple sections instead of living in one clearly navigable place, which is the 'minor organization gaps' of level 4.

4 / 5

Total

17

/

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.

A strong description: explicit what-and-when structure with an extensive list of natural Chinese trigger phrases and a highly distinctive niche. The only weakness is that capability coverage is narrower than the skill actually offers — SVG diagram creation, progress-file maintenance, and the reasoning-chain methodology are body-only and absent from the description.

DimensionReasoningScore

Specificity

The description names one clear capability pair — 'Write and save Chinese beginner-friendly paid manual subsections' — plus rich domain framing ('17-chapter + appendix outline', 'retail-investor education/subscription product'), which matches the anchor for 1-2 concrete actions with coverage gaps. It does not list other real capabilities of the skill (SVG diagram generation, progress tracking, first-principles derivation), so it is not the 'several specific actions' of level 4.

3 / 5

Completeness

It explicitly answers both what ('Write and save Chinese beginner-friendly paid manual subsections for 全品种操盘手册...') and when ('Use when the user provides a subsection title or asks to continue/complete the manual...') with concrete trigger phrases, exactly matching the level 5 anchor. Level 4 would require the 'when' clause to be less explicit or specific, which is not the case here.

5 / 5

Trigger Term Quality

It provides comprehensive natural triggers a user would actually say: '每次写一小节', '全品种操盘手册', '操盘手册', '知识付费', 'SVG图解', '第一性原理', 'markdown目录', '进度跟踪', '散户金融工具', plus scenario phrases like 'continue/complete the manual' and audience terms '投资小白/散户'. This covers synonyms and phrasing variants at level 5; level 4's 'a few natural terms missing' understates the breadth of the list.

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — a specific named Chinese paid-manual product (全品种操盘手册) with a unique outline and distinctive Chinese trigger phrases — so risk of triggering for the wrong skill is minimal, matching the level 5 anchor. It is far more distinct than the 'mostly distinct; minor overlap risk' of level 4.

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.

Validation — 15 / 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

Path

skills/retail-trading-manual-writer/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.