CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-implement-feature

Build a working artifact from a plain "implement X for me" request: a running end-to-end spine first, then one feature per rung, with every under-determined decision written to an assumption ledger BEFORE the code that depends on it and a sweep for the ones that slipped through undeclared (same-family provisional in the base Codex mirror). Use when user says "给我实现", "implement X", "帮我做一个能跑的", "先搭个原型再加功能", "build this feature", "prototype then extend", or hands over a capability description rather than an experiment plan.

Quality

87%

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

77%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 tightly sequenced, highly actionable phase workflow with pervasive validation checkpoints (per-rung exit-code gates, regression re-runs, fix budgets, re-sweep rounds) and copy-paste templates and prompts. It loses points on redundancy — the same-family provisional rule is repeated four times and the Phase 4 reviewer message inlines ~50 lines whose scope limits duplicate a referenced shared doc — and on inlining that prompt rather than splitting it into a bundle reference file.

Suggestions

State the same-family provisional rule once (e.g., in the 'Review assurance' blockquote near the top) and reference it from Phase 4, the assurance table, and the anti-patterns list instead of repeating it four separate times.

Move the ~50-line Phase 4 spawn_agent reviewer message into a bundle file (e.g., references/sweep-reviewer-prompt.md); its SCOPE LIMITS section already duplicates shared-references/review-scope-limits.md, so the inline copy can collapse to a pointer.

Trim the two opening blockquotes (Selectable Reviewers, Review assurance) to one-line pointers into ../shared-references/reviewer-backends.md and reviewer-independence.md so SKILL.md reads as an overview rather than embedding routing policy inline.

DimensionReasoningScore

Conciseness

The body is mostly operational (templates, commands, tables) with no basic-concept padding, but it could be tightened: the same-family-provisional rule is stated four separate times (opening 'Review assurance' blockquote, Phase 4 table row, 'Review limitation' paragraph, and an anti-pattern bullet), and the ~50-line Phase 4 reviewer message inlines scope limits that the referenced shared-references/review-scope-limits.md already covers. This matches anchor 3 ('mostly efficient… could be tightened') rather than anchor 2, since there is no conceptual explanation of things Claude already knows.

3 / 5

Actionability

Guidance is fully executable throughout: one-command acceptance checks ('python scripts/run.py --smoke && test -f out/smoke.json', 'pytest tests/test_loader.py'), 'git rev-parse HEAD' for the base commit, copy-paste markdown templates for ASSUMPTIONS.md and BUILD_NOTE.md, a ready-to-use spawn_agent reviewer message, and an exact JSON return contract ('{"undeclared": [...], "stale_rows": [...], "semantic_undeclared": N, "verdict": "clean"|"gaps"}') — matching anchor 5's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

Phases 0–5 are strictly sequenced with explicit validation at every step: each rung's check requires exit 0, 'Every earlier rung's check → all exit 0' enforces regression gates, fix budgets create retry loops, exhaustion fills *Blockers* and stops the ladder, and the sweep re-runs up to a round budget — clear sequence, explicit validation, and feedback loops per anchor 5. The destructive/batch cap does not apply because validation checkpoints are pervasive rather than missing.

5 / 5

Progressive Disclosure

References are clearly signaled (inline links plus an annotated See Also listing eight shared references), but the skill bundle itself contains no files (no references/, scripts/, or assets/), every referenced document lives outside the bundle in ../shared-references/ where its existence cannot be verified from the skill, and the ~50-line Phase 4 reviewer prompt is inlined content that belongs in a separate reference file — its SCOPE LIMITS section even duplicates an existing shared reference. This matches anchor 3 ('content that should be separate is inline') rather than anchor 4, whose 'minor organization gaps' understates that misplacement.

3 / 5

Total

16

/

20

Passed

Description

96%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 is exemplary: it states concrete capabilities (spine-first ladder, pre-code assumption ledger, undeclared-assumption sweep) and an explicit bilingual 'Use when' trigger list that answers both what and when with concrete phrases. Its only weakness is that its most generic triggers ('implement X', 'build this feature') carry minor conflict risk against general implementation skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the whole workflow — 'Build a working artifact', 'a running end-to-end spine first, then one feature per rung', 'every under-determined decision written to an assumption ledger BEFORE the code that depends on it', 'a sweep for the ones that slipped through undeclared' — matching the comprehensive-coverage anchor rather than anchor 4, which reserves room for coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the opening sentence states what the skill does (spine-first ladder, pre-code assumption ledger, undeclared-assumption sweep) and 'Use when user says…' gives concrete trigger phrases — the exact structure of the anchor-5 example; it is not anchor 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

The trigger list gives natural phrasings users would actually say with synonym and bilingual coverage: 'implement X', 'build this feature', 'prototype then extend', '给我实现', '帮我做一个能跑的', '先搭个原型再加功能', plus 'hands over a capability description rather than an experiment plan' — comprehensive natural-term coverage per the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

The carve-out 'hands over a capability description rather than an experiment plan' establishes a clear niche distinct from research/experiment skills, but 'implement X' and 'build this feature' are generic build-request phrases that any general implementation skill would also claim — minor overlap risk, matching anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 14 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/research-implement-feature/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.