CtrlK
BlogDocsLog inGet started
Tessl Logo

huashu-article-edit

标准化文章编辑流程,确保修改范围明确、进度可追踪、变更有记录。当用户说"编辑文章"、"修改文章"、"调整内容"、"改一下这篇"时使用此技能。

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./huashu-article-edit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 clearly structured, actionable editing workflow with a useful user-confirmation checkpoint and progress reporting. Its main drawbacks are an unrelated promotional footer that wastes tokens, an aging 'last updated' date, and a dangling reference to a SHARED-RULES.md file not present in the skill bundle.

Suggestions

Remove the promotional footer ('花叔出品' block) and the '最后更新: 2026-02-06' line, or move date-stamped info into a deprecated/old-patterns section — neither serves the editing task.

In Step 3, name the concrete editing mechanism (e.g. the Edit/Write tool) so the save-and-edit loop is unambiguous and copy-paste ready.

Either include SHARED-RULES.md in the bundle (references/ or assets/) or remove the dangling reference to it in the '保持风格' principle.

DimensionReasoningScore

Conciseness

The core workflow is lean and assumes Claude's competence, but the trailing promotional footer ('花叔出品', '30万+粉丝', '小猫补光灯...') and the time-sensitive '最后更新: 2026-02-06' line are unrelated padding that do not earn their tokens.

3 / 5

Actionability

Provides concrete, sequenced guidance (Read the article, list edits with location/type/content, incremental save, progress template) with a copy-ready progress report block; the only gap is that the actual editing mechanism (e.g. the Edit tool) is not named in Step 3.

4 / 5

Workflow Clarity

Four clearly sequenced steps with an explicit validation checkpoint ('等待用户确认范围后再动手') and progress reporting every 3-5 edits; lacks a formal validate->fix->retry error-recovery loop, so it stops short of a 5.

4 / 5

Progressive Disclosure

Well-organized sections for a simple under-50-line skill, with a clearly signaled one-level reference to SHARED-RULES.md; the reference file is not present in the bundle, a minor gap that keeps it below 5.

4 / 5

Total

15

/

20

Passed

Description

78%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 well-constructed description that clearly states purpose and provides explicit, natural trigger phrases for when to use it. The main weakness is that the 'what' is framed as abstract process goals rather than concrete enumerated actions.

DimensionReasoningScore

Specificity

Names the domain (文章编辑) and conveys process goals ('修改范围明确、进度可追踪、变更有记录'), but these are abstract goals rather than concrete, enumerated actions; coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both 'what' (标准化文章编辑流程 ensuring clear scope, trackable progress, recorded changes) and 'when' with concrete quoted trigger phrases.

5 / 5

Trigger Term Quality

Includes several natural trigger phrases users would actually say ('编辑文章', '修改文章', '调整内容', '改一下这篇'), giving good keyword coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear article-editing niche with specific triggers; minor overlap risk with the related proofreading/审校 skill referenced in the body.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alchaincyf/huashu-skills
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.