CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev-workflow

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

64

Quality

80%

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

Quality

Content

65%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.

The body is a concise, well-organized orchestrator with concrete file-persistence rules, but it relies entirely on five reference files that are missing from the bundle, and its destructive落盘 workflow lacks validation checkpoints. These two gaps cap both workflow clarity and progressive disclosure at 3.

Suggestions

Ship the five referenced reference/*.md files (or inline the per-phase guidance) so the progressive-disclosure routing actually resolves.

Add a validation checkpoint to the落盘 workflow (e.g. verify the write/archive succeeded before declaring the step complete) to satisfy the destructive-operation feedback-loop requirement.

Include one short example of a stage deliverable so the '输出符合该阶段要求的交付物' instruction is concrete rather than implicit.

DimensionReasoningScore

Conciseness

Lean orchestration body that assumes Claude's competence and avoids explaining known concepts; the落盘 rules are operational specifics that earn their place, with only minor edge-case detail (同日多次归档加时分后缀) that could be trimmed, so not a 5.

4 / 5

Actionability

Provides concrete executable guidance — file paths (docs/<feature>/01-需求理解.md), archive naming patterns, and revision-record format — but phase execution is delegated to reference files that are not present and no example deliverable is shown, keeping it below 5.

4 / 5

Workflow Clarity

A clear five-step sequence with Step 1/Step 2 framing is present, but the落盘 operation overwrites and archives files (a destructive change) with no validate→fix→retry checkpoint, which caps workflow clarity at 3 per the rubric's destructive-operation rule.

3 / 5

Progressive Disclosure

The overview is well-structured with a routing table pointing one level deep to five reference files, but none of the referenced files (reference/requirement.md, design.md, implementation.md, review.md, bug-fix.md) exist in the bundle, so the disclosure is non-functional; this is more than the minor gap required for a 4.

3 / 5

Total

14

/

20

Passed

Description

87%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 both capability and explicit trigger conditions with comprehensive natural-language keywords. Its main weakness is trigger breadth — generic terms like 'bug' and '报错' risk conflicting with dedicated debugging or code-review skills.

Suggestions

Tighten generic triggers (bug、报错、异常、出错了) by tying them to the workflow context (e.g. '修复流程中的 bug/报错') to reduce conflict with standalone debugging skills.

Clarify that this is an orchestrator skill so its distinctiveness from single-purpose coding/review skills is obvious from the description alone.

DimensionReasoningScore

Specificity

Names the domain (开发流程五步法) and lists five concrete stages (需求理解、方案设计、代码实现、代码审查、Bug 修复), which is several specific actions; not a 5 because the stages are phase labels rather than granular operations and coverage of each phase's actions is not detailed.

4 / 5

Completeness

Explicitly answers both 'what' (开发流程五步法,支持五个阶段) and 'when' (当用户提到「…」时使用) with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers with synonyms across all five phases (需求分析/理解需求, 方案设计/技术设计, 代码实现/开始写代码, 代码审查/Review/检查代码, bug/报错/崩溃/异常/出错了) that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Scoped to a distinct dev-workflow niche, but very generic triggers (bug、报错、异常、出错了、开始写代码) create real overlap risk with general coding, debugging, and code-review skills; not a 4 because the overlap is more than minor.

3 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

xstongxue/best-skills

Path

skills/dev-workflow/SKILL.md

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.