CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

83%

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

100%

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-engineered multi-phase workflow: tightly written, actionable with concrete commands and named tooling, and sequenced with explicit validation checkpoints and bounded feedback loops. Organization is clear and self-contained, so no progressive-disclosure changes are needed.

DimensionReasoningScore

Conciseness

The body is lean: each phase uses terse bullets and an 'Output:' line, and it does not explain concepts Claude already knows, matching 'lean and efficient; every token earns its place'; it is tighter than the level-2 example that adds unnecessary justification.

3 / 3

Actionability

It gives concrete commands ('npm run build', 'npm run typecheck', 'npm run bundle', 'node dist/cli.js'), specific artifact paths, and named tools/agents; the guidance is actionable even though much is instructional, so it is not penalized for absence of code per the scoring notes.

3 / 3

Workflow Clarity

Eight phases are explicitly sequenced, each producing a concrete artifact, with validation checkpoints and feedback loops ('until all groups pass', 'two consecutive clean passes', 'do not loop more than 3 times'), matching the anchor for clear sequence with explicit validation and error-recovery loops.

3 / 3

Progressive Disclosure

No bundle files are present, so this is judged on organization; the body is split into clearly headed, navigable sections with no nested references, satisfying the well-organized-sections allowance for content that needs no external detail files.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and well-scoped to qwen-code feature development, listing concrete phases that make it distinguishable. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the activation guidance implied rather than stated.

Suggestions

Add an explicit activation clause such as 'Use when implementing a non-trivial feature in qwen-code that needs design or behavioral validation.'

Broaden trigger terms to include natural variations users might say, e.g. 'feature development', 'add a feature to qwen-code', or 'E2E test a new feature'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'requirements investigation, design, E2E test planning, baseline dry-run, implementation, verification, self-audit, code review, and iteration' — matching the anchor for enumerating several specific activities.

3 / 3

Completeness

It clearly answers 'what' via the enumerated phases, but 'when' is only implied — there is no 'Use when...' clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

The phrase 'implementing a non-trivial qwen-code feature' is a natural trigger, but coverage is narrow with no common variations, fitting 'some relevant keywords but missing common variations' rather than broad coverage.

2 / 3

Distinctiveness Conflict Risk

Scoping to 'a non-trivial qwen-code feature' carves a clear niche unlikely to fire for unrelated skills, matching the distinct-trigger anchor; it is well above the generic-overlap level 2.

3 / 3

Total

10

/

12

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
QwenLM/qwen-code
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.