Agent skill

Organize Tests

Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.

Apache-2.0Auto-check passedTesting & QA

Install Organize Tests

skills CLI

$ npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a claude-code

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

GitHub CLI

$ gh skill install r3bl-org/r3bl-open-core organize-tests --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/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/organize-tests .claude/skills/organize-tests && 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/

Paste into Claude Code

Install the "organize-tests" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests into .claude/skills/organize-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-tests", 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

$skill-installer install https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests

Type 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.

skills CLI

$ npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install r3bl-org/r3bl-open-core organize-tests --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/organize-tests .agents/skills/organize-tests && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "organize-tests" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests into .agents/skills/organize-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-tests", 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.

skills CLI

$ npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install r3bl-org/r3bl-open-core organize-tests --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/organize-tests .cursor/skills/organize-tests && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "organize-tests" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests into .cursor/skills/organize-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-tests", 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

$ gemini skills install https://github.com/r3bl-org/r3bl-open-core.git --path .agents/skills/organize-tests

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install r3bl-org/r3bl-open-core organize-tests --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/organize-tests .gemini/skills/organize-tests && rm -rf skills-src

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

Paste into Gemini CLI

Install the "organize-tests" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests into .gemini/skills/organize-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-tests", 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.

GitHub CLI

$ gh skill install r3bl-org/r3bl-open-core organize-tests

Installs 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).

skills CLI

$ npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/organize-tests .github/skills/organize-tests && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "organize-tests" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests into .github/skills/organize-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-tests", 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.

skills CLI

$ npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install r3bl-org/r3bl-open-core organize-tests --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/organize-tests .opencode/skills/organize-tests && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "organize-tests" agent skill from https://github.com/r3bl-org/r3bl-open-core/tree/main/.agents/skills/organize-tests into .opencode/skills/organize-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-tests", 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: organize-tests
GitHub stars: 485
Token cost: ~1.2k tokens
SKILL.md length: 541 words
Files: 4
Skills in repo: 25
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.

Works in 7 steps: Identify Isolation Requirements → Follow PTY Conventions → Orchestrate Process Isolation → …
Testing & QA work in your project
SKILL.md covers When to Use, Instructions and Related Skills
Calls cargo

What it does

Organize Tests is an agent skill from r3bl-org/r3bl-open-core. Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `examples.md`, `pty-conventions.md` and `taxonomy.md`).

It sits in Testing & QA. The repository describes itself as: TUI framework and developer productivity apps in Rust 🦀. The licence is Apache-2.0.

When your agent uses it

Testing & QA work in your project

Example prompts

“/organize-tests”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Identify Isolation Requirements
Follow PTY Conventions
Orchestrate Process Isolation
Wire Up Modules
Organize Conformance & Golden Test Data (test_data/)
Memory Size "Tripwire" Tests
Test OUR Code, Not Dependencies (Zero Test Bloat)

What it can do on your machine

Read from SKILL.md and the folder at commit 89db352. 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

Organize Tests loads about 1.2k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 541 words of instructions outside code blocks.

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

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 r3bl-org/r3bl-open-core at commit 89db352, republished under its Apache-2.0 licence (© r3bl-org). 541 words, ~1,188 tokens.

Download SKILL.mdSave it as .claude/skills/organize-tests/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: organize-tests
description: Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.

Skill: organize-tests

Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.

When to Use

Adding new tests to the codebase.
Refactoring existing tests.
Organizing test modules and directories.
Ensuring PTY tests follow the "Run with:" and deadlock prevention conventions.

Instructions

1. Identify Isolation Requirements

Choose the correct directory based on why the test needs isolation. This maintains low cognitive load for future developers.

See Taxonomy for directory details.

2. Follow PTY Conventions

PTY tests are complex and prone to deadlocks (especially on macOS). Strict adherence to naming, documentation, and resource management is mandatory.

See PTY Conventions for details.

3. Orchestrate Process Isolation

Tests that pollute global mock state (e.g., static Mutexes) must be isolated into a single subprocess and run sequentially.

See Examples for macro usage.

4. Wire Up Modules

Always ensure test modules are visible for both tests and documentation using #[cfg(any(test, doc))].

rust

#[cfg(any(test, doc))]
pub mod unit_tests;
#[cfg(any(test, doc))]
pub mod process_isolated_tests;
#[cfg(any(test, doc))]
pub mod my_module_integration_tests;

5. Organize Conformance & Golden Test Data (`test_data/`)

When tests validate external files or assert outputs against golden files, place them in test_data/ with input/ and expected_output/ subdirectories. Use matching basenames (e.g., input/unix/cargo_env.sh and expected_output/unix/cargo_env.fish) and protect the directory with an AGENTS.md file. See Taxonomy for details.

6. Memory Size "Tripwire" Tests

When writing tests that assert the byte size of a struct (std::mem::size_of), you MUST gate the test or the assertion block with #[cfg(target_pointer_width = "64")] to ensure it only runs on 64-bit architectures. Struct sizes vary between 32-bit and 64-bit platforms due to pointer sizes.

rust

#[test]
fn test_my_struct_size() {
    // TRIPWIRE: If you add or remove a field, this test will fail.
    // This reminds you to update the `GetMemSize` implementation.
    #[cfg(target_pointer_width = "64")]
    {
        assert_eq!(std::mem::size_of::<MyStruct>(), 184);
    }
}

Show full SKILL.md (287 more words)Show less

7. Test OUR Code, Not Dependencies (Zero Test Bloat)

