Implement Agent Skill
Make tests pass. Invoke after /write-tests produces failing tests.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/huggingface/OpenEnv --skill implementThe instruction itself
10 sections, as written by the author/implement
Make failing tests pass with minimal code.
Usage
/implement
The implementer will automatically find failing tests from the most recent /write-tests run.
When to Use
- After
/write-testshas created failing tests - When you have specific tests that need implementation
- Never before tests exist
When NOT to Use
- No failing tests exist (run
/write-testsfirst) - You want to add features not covered by tests
- You want to refactor (use
/simplifyinstead)
What It Does
- Finds the failing tests from
/write-tests - Reads tests to understand requirements
- Writes the minimum code to make tests pass
- Runs tests after each change
- Stops when ALL tests pass
Output
The implementer agent will produce:
## Implementation Complete
### Tests Passed
- `test_client_reset_returns_observation` ✓
- `test_client_step_advances_state` ✓
- `test_client_handles_invalid_action` ✓
### Changes Made
| File | Change |
|------|--------|
| `src/openenv/core/client.py` | Added `reset()` method |
| `src/openenv/core/client.py` | Added `step()` method |
| `src/openenv/core/client.py` | Added input validation |
### Verification
PYTHONPATH=src:envs uv run pytest tests/test_client.py -v
All 3 tests passed
### Next Steps
- Mark todo as complete
- Consider `/simplify` if change was large
- Move to next pending todo
Rules
- Read the failing tests first to understand exactly what's needed
- Write the MINIMUM code needed to pass tests
- Run tests after each change to verify progress
- Do NOT add extra features not covered by tests
- Do NOT refactor existing code (that's
/simplify's job) - Stop when all tests pass
Anti-patterns (NEVER do these)
- Adding features not covered by tests
- Refactoring existing code
- Writing additional tests (that's
/write-tests's job) - Over-engineering solutions
- Adding comments or documentation beyond what's necessary
- "Improving" code that already works
Completion Criteria
Before returning, verify:
- ALL tests pass
- No new test failures introduced
- Implementation is minimal and focused
Philosophy
The implementer is a "code machine" - it takes test specifications and produces the minimal code to satisfy them. This keeps implementations focused and prevents scope creep.
Think of it as TDD's second phase: Red → Green → Refactor. You are "Green" - make tests pass, nothing more.
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take huggingface/implement from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.