CtrlK
BlogDocsLog inGet started
Tessl Logo

huashu-prompt-save

自动识别Prompt类型并分类保存(技术/内容/教学/产品/通用)。当用户提到"保存prompt"、"记录prompt"、"整理prompt"时使用。

63

Quality

73%

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 ./huashu-prompt-save/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 compact, well-structured instruction skill with concrete save format and naming conventions. Its main weakness is the absence of validation/verification checkpoints for a batch file-writing workflow, which limits workflow clarity.

Suggestions

Add a verification checkpoint after saving: confirm the file was written and that INDEX.md now contains the new entry before reporting success.

Add a dedup/conflict rule for the auto-incrementing 序号 (e.g., scan existing files to determine the next number rather than guessing), since batch writes risk collisions.

Remove the author-signature trailer; it is off-topic padding that consumes context tokens without aiding task execution.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence—no padding explaining what prompts or indexes are—though the author-signature trailer ("花叔出品 | AI Native Coder...") is off-topic content that does not earn its place.

4 / 5

Actionability

Provides concrete file-naming pattern (prompt-[序号]-[标题].md), target directory, a full save-format template, and INDEX-update guidance; minor gaps because title/tag rules are guidelines rather than mechanical specs.

4 / 5

Workflow Clarity

A clear 5-step execution flow is present, but this batch file-writing operation has no validation/verification checkpoint (no verify-saved, no dedup-check for the auto-incrementing 序号, no INDEX-update confirmation), which the rubric caps at 3.

3 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with well-organized sections and no need for bundle files; the single referenced path is an external management rule, so the structure is appropriately flat and navigable.

5 / 5

Total

16

/

20

Passed

Description

75%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 concise, third-person description that names a specific niche and concrete actions with explicit trigger phrases. It clearly answers both what and when, with only minor room for additional synonyms and edge-case guidance.

DimensionReasoningScore

Specificity

Names the domain (prompt classification/saving) plus concrete actions (识别类型, 分类保存) and enumerates five concrete categories (技术/内容/教学/产品/通用), giving several specific actions with minor gaps rather than comprehensive coverage.

4 / 5

Completeness

Clearly states what it does (识别Prompt类型并分类保存) and gives an explicit "when" clause ("当用户提到...时使用"); the "when" is concrete but could be more specific about ambiguous cases.

4 / 5

Trigger Term Quality

Provides three natural phrases users would actually say ("保存prompt", "记录prompt", "整理prompt") with good coverage, though it lacks broader synonyms or format variations that would round out to a 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (prompt archiving/classification) with explicit trigger phrases, making it mostly distinct with only minor overlap risk against general note-taking skills.

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.