Agent skill

Rust Testing

by kurealnum in kurealnum/dotfiles

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage.

No licenceAuto-check passedTesting & QA

Install Rust Testing

skills CLI
$ npx skills add kurealnum/dotfiles --skill rust-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kurealnum/dotfiles rust-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kurealnum/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/rust-testing .claude/skills/rust-testing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
rust-testing
GitHub stars
290
Used in
6 other repos
Token cost
~2.9k tokens
SKILL.md length
331 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
None found

At a glance

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage.

  • Works in 7 steps: Identify target code — Find the… → Write a test — Use #[test] in a… → Mock dependencies — Use mockall to… → …
  • Tasks that involve Unit testing
  • SKILL.md covers When to Use, How It Works, TDD Workflow for Rust and Unit Tests, plus 9 more sections
  • Calls cargo

What it does

Rust Testing is an agent skill from kurealnum/dotfiles. Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

Its SKILL.md is about 2.9k 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, covering Unit testing, Test-driven development and Test strategy. It works with Rust.

When your agent uses it

  • Tasks that involve Unit testing
  • Tasks that involve Test-driven development
  • Tasks that involve Test strategy

Example prompts

  • “/rust-testing”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Identify target code — Find the function, trait, or module to test
  2. Write a test — Use #[test] in a #[cfg(test)] module, rstest for parameterized tests, or proptest for property-based tests
  3. Mock dependencies — Use mockall to isolate the unit under test
  4. Run tests (RED) — Verify the test fails with the expected error
  5. Implement (GREEN) — Write minimal code to pass
  6. Refactor — Improve while keeping tests green
  7. Check coverage — Use cargo-llvm-cov, target 80%+

What it can do on your machine

Read from SKILL.md and the folder at commit bcd8741. 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 2.9k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 331 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 331 words (~2,904 tokens).

“Comprehensive Rust testing patterns for writing reliable, maintainable tests following TDD methodology.”

— opening of SKILL.md by kurealnum
name
rust-testing
origin
ECC

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/rust-testing of kurealnum/dotfiles.

Open the folder on GitHubat commit bcd8741

Used in 6 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 6 other GitHub owners. This page covers the copy in kurealnum/dotfiles, which our catalogue first saw on October 7, 2026.

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.

Rust Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rust Testing this skillkurealnum/dotfiles2906 repos~2.9kAutomated safety check: PassNone
Godot Testing Patternsthedivergentai/GD-Agentic-Skills803—~2.9kAutomated safety check: PassLGPL-3.0
Test Experteinverne/dotfiles121—~2.3kAutomated safety check: PassGPL-3.0
Python Testingathola/claude-night-market342—~800Automated safety check: PassMIT
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Godot Testing Patterns

    thedivergentai/GD-Agentic-Skills

    Expert testing decision trees for GdUnit4: unit vs scene vs CI gates, headless runners, snapshots, and mock networks.

    803 GitHub stars~2.9k tokensUpdated 28 days ago
    Testing & QAAuto-check passed
  • Test Expert

    einverne/dotfiles

    Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks.

    121 GitHub stars~2.3k tokensUpdated 28 days ago
    Testing & QAAuto-check passed
  • Python Testing

    athola/claude-night-market

    Python testing patterns with pytest, fixtures, TDD, mocking, async and integration tests.

    342 GitHub stars~800 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • 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.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check: notes
  • 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.

    23k GitHub stars~1.1k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

More from kurealnum/dotfiles

All 13 skills in this repo
  • Continuous Learning V2

    kurealnum/dotfiles

    Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    290 GitHub starsUsed in 4 repos~3.1k tokens
    Auto-check passed
  • Frontend Patterns

    kurealnum/dotfiles

    Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

    290 GitHub starsUsed in 19 repos~3.7k tokens
    Auto-check passed
  • Coding Standards

    kurealnum/dotfiles

    Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

    290 GitHub starsUsed in 17 repos~2.9k tokens
    Auto-check passed
  • Python Patterns

    kurealnum/dotfiles

    Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.

    290 GitHub starsUsed in 8 repos~4.1k tokens
    Auto-check passed
  • Twitter Algorithm Optimizer

    kurealnum/dotfiles

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights.

    290 GitHub starsUsed in 8 repos~3.2k tokens
    Auto-check passed
  • DB Migrations

    kurealnum/dotfiles

    A skill your agent uses when generating or regenerating Drizzle migration files, changing database schema tables or columns, resolving migration sequence conflicts after rebase, reviewing migration…

    290 GitHub stars~820 tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Rust Testing

What does Rust Testing do?

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Rust Testing is an agent skill from kurealnum/dotfiles. Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage.

When should I use Rust Testing?

Rust Testing fits situations like: tasks that involve Unit testing; tasks that involve Test-driven development; tasks that involve Test strategy.

How do I install Rust Testing in Claude Code?

Run `npx skills add kurealnum/dotfiles --skill rust-testing -a claude-code`. Or copy the skill folder (.agents/skills/rust-testing in kurealnum/dotfiles) 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 kurealnum/dotfiles --skill rust-testing -a codex`. Or copy the skill folder (.agents/skills/rust-testing in kurealnum/dotfiles) 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 kurealnum/dotfiles --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?

No licence was found for Rust Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Rust Testing use?

About 2.9k tokens (SKILL.md is roughly 12k 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: Godot Testing Patterns (thedivergentai/GD-Agentic-Skills, 803 stars), Test Expert (einverne/dotfiles, 121 stars), Python Testing (athola/claude-night-market, 342 stars) and Rust TDD Workflow (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?

kurealnum (a GitHub user) maintains it in kurealnum/dotfiles, which has 290 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on April 13, 2026.

Source: kurealnum/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.