CtrlK
BlogDocsLog inGet started
Tessl Logo

skillshare-implement-feature

Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development, proper handler split conventions, oplog instrumentation, and dual-mode (global/project) patterns. If the request involves writing Go code and tests, use this skill — even if the user doesn't explicitly say "implement".

73

Quality

92%

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

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

Highly actionable and well-sequenced TDD workflow with strong validation feedback loops, though it is verbose in places and bundles reference-style project patterns inline rather than progressively disclosing them via separate reference files.

Suggestions

Move the "Project Patterns Reference" section (handler split, dual-mode, TUI, web API, oplog) into a references/ file (e.g. PROJECT_PATTERNS.md) and link to it from the body to improve progressive disclosure.

Trim the embedded Step 6 runbook markdown template to its essential structure, or relocate the full template into a separate reference file.

Reduce the placeholder-laden file-list bash block in Step 2 to a concise note, since the handler-split table later already conveys the file conventions.

DimensionReasoningScore

Conciseness

Mostly lean and project-specific (handler-split table, bubbletea components, oplog snippet), with minor trimmable prose such as the lengthy embedded runbook markdown template.

4 / 5

Actionability

Provides copy-paste-ready executable Go test code, oplog instrumentation snippet, dual-mode dispatch code, concrete make/go commands, and a full runbook template covering the common implementation cases.

5 / 5

Workflow Clarity

A 7-step TDD workflow with explicit validation checkpoints (RED "Verify tests fail", GREEN "Verify tests pass", refactor via `make check`) and a 3-strike feedback loop for error recovery.

5 / 5

Progressive Disclosure

No bundle files exist and the ~240-line body is entirely inline; the substantial "Project Patterns Reference" section is reference-style content that could be split into a separate file rather than inlined with no file-level navigation.

3 / 5

Total

17

/

20

Passed

Description

100%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 strong, third-person description that explicitly answers both what the skill does and when to use it, with concrete actions, natural trigger terms, and clear scoping to the skillshare codebase. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("add a new CLI command", "add a flag", "create a new internal package", "write Go code") plus enforced conventions (oplog, dual-mode, handler split), giving comprehensive coverage.

5 / 5

Completeness

Clearly states what (implement a feature via TDD with enforced conventions) and when (explicit "Use this skill whenever the user asks to..." trigger list with concrete phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases with synonyms ("implement", "build new functionality", "add a flag") and explicit guidance to trigger even when the user does not say "implement".

5 / 5

Distinctiveness Conflict Risk

Scoped to the skillshare Go codebase with distinctive conventions (oplog instrumentation, dual-mode patterns, handler split), giving a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
runkids/skillshare
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.