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".
96
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates what it does (TDD-based feature implementation for Go/skillshare), when to use it (comprehensive list of trigger scenarios), and includes distinctive technical patterns that differentiate it from generic coding skills. The description uses proper third-person voice and provides both explicit trigger guidance and implicit catch-all ('even if the user doesn't explicitly say implement').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, write Go code'. Also mentions specific technical patterns: 'test-first development, proper handler split conventions, oplog instrumentation, dual-mode patterns'. | 3 / 3 |
Completeness | Clearly answers both what ('Implement a feature from a spec file using TDD workflow') and when ('Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec...'). Includes explicit 'Use this skill whenever' clause with comprehensive trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'add a new CLI command', 'implement a feature', 'build new functionality', 'add a flag', 'create a new internal package', 'write Go code', 'spec file', 'TDD'. These are phrases developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically for 'skillshare' Go code, TDD workflow, and mentions unique patterns like 'oplog instrumentation' and 'dual-mode (global/project) patterns'. The combination of Go + TDD + skillshare context makes it unlikely to conflict with generic coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable TDD guidance for Go feature implementation. The workflow is clearly sequenced with validation checkpoints, and code examples are executable and project-specific. The main weakness is the lengthy inline patterns reference section which could benefit from being split into separate files for better progressive disclosure.
Suggestions
Consider moving the 'Project Patterns Reference' section to a separate PATTERNS.md file and linking to it, keeping only the most essential patterns inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with Go, TDD, and CLI development. No unnecessary explanations of basic concepts; every section provides actionable, project-specific guidance. | 3 / 3 |
Actionability | Provides fully executable code examples throughout—test patterns with testutil.Sandbox, oplog instrumentation, handler patterns, and bash commands. Copy-paste ready with specific file paths and command syntax. | 3 / 3 |
Workflow Clarity | Clear 7-step workflow with explicit validation checkpoints (verify tests fail in Step 3, verify tests pass in Step 4, run 'make check' in Step 5). Includes a 3-strike rule for error recovery and clear criteria for when to generate E2E runbooks. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the 'Project Patterns Reference' section is quite lengthy inline. Some of these patterns (handler split convention, TUI components) could be split into separate reference files for better navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- runkids/skillshare
- Commit
053ecb4
- 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.