CtrlK
BlogDocsLog inGet started
Tessl Logo

article-writer

Multi-style article creation skill. Supports 5 writing styles (deep analysis, practical guide, story-driven, opinion, news brief), including complete workflow: material collection → outline → content → formatting. Activated when users mention "write article", "write post", "create", or "draft".

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./SKILLs/article-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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-structured, highly actionable writing workflow with explicit approval gates, data-integrity rules, and a final checklist. The two weaknesses are the fully monolithic layout — no references/ or scripts/ bundle, so all five style templates and the title process live in SKILL.md — and a few spots where material collection leans on external skills without a self-contained fallback.

Suggestions

Move the five per-style outline templates and the title-optimization process into per-style reference files (e.g. references/deep-analysis.md) linked from a compact style table, keeping SKILL.md as a lean overview.

Give a self-contained fallback for material collection when content-planner's script is unavailable (e.g. a plain web-search invocation) instead of only the external script path.

Trim the duplicated Use Cases column in the style table and fold the title-scoring percentages into the title reference to tighten token usage.

DimensionReasoningScore

Conciseness

The body is dense with house-style content Claude cannot infer — per-style outline templates with word counts, ❌/✅ rewrite examples, WeChat formatting hard rules — with almost no conceptual padding. Minor instances could be trimmed (the style table's Use Cases column duplicates Characteristics, and the title-scoring percentages add length), placing it at the 'efficient; minor instances of over-explanation' anchor rather than the lean anchor 5.

4 / 5

Actionability

Guidance is concrete and executable throughout: an exact command 'node "$SKILLS_ROOT/content-planner/scripts/wechat_search.js" "topic keywords" -n 10', a filename format 'drafts/YYYYMMDD_[topic-slug].md', a complete frontmatter example, and five full outline templates. It falls just short of anchor 5 because material collection depends on an external skill's script and 'Also use web-search skill' is a vague pointer.

4 / 5

Workflow Clarity

Nine clearly sequenced steps include an explicit mandatory validation gate ('This is a mandatory approval gate and cannot be skipped'), a data-integrity feedback loop ('mark [数据待确认] and confirm with user'), and a final quality checklist, matching the anchor for clear sequence with explicit validation, feedback loops, and checklists. This is a non-destructive drafting workflow, so the batch/destructive cap does not apply.

5 / 5

Progressive Disclosure

There are no bundle files at all — the five per-style templates, the title-optimization process, and all formatting standards are inlined in a single ~230-line SKILL.md. Sections are well-organized and navigable, but content that clearly belongs in separate per-style reference files is inline, matching 'some structure but could be better organized'. It is not anchor 2 because the body is well-sectioned with headers, not a monolithic wall.

3 / 5

Total

16

/

20

Passed

Description

80%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 that clearly states capability and explicit activation triggers in third person. Its main risks are the overly generic 'create' trigger, which creates conflict risk with unrelated creation tasks, and the absence of the natural-language (Chinese) trigger phrases that the body's use cases depend on.

Suggestions

Replace or qualify the generic 'create' trigger with writing-specific phrases (e.g. 'write an article about', '写一篇文章') to reduce conflict risk with unrelated creation requests.

Include the natural-language trigger variations the body relies on, such as '写一篇关于XX的文章' and '公众号文章', so Chinese-language requests activate the skill.

Add one clause naming the concrete output (a Markdown draft saved under drafts/ formatted for WeChat publishing) to close the remaining specificity gap.

DimensionReasoningScore

Specificity

The description names several concrete capabilities — 'Supports 5 writing styles (deep analysis, practical guide, story-driven, opinion, news brief)' and a concrete workflow 'material collection → outline → content → formatting' — but stops short of full coverage (no output format or WeChat target stated), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both what ('Multi-style article creation skill. Supports 5 writing styles ... including complete workflow') and when ('Activated when users mention "write article", "write post", "create", or "draft"') with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

'write article', 'write post', 'create', or 'draft' gives good natural keyword coverage, but 'create' is overly generic and the Chinese phrases the body's use cases actually rely on (e.g. '写一篇关于XX的文章') are missing, so it fits the 'good coverage; a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The trigger 'create' (and to a lesser extent 'draft') would fire on nearly any generative request, and the WeChat-specific niche that distinguishes this skill is only weakly signaled, matching 'somewhat specific but could still overlap with similar skills'. It is not anchor 4 because the overlap risk from 'create' extends well beyond closely related skills.

3 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
netease-youdao/LobsterAI
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.