New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Diagnose

by ipea in ipea/geobr

Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing.

No licenceAuto-check passedTesting & QA

Install Diagnose

skills CLI
$ npx skills add ipea/geobr --skill diagnose -a claude-code

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

GitHub CLI
$ gh skill install ipea/geobr diagnose --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/ipea/geobr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/diagnose .claude/skills/diagnose && 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
diagnose
GitHub stars
959
Token cost
~1.5k tokens
SKILL.md length
631 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
None found

At a glance

Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing.

  • Works in 5 steps: Reproduce. Get the exact call, the exact… → Minimise. Reduce to the smallest failing… → Work the ladder. Rungs 1 → 5, in order.… → …
  • The user says why is this failing
  • SKILL.md covers Rung 1 — Network and proxy, Rung 2 — Stale cache, Rung 3 — Release-tag drift and Rung 4 — Upstream data change, plus 3 more sections
  • Calls uv; reaches cache.ipea.gov.br and github.com

What it does

Diagnose is an agent skill from ipea/geobr. Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing. Use when the user says "why is this failing", "read returns nothing", "could not download geobr metadata", "this worked yesterday", "R and Python disagree", "debug this download", or pastes a user bug report. Tuned to geobr's real failure modes: proxy, stale cache, release-tag drift, upstream re-release, and code-dispatch surprises. Use --no-fix to localize without editing.

Its SKILL.md is about 1.5k 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 Root cause analysis and QA and bug reports. It works with Python. The repository describes itself as: Easy access to official spatial data sets of Brazil in R and Python.

When your agent uses it

  • The user says why is this failing
  • Read returns nothing
  • Could not download geobr metadata
  • This worked yesterday

Example prompts

  • “why is this failing”
  • “read returns nothing”
  • “could not download geobr metadata”
  • “/diagnose”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): ["Read", "Grep", "Glob", "Bash", "Write"]

Workflow steps

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

  1. Reproduce. Get the exact call, the exact error, and sessionInfo() (R) or uv pip list
  2. Minimise. Reduce to the smallest failing call — usually one geography, one year, code = "all".
  3. Work the ladder. Rungs 1 → 5, in order. Record which rungs came back clean.
  4. Confirm the cause by making the symptom appear and disappear on demand. A fix you cannot
  5. Fix, unless --no-fix. Package source changes need maintainer sign-off — propose, do not

What it can do on your machine

Read from SKILL.md and the folder at commit 0969f92. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • ["Read"
    • "Grep"
    • "Glob"
    • "Bash"
    • "Write"]

    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

    Hosts in commands or code, which the agent is likely to contact:

    • cache.ipea.gov.br
    • github.com

    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

Diagnose loads about 1.5k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 631 words of instructions outside code blocks.

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

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 631 words (~1,526 tokens).

“Most geobr failures are environmental, not code. Work the ladder in order — each rung is cheaper than the one below it, and the top two explain the large majority of reports.”

— opening of SKILL.md by ipea
name
diagnose
allowed-tools
["Read", "Grep", "Glob", "Bash", "Write"]
author
geobr
version
2.0.0
argument-hint
[symptom, file, or pasted error] [--no-fix]
effort
high

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/diagnose of ipea/geobr.

Open the folder on GitHubat commit 0969f92

Compare with similar skills

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

Diagnose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Diagnose this skillipea/geobr959—~1.5kAutomated safety check: PassNone
Pipensx Bug Report Triagei3sey/pipensx220—~1.5kAutomated safety check: NotesGPL-3.0
Bug ReproducerAnastasiyaW/codex-claude-code-config154—~4.1kAutomated safety check: PassMIT
Playwright Screen Recordingliaohch3/claude-tap3.3k—~714Automated safety check: PassMIT
Supporthomebridge-plugins/homebridge-eufy223—~1.7kAutomated safety check: PassApache-2.0
cmux Package Test Bisectmanaflow-ai/cmux28k—~1.5kAutomated safety check: PassCustom licence

