CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-workflow

开发流程五步法。支持需求理解、方案设计、代码实现、代码审查、Bug 修复。当用户提到「需求分析」「方案设计」「代码实现」「代码审查」「理解需求」「技术设计」「开始写代码」「Review」「检查代码」「bug」「报错」「崩溃」「异常」「出错了」时使用。

57

Quality

66%

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/dev-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is a well-organized overview with clear sequencing and a sensible reference table, but it is undermined by broken references to missing files, redundant keyword repetition, and no validation step around the automatic disk-writing operation. As written, the skill cannot fully execute because the referenced per-stage details are absent.

Suggestions

Provide the referenced reference/requirement.md, design.md, implementation.md, review.md, and bug-fix.md files (or inline the per-stage guidance) so the skill is actionable as written.

Add a validation/verification checkpoint before and after the automatic 落盘 write (e.g., confirm the output dir, verify the write succeeded, surface errors) since it is a batch file operation.

Remove the redundant '使用时机' keyword list and the table's trigger column, keeping triggers in one place to reduce token cost.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining basic concepts, but the trigger keyword list is repeated three times (description, the '使用时机' section, and the table column), which is redundant and could be tightened.

2 / 3

Actionability

The 落盘 rules give concrete file paths and formatting rules, but the core per-stage execution guidance delegates to 'reference/*.md' files that are not present, leaving the actual instructions incomplete and non-actionable as written.

2 / 3

Workflow Clarity

The five stages are clearly sequenced (Step 1 → Step 3) with stage-transition guidance, but the automatic file-writing (落盘) batch operation has no validation or verification checkpoint, which caps workflow clarity per the destructive/batch guideline.

2 / 3

Progressive Disclosure

The body uses a clean table with one-level-deep references to reference/*.md files, but those referenced files do not exist in any bundle directory, so the navigation is broken and the disclosure structure is not actually backed by real content.

2 / 3

Total

8

/

12

Passed

Description

82%

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 is well-structured with a clear what-and-when pattern and rich natural trigger terms, but its capability list reads as workflow phase labels and its triggers are broad enough to risk overlap with other coding skills. It uses neutral third-person voice with no first/second-person slips.

Suggestions

Tighten broad triggers like 'bug', '报错', '异常', '开始写代码' by tying them to the full five-step workflow context so they don't conflict with single-purpose coding skills.

Replace abstract phase labels with one or two concrete actions per stage to lift specificity from stage names to tangible operations.

DimensionReasoningScore

Specificity

The description names the five workflow stages ('需求理解、方案设计、代码实现、代码审查、Bug 修复'), which cover its domain comprehensively, but these are abstract phase labels rather than concrete executable actions like 'extract text' or 'fill forms'.

2 / 3

Completeness

It states both what the skill does ('开发流程五步法...支持...') and an explicit when-to-use clause ('当用户提到...时使用'), clearly answering both what and when.

3 / 3

Trigger Term Quality

It lists many natural terms a user would actually say ('需求分析', '开始写代码', 'Review', '检查代码', 'bug', '报错', '崩溃', '异常', '出错了'), giving strong coverage of common phrasings across all five stages.

3 / 3

Distinctiveness Conflict Risk

The five-stage niche is identifiable, but extremely broad triggers like 'bug', '报错', '异常', and '开始写代码' would overlap with many general coding skills and could fire for the wrong skill.

2 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

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.