Rust TDD Workflow
rtk-ai/rtk
Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.
A skill your agent uses when adding or modifying tests. An agent skill from Jxck/sptth.
Install Rust Testing
$ npx skills add Jxck/sptth --skill rust-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jxck/sptth rust-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jxck/sptth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rust-testing .claude/skills/rust-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rust-testing" agent skill from https://github.com/Jxck/sptth/tree/main/skills/rust-testing into .claude/skills/rust-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jxck/sptth/tree/main/skills/rust-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jxck/sptth --skill rust-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jxck/sptth rust-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jxck/sptth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rust-testing .agents/skills/rust-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rust-testing" agent skill from https://github.com/Jxck/sptth/tree/main/skills/rust-testing into .agents/skills/rust-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jxck/sptth --skill rust-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jxck/sptth rust-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jxck/sptth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rust-testing .cursor/skills/rust-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rust-testing" agent skill from https://github.com/Jxck/sptth/tree/main/skills/rust-testing into .cursor/skills/rust-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jxck/sptth.git --path skills/rust-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jxck/sptth --skill rust-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jxck/sptth rust-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jxck/sptth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rust-testing .gemini/skills/rust-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rust-testing" agent skill from https://github.com/Jxck/sptth/tree/main/skills/rust-testing into .gemini/skills/rust-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jxck/sptth rust-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jxck/sptth --skill rust-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jxck/sptth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rust-testing .github/skills/rust-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rust-testing" agent skill from https://github.com/Jxck/sptth/tree/main/skills/rust-testing into .github/skills/rust-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jxck/sptth --skill rust-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jxck/sptth rust-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jxck/sptth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rust-testing .opencode/skills/rust-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rust-testing" agent skill from https://github.com/Jxck/sptth/tree/main/skills/rust-testing into .opencode/skills/rust-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rust-testing- GitHub stars
- 133
- Token cost
- ~293 tokens
- SKILL.md length
- 115 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when adding or modifying tests. An agent skill from Jxck/sptth.
- Works in 3 steps: Unit tests for pure logic and validation… → Integration-like checks for… → Regression tests for security-sensitive…
- Modifying tests
- SKILL.md covers Goal, Test Strategy, What to Test and Rules, plus 2 more sections
- Calls cargo
What it does
Rust Testing is an agent skill from Jxck/sptth. Use when adding or modifying tests. Ensures behavior changes are covered with focused tests and fast feedback.
Its SKILL.md is about 290 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA. It works with Rust. The repository describes itself as: reverse https proxy (https <- sptth) for local development. The licence is MIT.
When your agent uses it
- Modifying tests
Example prompts
- “/rust-testing”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Unit tests for pure logic and validation helpers.
- Integration-like checks for command-level behavior when practical.
- Regression tests for security-sensitive fixes.
What it can do on your machine
Read from SKILL.md and the folder at commit cd865e2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rust Testing loads about 293 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 115 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jxck/sptth at commit cd865e2, republished under its MIT licence (© Jxck). 115 words, ~293 tokens.
Download SKILL.mdSave it as
.claude/skills/rust-testing/SKILL.md (or your agent's skills folder).- name
- rust-testing
- description
- Use when adding or modifying tests. Ensures behavior changes are covered with focused tests and fast feedback.
rust-testing Skill
Use this skill when adding or modifying tests in this repository.
Goal
Ensure behavior changes are covered with focused tests and fast feedback loops.
Test Strategy
- Unit tests for pure logic and validation helpers.
- Integration-like checks for command-level behavior when practical.
- Regression tests for security-sensitive fixes.
What to Test
- Config parsing/validation (
src/config.rs) - DNS response routing/forwarding decisions (
src/dns.rs) - Proxy routing/header/body constraints (
src/proxy.rs) - Key/cert file handling constraints (
src/ca.rs)
Rules
- Keep test scopes tight (one behavior per test).
- Name tests by behavior, not implementation details.
- Prefer deterministic fixtures and fixed inputs.
- Avoid network dependency in unit tests.
Commands
cargo test -q
cargo check --workspace
cargo run -p xtask -- fmt-checkDone Criteria
- New behavior is covered.
- Existing tests still pass.
- Tests remain readable and maintainable.
© Jxck, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/rust-testing of Jxck/sptth.
Open the folder on GitHubat commit cd865e2
Compare with similar skills
Rust Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rust Testing this skillJxck/sptth | 133 | — | ~293 | Automated safety check: Pass | MIT | |
| Rust TDD Workflowrtk-ai/rtk | 83k | — | ~753 | Automated safety check: Notes | Apache-2.0 | |
| Remote Executor Integration Testsopeninterpreter/openinterpreter | 69k | 2 repos | ~842 | Automated safety check: Pass | Apache-2.0 | |
| Apple Container Test RunnerRustPython/RustPython | 22k | — | ~467 | Automated safety check: Pass | MIT | |
| RTK Filter TDD in Rustrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| OpenLogi Device Fixture ContributionAprilNEA/OpenLogi | 23k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Remote Executor Integration Tests
openinterpreter/openinterpreter
Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them.
Apple Container Test Runner
RustPython/RustPython
Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.
RTK Filter TDD in Rust
rtk-ai/rtk
Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.
OpenLogi Device Fixture Contribution
AprilNEA/OpenLogi
Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.
Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
More from Jxck/sptth
Sptth Dev
Jxck/sptth
A skill your agent uses when making code or documentation changes in this repository.
Update Version
Jxck/sptth
Update project versions and release tag in one consistent flow (Cargo.toml, xtask, docs, and git tag).
Rust Error Handling
Jxck/sptth
A skill your agent uses when changing Rust code paths that return errors or log failures.
Rust Security Checklist
Jxck/sptth
Use before merging security-relevant Rust changes. An agent skill from Jxck/sptth.
Health Check
Jxck/sptth
Run a repository-wide maintenance pass before merge/release.
Related
Works with
Categories
Questions about Rust Testing
What does Rust Testing do?
A skill your agent uses when adding or modifying tests. An agent skill from Jxck/sptth. Rust Testing is an agent skill from Jxck/sptth. Use when adding or modifying tests.
When should I use Rust Testing?
Rust Testing fits situations like: modifying tests.
How do I install Rust Testing in Claude Code?
Run `npx skills add Jxck/sptth --skill rust-testing -a claude-code`. Or copy the skill folder (skills/rust-testing in Jxck/sptth) into .claude/skills/rust-testing in your project. Claude Code loads it when a task matches its description.
How do I install Rust Testing in Codex?
Run `npx skills add Jxck/sptth --skill rust-testing -a codex`. Or copy the skill folder (skills/rust-testing in Jxck/sptth) into .agents/skills/rust-testing in your project. Codex loads it when a task matches its description.
Can I use Rust Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jxck/sptth --skill rust-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-testing, .gemini/skills/rust-testing, .github/skills/rust-testing and .opencode/skills/rust-testing in your project.
What does Rust Testing need to run?
Going by SKILL.md and its folder, Rust Testing needs the command-line tools its instructions call (cargo).
Does Rust Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rust Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rust Testing use?
Rust Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rust Testing use?
About 293 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Rust Testing?
Skills that share tags, products or a category with Rust Testing: Rust TDD Workflow (rtk-ai/rtk, 83k stars), Remote Executor Integration Tests (openinterpreter/openinterpreter, 69k stars), Apple Container Test Runner (RustPython/RustPython, 22k stars) and RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rust Testing?
Jxck (a GitHub user) maintains it in Jxck/sptth, which has 133 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on February 25, 2026.
Source: Jxck/sptth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.