CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-prompt-convert

在 Skill(SKILL.md)与 Prompt(聊天框指令)两种格式之间相互转换。支持 Skill→Prompt 与 Prompt→Skill 双向转换,保持核心信息零丢失。当用户提到 Skill 转 Prompt、Prompt 转 Skill、格式互转、SKILL.md 转换时使用。

65

Quality

77%

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 ./skills/skill-prompt-convert/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 lean, actionable, well-structured conversion skill with a clear step sequence. The main weakness is missing explicit validation checkpoints — the zero-loss and standard-format requirements are asserted as rules rather than verified within the workflow.

Suggestions

Add an explicit verification step (e.g., Step 2.5 / a checklist) where Claude checks the converted output against the source for zero information loss and confirms it conforms to the standard Skill YAML format before delivering Part 2.

Include one short end-to-end worked example (a minimal SKILL.md → Prompt and Prompt → SKILL.md pair) to anchor the abstract field-mapping rules in concrete output.

Tighten the 注意事项 list by merging the overlapping 'description 质量', 'Skill 正文结构', and '标准 Skill 格式' bullets into a single concise format-checklist.

DimensionReasoningScore

Conciseness

The body is efficient and free of concept padding, though the 注意事项 rule list is somewhat long and could be trimmed further.

4 / 5

Actionability

Concrete field-mapping rules, naming examples, and a YAML template make the guidance mostly executable, though it lacks a full end-to-end worked conversion example.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Step 1→2→3 with direction and output splits), but validation checkpoints are implicit — '信息零丢失' and conformance to '标准 Skill 格式' are stated as goals/rules without an explicit verify step in the workflow.

3 / 5

Progressive Disclosure

No bundle files are needed for this under-50-line single-purpose skill, and the body is well-organized into clearly headed sections, satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

82%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, well-targeted description that clearly states both the capability and explicit trigger conditions with natural phrasings. Its main limitation is that the 'what' boils down to a single (bidirectional) action rather than a list of several concrete operations.

DimensionReasoningScore

Specificity

The description names the domain (Skill/Prompt conversion) and commits to two concrete actions (bidirectional conversion, core-info preservation), but it is essentially a single capability stated both directions rather than several distinct actions.

3 / 5

Completeness

It explicitly answers both 'what' (bidirectional Skill↔Prompt conversion preserving core info) and 'when' via concrete trigger phrases ('当用户提到...时使用').

5 / 5

Trigger Term Quality

It explicitly enumerates natural user phrasings ('Skill 转 Prompt', 'Prompt 转 Skill', '格式互转', 'SKILL.md 转换') with a synonym, giving good keyword coverage, though a few additional synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The Skill↔Prompt format-conversion niche is narrow with distinct trigger phrases, making conflict with other skills minimal.

5 / 5

Total

17

/

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
xstongxue/best-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.