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…
Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
Install Pytest Testing Assistant
$ npx skills add dmitriiweb/extract-emails --skill pytest-testing-assistant -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dmitriiweb/extract-emails pytest-testing-assistant --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/dmitriiweb/extract-emails.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/pytest-testing-assistant .claude/skills/pytest-testing-assistant && 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 "pytest-testing-assistant" agent skill from https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistant into .claude/skills/pytest-testing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytest-testing-assistant", 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/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistantType 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 dmitriiweb/extract-emails --skill pytest-testing-assistant -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dmitriiweb/extract-emails pytest-testing-assistant --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dmitriiweb/extract-emails.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/pytest-testing-assistant .agents/skills/pytest-testing-assistant && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pytest-testing-assistant" agent skill from https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistant into .agents/skills/pytest-testing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytest-testing-assistant", 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 dmitriiweb/extract-emails --skill pytest-testing-assistant -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dmitriiweb/extract-emails pytest-testing-assistant --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dmitriiweb/extract-emails.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/pytest-testing-assistant .cursor/skills/pytest-testing-assistant && 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 "pytest-testing-assistant" agent skill from https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistant into .cursor/skills/pytest-testing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytest-testing-assistant", 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/dmitriiweb/extract-emails.git --path .codex/skills/pytest-testing-assistant--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 dmitriiweb/extract-emails --skill pytest-testing-assistant -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dmitriiweb/extract-emails pytest-testing-assistant --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dmitriiweb/extract-emails.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/pytest-testing-assistant .gemini/skills/pytest-testing-assistant && 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 "pytest-testing-assistant" agent skill from https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistant into .gemini/skills/pytest-testing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytest-testing-assistant", 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 dmitriiweb/extract-emails pytest-testing-assistantInstalls 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 dmitriiweb/extract-emails --skill pytest-testing-assistant -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dmitriiweb/extract-emails.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/pytest-testing-assistant .github/skills/pytest-testing-assistant && 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 "pytest-testing-assistant" agent skill from https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistant into .github/skills/pytest-testing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytest-testing-assistant", 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 dmitriiweb/extract-emails --skill pytest-testing-assistant -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dmitriiweb/extract-emails pytest-testing-assistant --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dmitriiweb/extract-emails.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/pytest-testing-assistant .opencode/skills/pytest-testing-assistant && 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 "pytest-testing-assistant" agent skill from https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/pytest-testing-assistant into .opencode/skills/pytest-testing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytest-testing-assistant", 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
pytest-testing-assistant- GitHub stars
- 111
- Token cost
- ~394 tokens
- SKILL.md length
- 178 words
- Files
- 2 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
- Works in 4 steps: Identify behavior → Write the test → Assertions → …
- Tasks that involve Unit testing
- SKILL.md covers Quick start, Workflow and Reference
- Calls pytest
What it does
Pytest Testing Assistant is an agent skill from dmitriiweb/extract-emails. Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/pytest_rules.md`).
It sits in Testing & QA, covering Unit testing. It works with pytest. The repository describes itself as: Extract emails and links to linkedin accounts from URLs. The licence is MIT.
When your agent uses it
- Tasks that involve Unit testing
Example prompts
- “/pytest-testing-assistant”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify behavior
- Write the test
- Assertions
- Run and iterate
What it can do on your machine
Read from SKILL.md and the folder at commit 1f2bb40. 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:
pytest
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
Pytest Testing Assistant loads about 394 tokens when it runs, and up to ~652 if it reads all its reference files. Until then it costs about 31 tokens; SKILL.md has 178 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 dmitriiweb/extract-emails at commit 1f2bb40, republished under its MIT licence (© dmitriiweb). 178 words, ~394 tokens.
Download SKILL.mdSave it as
.claude/skills/pytest-testing-assistant/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- pytest-testing-assistant
- description
- Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
Pytest Testing Assistant
Quick start
- Write tests as plain functions; do not use test classes. Aim for one focused test per function/behavior.
- Use clear names:
test_<function>_<behavior>; keep AAA (arrange/act/assert) obvious. - Prefer one primary assertion per test; add minimal supporting checks when necessary.
- Use fixtures sparingly to keep tests readable; favor in-test setup when simple.
- Run with
pytestorpytest path/to/test_file.pyto scope runs. - See
references/pytest_rules.mdfor detailed guidelines and examples.
Workflow
Identify behavior
- Target a single function/behavior per test. Name the test after the behavior being validated.
Write the test
- Use a standalone function
def test_<thing>():(no classes). - Keep a clear arrange/act/assert structure; avoid hidden work in fixtures unless it improves clarity.
- Use parametrization for small input/output matrices instead of loops.
- Use a standalone function
Assertions
- Prefer one main assertion; add secondary checks only when they clarify the outcome.
- Include helpful assertion messages or use expressive matchers for readability.
Run and iterate
- Run
pytest(optionally narrow with paths or-kexpressions). - Refine names and setup for readability and isolation.
- Run
Reference
references/pytest_rules.md: structure rules, naming patterns, and usage tips.
© dmitriiweb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .codex/skills/pytest-testing-assistant of dmitriiweb/extract-emails.
- SKILL.md
- references/pytest_rules.md
Open the folder on GitHubat commit 1f2bb40
Compare with similar skills
Pytest Testing Assistant 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 |
|---|---|---|---|---|---|---|
| Pytest Testing Assistant this skilldmitriiweb/extract-emails | 111 | — | ~394 | Automated safety check: Pass | MIT | |
| Adk Verify Snippetsgoogle/adk-python | 22k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Megatron Core Testing GuideNVIDIA/Megatron-LM | 18k | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Hermetic Python Unit TestsdimensionalOS/dimos | 4.6k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Test GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Fla Optimization Loopfla-org/flash-linear-attention | 5.8k | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Megatron Core Testing Guide
NVIDIA/Megatron-LM
Guide to the Megatron-LM test system: layout, recipe YAML, running and adding unit and functional tests, golden values, marker filters and CI parity.
Hermetic Python Unit Tests
dimensionalOS/dimos
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.
Test Guard
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
Fla Optimization Loop
fla-org/flash-linear-attention
Disciplined, reproducible loop for making an FLA kernel faster (Triton, Gluon, TileLang, CuTe) without ever breaking or gaming correctness.
Pytest Runner
saleor/saleor
Run pytest tests with automatic virtual environment activation. Use this skill whenever running tests, executing pytest, or when asked to "run tests", "test…
More from dmitriiweb/extract-emails
All 8 skills in this repoGit Commit Assistant
dmitriiweb/extract-emails
Generate high-quality conventional git commit messages and, with user approval, run the commit.
Agents Md Assistant
dmitriiweb/extract-emails
Inspect a repository and draft an AGENTS.md file using the standard template, capturing commands, structure, and workflow rules.
Code Review Assistant
dmitriiweb/extract-emails
Perform structured, actionable code reviews for Python code with clear findings and suggestions.
Debug Logging Assistant
dmitriiweb/extract-emails
Add purposeful debug logging to improve observability without changing behavior.
Format Lint Assistant
dmitriiweb/extract-emails
Run the project's formatter, linters, and mypy checks in the required order, fixing issues and managing any needed stub dependencies via uv.
Google Docstring Assistant
dmitriiweb/extract-emails
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Related
Works with
Categories
Questions about Pytest Testing Assistant
What does Pytest Testing Assistant do?
Write focused pytest tests as standalone functions (one test per function), avoiding test classes. Pytest Testing Assistant is an agent skill from dmitriiweb/extract-emails. Write focused pytest tests as standalone functions (one test per function), avoiding test classes.
When should I use Pytest Testing Assistant?
Pytest Testing Assistant fits situations like: tasks that involve Unit testing.
How do I install Pytest Testing Assistant in Claude Code?
Run `npx skills add dmitriiweb/extract-emails --skill pytest-testing-assistant -a claude-code`. Or copy the skill folder (.codex/skills/pytest-testing-assistant in dmitriiweb/extract-emails) into .claude/skills/pytest-testing-assistant in your project. Claude Code loads it when a task matches its description.
How do I install Pytest Testing Assistant in Codex?
Run `npx skills add dmitriiweb/extract-emails --skill pytest-testing-assistant -a codex`. Or copy the skill folder (.codex/skills/pytest-testing-assistant in dmitriiweb/extract-emails) into .agents/skills/pytest-testing-assistant in your project. Codex loads it when a task matches its description.
Can I use Pytest Testing Assistant 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 dmitriiweb/extract-emails --skill pytest-testing-assistant -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pytest-testing-assistant, .gemini/skills/pytest-testing-assistant, .github/skills/pytest-testing-assistant and .opencode/skills/pytest-testing-assistant in your project.
What does Pytest Testing Assistant need to run?
Going by SKILL.md and its folder, Pytest Testing Assistant needs the command-line tools its instructions call (pytest).
Does Pytest Testing Assistant 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 Pytest Testing Assistant 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 Pytest Testing Assistant use?
Pytest Testing Assistant 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 Pytest Testing Assistant use?
About 394 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 258 tokens, read only when the agent opens those files.
What are the alternatives to Pytest Testing Assistant?
Skills that share tags, products or a category with Pytest Testing Assistant: Adk Verify Snippets (google/adk-python, 22k stars), Megatron Core Testing Guide (NVIDIA/Megatron-LM, 18k stars), Hermetic Python Unit Tests (dimensionalOS/dimos, 4.6k stars) and Test Guard (amElnagdy/guard-skills, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pytest Testing Assistant?
dmitriiweb (a GitHub user) maintains it in dmitriiweb/extract-emails, which has 111 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on January 2, 2026.
Source: dmitriiweb/extract-emails on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.