Similar skills

  • Pipensx Bug Report Triage

    i3sey/pipensx

    Decodes QR-code bug report photos and screenshots from the pipensx app into a log, then triages crashes and update, download or install failures.

    220 GitHub stars~1.5k tokensUpdated 5 days ago
    Testing & QAAuto-check: notes

  • Bug Reproducer

    AnastasiyaW/codex-claude-code-config

    Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.

    154 GitHub stars~4.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Screen Recording

    liaohch3/claude-tap

    Records headless Playwright sessions as .webm videos to show a bug fix working or to give pull request reviewers visual evidence.

    3.3k GitHub stars~714 tokensUpdated 15 days ago
    Testing & QAAuto-check passed

  • Support

    homebridge-plugins/homebridge-eufy

    Triage a GitHub issue using diagnostics archives and logs. An agent skill from homebridge-plugins/homebridge-eufy.

    223 GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • cmux Package Test Bisect

    manaflow-ai/cmux

    Finds which commit broke a failing Swift package suite in the cmux repo by bisecting on CI, then judges per test whether it went stale or the code regressed.

    28k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Sandbox Feedback Loop

    bagofwords1/bagofwords

    Build a runnable reproduce→fix→verify loop for a bug or feature in a fresh sandbox, and record it as a feedback-loop doc.

    458 GitHub stars~857 tokensUpdated today
    Testing & QAAuto-check passed

More from ipea/geobr

All 9 skills in this repo

  • Learn

    ipea/geobr

    Extract reusable knowledge from the current session into a persistent skill.

    959 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check: notes

  • Checkpoint

    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.

    959 GitHub stars~1.4k tokensUpdated 10 days ago
    Auto-check: notes

  • Deep Audit

    ipea/geobr

    Deep consistency audit of the geobr repository — configuration, documentation, and the two packages.

    959 GitHub stars~1.8k tokensUpdated 10 days ago
    Auto-check: notes

  • Parity Check

    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…

    959 GitHub stars~1.4k tokensUpdated 10 days ago
    Auto-check: notes

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

    959 GitHub stars~1.4k tokensUpdated 10 days ago
    Auto-check: notes

  • R Package Check

    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.

    959 GitHub stars~1.5k tokensUpdated 10 days ago
    Auto-check: notes

Works with

Categories

Questions about Diagnose

What does Diagnose do?

Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing. Diagnose is an agent skill from ipea/geobr. Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing.

When should I use Diagnose?

Diagnose fits situations like: the user says why is this failing; read returns nothing; could not download geobr metadata; this worked yesterday.

How do I install Diagnose in Claude Code?

Run `npx skills add ipea/geobr --skill diagnose -a claude-code`. Or copy the skill folder (.claude/skills/diagnose in ipea/geobr) into .claude/skills/diagnose in your project. Claude Code loads it when a task matches its description.

How do I install Diagnose in Codex?

Run `npx skills add ipea/geobr --skill diagnose -a codex`. Or copy the skill folder (.claude/skills/diagnose in ipea/geobr) into .agents/skills/diagnose in your project. Codex loads it when a task matches its description.

Can I use Diagnose 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 ipea/geobr --skill diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnose, .gemini/skills/diagnose, .github/skills/diagnose and .opencode/skills/diagnose in your project.

What does Diagnose need to run?

Going by SKILL.md and its folder, Diagnose needs the command-line tools its instructions call (uv). Our summary lists: Python 3. Its frontmatter pre-approves these tools: ["Read", "Grep", "Glob", "Bash", "Write"].

Does Diagnose access the network?

SKILL.md names 2 domains. In commands or code: cache.ipea.gov.br and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Diagnose 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 Diagnose use?

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

How many tokens does Diagnose use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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 Diagnose?

Skills that share tags, products or a category with Diagnose: Pipensx Bug Report Triage (i3sey/pipensx, 220 stars), Bug Reproducer (AnastasiyaW/codex-claude-code-config, 154 stars), Playwright Screen Recording (liaohch3/claude-tap, 3.3k stars) and Support (homebridge-plugins/homebridge-eufy, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Diagnose?

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.