Adk Verify Snippets
google/adk-python
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.
Install Hermetic Python Unit Tests
$ npx skills add dimensionalOS/dimos --skill python-unit-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dimensionalOS/dimos python-unit-tests --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/dimensionalOS/dimos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/python-unit-tests .claude/skills/python-unit-tests && 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 "python-unit-tests" agent skill from https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-tests into .claude/skills/python-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-unit-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 install https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-testsType 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 dimensionalOS/dimos --skill python-unit-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dimensionalOS/dimos python-unit-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimensionalOS/dimos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/python-unit-tests .agents/skills/python-unit-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "python-unit-tests" agent skill from https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-tests into .agents/skills/python-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-unit-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.
$ npx skills add dimensionalOS/dimos --skill python-unit-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dimensionalOS/dimos python-unit-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimensionalOS/dimos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/python-unit-tests .cursor/skills/python-unit-tests && 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 "python-unit-tests" agent skill from https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-tests into .cursor/skills/python-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-unit-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 https://github.com/dimensionalOS/dimos.git --path .agents/skills/python-unit-tests--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 dimensionalOS/dimos --skill python-unit-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dimensionalOS/dimos python-unit-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimensionalOS/dimos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/python-unit-tests .gemini/skills/python-unit-tests && 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 "python-unit-tests" agent skill from https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-tests into .gemini/skills/python-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-unit-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.
$ gh skill install dimensionalOS/dimos python-unit-testsInstalls 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 dimensionalOS/dimos --skill python-unit-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dimensionalOS/dimos.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/python-unit-tests .github/skills/python-unit-tests && 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 "python-unit-tests" agent skill from https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-tests into .github/skills/python-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-unit-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.
$ npx skills add dimensionalOS/dimos --skill python-unit-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dimensionalOS/dimos python-unit-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimensionalOS/dimos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/python-unit-tests .opencode/skills/python-unit-tests && 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 "python-unit-tests" agent skill from https://github.com/dimensionalOS/dimos/tree/main/.agents/skills/python-unit-tests into .opencode/skills/python-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-unit-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
python-unit-tests- GitHub stars
- 4.6k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 760 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.
- Works in 5 steps: Scope the behavior. Identify the code… → Build a hermetic setup. Use module-level… → Assert the contract. Use small examples… → …
- Writing pytest unit tests for new or changed Python code
- SKILL.md covers Steps, Test shape, Fixtures and cleanup and Assertions, plus 4 more sections
- Calls uv
What it does
This skill sets out how to write Python pytest unit tests that are hermetic. It is meant to be used before adding, changing or reviewing tests. A five-step flow starts by scoping the behavior and placing the test file beside the code (`dimos/core/foo.py` gets `dimos/core/test_foo.py`), then builds a setup that owns its cleanup and has no fixed sleeps, asserts exact outcomes a caller depends on, mocks only slow, nondeterministic or external boundaries, and validates with the smallest command that could fail.
Test-shape rules favor descriptive names, Arrange-Act-Assert order, module-level imports and `assert result == expected` over shape-only checks, and rule out no-value tests such as ones proving a dataclass stores its constructor arguments. Mocking goes through `mocker.patch`, `mocker.patch.object` or `monkeypatch`, never direct method assignment. Fixtures keep setup and teardown together so cleanup runs even when assertions fail. A few repo docs on testing and code quality are consulted only when more context is needed.
When your agent uses it
- Writing pytest unit tests for new or changed Python code
- Fixing flaky tests that use sleeps or leak global state
- Reviewing feedback on a PR's tests
- Replacing hand-rolled mocks with mocker or monkeypatch
Example prompts
- “Write unit tests for dimos/core/foo.py covering the retry behavior.”
- “This test uses time.sleep to wait for a thread. Make it deterministic.”
- “Review the tests in my PR and remove any that only prove a constructor stored its arguments.”
Requirements
- Python with pytest
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Scope the behavior. Identify the code under test, the caller-visible outcome, and the smallest test file next to it: dimos/core/foo.py…
- Build a hermetic setup. Use module-level imports, Arrange-Act-Assert structure, fixtures for shared or resource-owning setup, and context…
- Assert the contract. Use small examples and exact expected values. Completion: every test has an unconditional assertion that proves…
- Mock the boundary. Mock only slow, nondeterministic, or external boundaries. Completion: patches use mocker.patch, mocker.patch.object, or…
- Validate tightly. Run the smallest command that can fail for the change, then broaden only when the edit justifies it. Completion: the…
What it can do on your machine
Read from SKILL.md and the folder at commit faf1bed. 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:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
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
Hermetic Python Unit Tests loads about 1.4k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 760 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 760 words (~1,438 tokens).
“Use this skill before adding, changing, or reviewing Python unit tests. The goal is hermetic tests: behavior-focused, deterministic, isolated, and cheap to run.”
- name
- python-unit-tests
Files
Just SKILL.md in .agents/skills/python-unit-tests of dimensionalOS/dimos.
Open the folder on GitHubat commit faf1bed
Compare with similar skills
Hermetic Python Unit 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hermetic Python Unit Tests this skilldimensionalOS/dimos | 4.6k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Adk Verify Snippetsgoogle/adk-python | 22k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Test Coverage Reviewareed1192/finance-news-aggregator | 149 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Py Package Checkipea/geobr | 959 | — | ~1.4k | Automated safety check: Notes | None | |
| Testing Livekit Agentslivekit-examples/agent-starter-python | 264 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Mutation Test Strength Auditbuildfastwithai/gen-ai-experiments | 785 | — | ~641 | Automated safety check: Pass | MIT |
Similar skills
- Official
Test Coverage Review
areed1192/finance-news-aggregator
Audit, plan, write, and verify unit tests for Python projects using pytest.
Py Package Check
ipea/geobr
Run the Python package release gate for geobr — sync the locked environment, run the offline and network test suites, build the distribution, and review the source against the Python conventions.
Testing Livekit Agents
livekit-examples/agent-starter-python
Writes turn-level tests for a LiveKit agent in the user's normal test suite: pytest (Python) or Vitest (Node.js).
Mutation Test Strength Audit
buildfastwithai/gen-ai-experiments
Measures how well a Python pytest suite catches behavior changes through diff-scoped mutation testing, then proposes and verifies tests for surviving mutants.
TDD Guide
alirezarezvani/claude-skills
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…
Related
Categories
Questions about Hermetic Python Unit Tests
What does Hermetic Python Unit Tests do?
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run. This skill sets out how to write Python pytest unit tests that are hermetic. It is meant to be used before adding, changing or reviewing tests.
When should I use Hermetic Python Unit Tests?
Hermetic Python Unit Tests fits situations like: writing pytest unit tests for new or changed Python code; fixing flaky tests that use sleeps or leak global state; reviewing feedback on a PR's tests; replacing hand-rolled mocks with mocker or monkeypatch.
How do I install Hermetic Python Unit Tests in Claude Code?
Run `npx skills add dimensionalOS/dimos --skill python-unit-tests -a claude-code`. Or copy the skill folder (.agents/skills/python-unit-tests in dimensionalOS/dimos) into .claude/skills/python-unit-tests in your project. Claude Code loads it when a task matches its description.
How do I install Hermetic Python Unit Tests in Codex?
Run `npx skills add dimensionalOS/dimos --skill python-unit-tests -a codex`. Or copy the skill folder (.agents/skills/python-unit-tests in dimensionalOS/dimos) into .agents/skills/python-unit-tests in your project. Codex loads it when a task matches its description.
Can I use Hermetic Python Unit 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 dimensionalOS/dimos --skill python-unit-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/python-unit-tests, .gemini/skills/python-unit-tests, .github/skills/python-unit-tests and .opencode/skills/python-unit-tests in your project.
What does Hermetic Python Unit Tests need to run?
Going by SKILL.md and its folder, Hermetic Python Unit Tests needs the command-line tools its instructions call (uv). Our summary lists: Python with pytest.
Does Hermetic Python Unit Tests access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Hermetic Python Unit 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 Hermetic Python Unit Tests use?
Hermetic Python Unit Tests has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Hermetic Python Unit Tests use?
About 1.4k tokens (SKILL.md is roughly 5.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 Hermetic Python Unit Tests?
Skills that share tags, products or a category with Hermetic Python Unit Tests: Adk Verify Snippets (google/adk-python, 22k stars), Test Coverage Review (areed1192/finance-news-aggregator, 149 stars), Py Package Check (ipea/geobr, 959 stars) and Testing Livekit Agents (livekit-examples/agent-starter-python, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hermetic Python Unit Tests?
dimensionalOS (a GitHub organization) maintains it in dimensionalOS/dimos, which has 4,626 GitHub stars. The repository was last updated on October 7, 2026.
Source: dimensionalOS/dimos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.