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…
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.
$ npx skills add ipea/geobr --skill py-package-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ipea/geobr py-package-check --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/ipea/geobr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/py-package-check .claude/skills/py-package-check && 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 "py-package-check" agent skill from https://github.com/ipea/geobr/tree/master/.claude/skills/py-package-check into .claude/skills/py-package-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "py-package-check", 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/ipea/geobr/tree/master/.claude/skills/py-package-checkType 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 ipea/geobr --skill py-package-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ipea/geobr py-package-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ipea/geobr.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/py-package-check .agents/skills/py-package-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "py-package-check" agent skill from https://github.com/ipea/geobr/tree/master/.claude/skills/py-package-check into .agents/skills/py-package-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "py-package-check", 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 ipea/geobr --skill py-package-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ipea/geobr py-package-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ipea/geobr.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/py-package-check .cursor/skills/py-package-check && 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 "py-package-check" agent skill from https://github.com/ipea/geobr/tree/master/.claude/skills/py-package-check into .cursor/skills/py-package-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "py-package-check", 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/ipea/geobr.git --path .claude/skills/py-package-check--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 ipea/geobr --skill py-package-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ipea/geobr py-package-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ipea/geobr.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/py-package-check .gemini/skills/py-package-check && 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 "py-package-check" agent skill from https://github.com/ipea/geobr/tree/master/.claude/skills/py-package-check into .gemini/skills/py-package-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "py-package-check", 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 ipea/geobr py-package-checkInstalls 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 ipea/geobr --skill py-package-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ipea/geobr.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/py-package-check .github/skills/py-package-check && 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 "py-package-check" agent skill from https://github.com/ipea/geobr/tree/master/.claude/skills/py-package-check into .github/skills/py-package-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "py-package-check", 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 ipea/geobr --skill py-package-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ipea/geobr py-package-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ipea/geobr.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/py-package-check .opencode/skills/py-package-check && 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 "py-package-check" agent skill from https://github.com/ipea/geobr/tree/master/.claude/skills/py-package-check into .opencode/skills/py-package-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "py-package-check", 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.
py-package-checkRun 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.
Py Package Check is an agent skill from 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. Use when the user says "check the python package", "run pytest", "is the python side ready", "prepare a PyPI release", or points at python-package/. Produces a check report in qualityreports/. Mirrors .github/workflows/Python-CMD-check.yaml so local and CI cannot diverge.
Its SKILL.md is about 1.4k 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 and Test generation. It works with Python, GitHub Actions and pytest. The repository describes itself as: Easy access to official spatial data sets of Brazil in R and Python.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 0969f92. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBashWriteTaskMonitorFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvpipFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
docs.astral.shFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Py Package Check loads about 1.4k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 408 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Grep, Glob, Bash, Write, Task, MonitorAutomated 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.
Without a licence we can't republish the file, so here is its outline and opening line. It has 408 words (~1,401 tokens).
“The Python counterpart to /r-package-check. Sync → test → build → review, then a verdict.”
Just SKILL.md in .claude/skills/py-package-check of ipea/geobr.
Open the folder on GitHubat commit 0969f92
Py Package Check 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 |
|---|---|---|---|---|---|---|
| Py Package Check this skillipea/geobr | 959 | — | ~1.4k | Automated safety check: Notes | None | |
| Adk Verify Snippetsgoogle/adk-python | 22k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Hermetic Python Unit TestsdimensionalOS/dimos | 4.6k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Simple Modern Uvjlevy/simple-modern-uv | 301 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Test Coverage Reviewareed1192/finance-news-aggregator | 149 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Testing Livekit Agentslivekit-examples/agent-starter-python | 264 | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
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…
dimensionalOS/dimos
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.
jlevy/simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.
areed1192/finance-news-aggregator
Audit, plan, write, and verify unit tests for Python projects using pytest.
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).
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.
ipea/geobr
Extract reusable knowledge from the current session into a persistent skill.
ipea/geobr
Save a structured state snapshot the next session can resume from — active plan, decisions and why, file pointers with line numbers, open questions, next 1-3 actions, and what to deliberately forget.
ipea/geobr
Deep consistency audit of the geobr repository — configuration, documentation, and the two packages.
ipea/geobr
Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing.
ipea/geobr
Check R↔Python API parity across geobr's two packages — which read functions exist on one side but not the other, and where matched functions disagree on argument names, defaults, or the metadata…
ipea/geobr
Run the full R package release gate — regenerate docs, run the test suite, run R CMD check --as-cran, and triage every ERROR / WARNING / NOTE against CRAN policy before a release or submission.
Works with
Categories
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. Py Package Check is an agent skill from 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.
Py Package Check fits situations like: the user says check the python package; is the python side ready; prepare a PyPI release; points at python-package/.
Run `npx skills add ipea/geobr --skill py-package-check -a claude-code`. Or copy the skill folder (.claude/skills/py-package-check in ipea/geobr) into .claude/skills/py-package-check in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ipea/geobr --skill py-package-check -a codex`. Or copy the skill folder (.claude/skills/py-package-check in ipea/geobr) into .agents/skills/py-package-check in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ipea/geobr --skill py-package-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/py-package-check, .gemini/skills/py-package-check, .github/skills/py-package-check and .opencode/skills/py-package-check in your project.
Going by SKILL.md and its folder, Py Package Check needs the command-line tools its instructions call (uv and pip). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Write, Task, Monitor.
SKILL.md names 1 domain. In commands or code: docs.astral.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
No licence was found for Py Package Check or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Py Package Check: Adk Verify Snippets (google/adk-python, 22k stars), Hermetic Python Unit Tests (dimensionalOS/dimos, 4.6k stars), Simple Modern Uv (jlevy/simple-modern-uv, 301 stars) and Test Coverage Review (areed1192/finance-news-aggregator, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ipea (a GitHub organization) maintains it in ipea/geobr, which has 959 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 27, 2026.
Source: ipea/geobr on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.