huashu-article-edit

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./huashu-article-edit/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured editing workflow with a useful progress template, but it lacks a post-edit verification step for a batch/destructive operation, leaves the save mechanism unspecified, and carries promotional footer content that wastes tokens.

Suggestions

Add an explicit verification step after editing (e.g., re-Read the article and confirm each listed change landed) before reporting completion, since batch edits are destructive.

Specify the save mechanism concretely (e.g., 'use Edit/Write to save after each batch') instead of the generic '保存文件'.

Remove the promotional signature footer and the '最后更新' date — they add tokens without aiding execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and well-organized, but the promotional footer ("花叔出品 \| 30万+粉丝…") and obvious guidance like "快速理解文章主题、结构、当前状态" add tokens that do not help Claude, matching the score-2 anchor of being mostly efficient with some unnecessary content.	2 / 3
Actionability	Concrete elements exist (use the Read tool, a progress-report template, save after each batch), but key actions are underspecified — which tool to save with (Edit/Write) and how to surface the modification list are described abstractly, matching the score-2 anchor of some concrete guidance with missing details.	2 / 3
Workflow Clarity	The four steps are clearly sequenced with a pre-edit confirmation checkpoint and periodic progress reports, but this batch editing of an existing article has no post-edit verification/re-read step; per the rubric, missing validation in batch/destructive operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files and no genuine need for external references, and its content is organized into clearly labeled sections, so it meets the score-3 bar for simple skills with well-organized sections.	3 / 3
	Total	9 / 12 Passed

Description

82%Weight 40%Scale 1-3

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 cleanly covers what and when with natural trigger phrases, but its capability list reads as assurances rather than concrete actions and some triggers are generic enough to risk overlap with sibling skills.

Suggestions

Replace abstract assurances ("确保修改范围明确、进度可追踪、变更有记录") with concrete actions such as '列出修改项、增量编辑、按批次保存、汇报进度'.

Tighten generic triggers like "调整内容"、"改一下这篇" toward article-specific phrasing to reduce overlap with other editing skills.

Dimension	Reasoning	Score
Specificity	Names the domain (article editing) and capabilities (范围明确、进度可追踪、变更有记录), but these are stated as abstract assurances rather than concrete user-facing actions like 'revise paragraphs' or 'restructure sections', matching the score-2 anchor of naming domain and some actions without being comprehensive.	2 / 3
Completeness	Explicitly answers both what (标准化文章编辑流程，确保修改范围明确、进度可追踪、变更有记录) and when (当用户说…时使用此技能), matching the score-3 anchor with an explicit 'Use when…' clause.	3 / 3
Trigger Term Quality	Provides natural phrases a user would actually say — "编辑文章"、"修改文章"、"调整内容"、"改一下这篇" — giving good coverage of common variations, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The article-editing niche is fairly clear, but generic triggers like "调整内容" and "改一下这篇" could overlap with other editing or content skills, matching the score-2 anchor of being somewhat specific but still able to overlap.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alchaincyf/huashu-skills
Path: huashu-article-edit/SKILL.md
Commit: 35e7cf3

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.