Tests must exclusively target the branches, state transitions, error paths, and delegation logic of our codebase (the System Under Test).

Why Noisy Tests Add Negative Value:

Compilation Overhead: Each redundant test function generates additional compiler symbols, AST nodes, and test runner harness code, slowing down incremental cargo test and check.fish iteration cycles.
Obfuscation & Signal Dilution: When a real regression occurs, walls of redundant, noisy failures obscure the root cause, making triage and debugging far harder.
Refactoring Drag: Tests that assert upstream crate or std behaviors add zero bug-catching value while creating maintenance friction during internal architecture refactors.

Key Rules:

Never Test the Standard Library or Third-Party Crates: Do NOT write test cases that merely assert or re-verify standard library behaviors (such as std::ffi::OsString UTF-8 validation permutations, std::collections::HashMap storage integrity, tokio task scheduling, serde serialization formats, etc.). These dependencies are already heavily tested upstream.
Branch-Targeted Coverage: Count the execution paths and branches in our code:
- If our method has two branches (e.g., Ok fast path vs unwrap_or_else fallback closure), write exactly one test per branch.
- Redundant permutations of valid inputs (such as testing multiple languages, emojis, whitespace variants, or path styles on a method that simply forwards to a standard library function) test the standard library, not our logic.
High Signal, Low Cognitive Load: Every test in the repository must serve a distinct purpose by covering a specific branch or boundary condition of our implementation. Proactively remove redundant, needless, or duplicative tests that only inflate maintenance overhead.

organize-modules: Use for general module structure and re-exports.
write-documentation: Use for formatting "Run with:" blocks and intra-doc links.
check-code-quality: Use for comprehensive quality checklists and test execution.

Files

SKILL.md and 3 other files in .agents/skills/organize-tests of r3bl-org/r3bl-open-core.

SKILL.md
examples.md
pty-conventions.md
taxonomy.md

Open the folder on GitHubat commit 89db352

Compare with similar skills

Organize Tests 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.

Organize Tests compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Organize Tests this skillr3bl-org/r3bl-open-core	485	—	~1.2k	Automated safety check: Pass	Apache-2.0	yesterday
Web Application Testinganthropics/skills	180k	51 repos	~966	Automated safety check: Pass	Apache-2.0	yesterday
Diagnosing Bugsfossasia/eventyay-interpretation	1.6k	32 repos	~2.1k	Automated safety check: Pass	Apache-2.0	4 days ago
TDDpietheinstrengholt/rssmonster	564	30 repos	~906	Automated safety check: Pass	MIT	2 days ago
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph	112	11 repos	~2.4k	Automated safety check: Pass	None	8 mo ago
TDDsanity-io/sanity	6.4k	20 repos	~1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Web Application Testing
anthropics/skills
Official
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
180k GitHub starsUsed in 51 repos~966 tokens
Testing & QAAuto-check passed
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
1.6k GitHub starsUsed in 32 repos~2.1k tokens
Testing & QAAuto-check passed
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
564 GitHub starsUsed in 30 repos~906 tokens
Testing & QAAuto-check passed
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
112 GitHub starsUsed in 11 repos~2.4k tokens
Testing & QAAuto-check passed
TDD
sanity-io/sanity
Official
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
6.4k GitHub starsUsed in 20 repos~1k tokens
Testing & QAAuto-check passed
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
381 GitHub starsUsed in 9 repos~2.9k tokens
Testing & QAAuto-check passed

Questions about Organize Tests

What does Organize Tests do?

Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns. Organize Tests is an agent skill from r3bl-org/r3bl-open-core. Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.

When should I use Organize Tests?

Organize Tests fits situations like: testing & QA work in your project.

How do I install Organize Tests in Claude Code?

Run `npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a claude-code`. Or copy the skill folder (.agents/skills/organize-tests in r3bl-org/r3bl-open-core) into .claude/skills/organize-tests in your project. Claude Code loads it when a task matches its description.

How do I install Organize Tests in Codex?

Run `npx skills add r3bl-org/r3bl-open-core --skill organize-tests -a codex`. Or copy the skill folder (.agents/skills/organize-tests in r3bl-org/r3bl-open-core) into .agents/skills/organize-tests in your project. Codex loads it when a task matches its description.

Can I use Organize Tests 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 r3bl-org/r3bl-open-core --skill organize-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/organize-tests, .gemini/skills/organize-tests, .github/skills/organize-tests and .opencode/skills/organize-tests in your project.

What does Organize Tests need to run?

Going by SKILL.md and its folder, Organize Tests needs the command-line tools its instructions call (cargo).

Does Organize Tests 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 Organize Tests 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 Organize Tests use?

Organize Tests is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Organize Tests use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Organize Tests?

Skills that share tags, products or a category with Organize Tests: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Organize Tests?

r3bl-org (a GitHub organization) maintains it in r3bl-org/r3bl-open-core, which has 485 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.

Source: r3bl-org/r3bl-open-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Organize Tests

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: organize-tests

When to Use

Instructions

1. Identify Isolation Requirements

2. Follow PTY Conventions

3. Orchestrate Process Isolation

4. Wire Up Modules

5. Organize Conformance & Golden Test Data (test_data/)

6. Memory Size "Tripwire" Tests

7. Test OUR Code, Not Dependencies (Zero Test Bloat)

Related Skills

Files

Compare with similar skills

Similar skills

More from r3bl-org/r3bl-open-core

Related

Questions about Organize Tests

5. Organize Conformance & Golden Test Data (`test_data/`)