CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

feat-dev

End-to-end workflow for implementing a non-trivial qwen-code feature. Covers requirements investigation, design, E2E test planning, baseline dry-run, implementation, verification, self-audit, code review, and iteration.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is a tightly written, highly actionable multi-phase workflow with explicit outputs, validation checkpoints, and feedback-loop rules that prevent runaway iteration. Its only notable weaknesses are a few commands left implicit (unit tests, agent spawning) and a single-file layout that could offload some per-phase checklists to reference files.

DimensionReasoningScore

Conciseness

The body is lean and dense with project-specific rules — phase artifacts, build commands, iteration caps — with no padding or explanation of concepts Claude already knows. Every line ('Do not combine phases; the output of each phase feeds the next', the per-phase 'Output:' lines) earns its place, matching the anchor 'Lean and efficient; assumes Claude's competence'.

5 / 5

Actionability

Concrete guidance throughout: exact artifact paths ('docs/design/<feature>.md', '.qwen/e2e-tests/<feature>.md'), executable commands ('npm run build', 'npm run typecheck', 'npm run bundle', 'node dist/cli.js'), named tools ('the `e2e-testing` skill', '/review'), and a concrete review-triage taxonomy. It falls short of 5 only because some steps remain high-level, e.g., 'run focused unit tests for changed files' and spawning 'test-engineer' agents lack exact commands.

4 / 5

Workflow Clarity

Eight clearly sequenced phases each with an explicit output artifact, validation checkpoints (Phase 4 dry-run against baseline, Phase 6 full E2E re-test, Phase 7 'until two consecutive clean passes'), and explicit feedback loops ('If Phase 6 fails, return to Phase 5 and then re-run Phase 6', 'Do not loop more than 3 times... without asking the user'). This matches the anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

The single-file body is well organized into labeled phases with a dedicated 'Artifact Paths' section, and its cross-references (the 'e2e-testing' skill, AGENTS.md) are clearly signaled; no bundle files exist to misplace content. It is not a 5 because at ~140 lines the Phase 2/3 checklists could arguably live in reference files, leaving SKILL.md a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

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

The description clearly and specifically communicates what the skill does through a comprehensive list of workflow phases, and it is well-scoped to the qwen-code project. Its main weakness is the absence of any explicit 'when to use' trigger guidance, which both limits completeness and reduces natural trigger-term coverage.

Suggestions

Add an explicit trigger clause such as: 'Use when the user asks to implement or add a non-trivial feature to qwen-code that requires design, testing, or multi-file changes.'

Include natural user phrasings and synonyms (e.g., 'add functionality', 'build a feature', 'extend qwen-code') so the skill triggers on how users actually phrase feature requests.

State the scope boundary in the description (e.g., skip for trivial single-file edits) to further reduce overlap with general coding workflows.

DimensionReasoningScore

Specificity

The description lists many concrete workflow actions — 'requirements investigation, design, E2E test planning, baseline dry-run, implementation, verification, self-audit, code review, and iteration' — giving comprehensive coverage of the feature-development process. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' rather than 4, which requires minor gaps in coverage; none are evident.

5 / 5

Completeness

The 'what' is clear (an end-to-end implementation workflow with enumerated phases), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is explicit and specific rather than vague.

3 / 5

Trigger Term Quality

Some relevant natural terms are present ('implementing', 'feature', 'design', 'code review'), but it misses common user phrasings like 'add a feature', 'build functionality', or 'make a change to qwen-code'. It sits at anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4, which would require only a few missing natural terms.

3 / 5

Distinctiveness Conflict Risk

Naming the specific domain ('a non-trivial qwen-code feature') gives it a fairly distinct niche with minimal conflict risk against other skills. It falls just short of 5 because generic terms like 'code review' and 'implementation' could weakly overlap with general development skills.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

QwenLM/qwen-code

Path

.qwen/skills/feat-dev/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.