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

R Package Check

by ipea in 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.

No licenceAuto-check: notesTesting & QA

Install R Package Check

skills CLI
$ npx skills add ipea/geobr --skill r-package-check -a claude-code

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

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

At a glance

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 in 7 steps: Pre-Flight Report → Document → Test → …
  • The user says check my R package
  • SKILL.md covers Constraints, Workflow Phases, Important and Long-running checks: use the…
  • Calls git

What it does

R Package Check is an agent skill from 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. Use when the user says "check my R package", "R CMD check", "is this package CRAN-ready", "run devtools::check", "prepare for CRAN submission", or asks about the R side of geobr. Produces a check report + CRAN-submission checklist in qualityreports/.

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 Test generation. 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 check my R package
  • Is this package CRAN-ready
  • Run devtools::check
  • Prepare for CRAN submission

Example prompts

  • “check my R package”
  • “R CMD check”
  • “is this package CRAN-ready”
  • “/r-package-check”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, Write, Task, Monitor

Workflow steps

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

  1. Pre-Flight Report
  2. Document
  3. Test
  4. Check (--as-cran)
  5. Coverage (optional)
  6. Source Review
  7. Release Gate + Report

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
    • Task
    • Monitor

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, 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

R Package Check loads about 1.5k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 406 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, Write, Task, Monitor

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

“Run the document → test → check → triage pipeline that decides whether an R package is releasable, then review the source for the issues R CMD check cannot see.”

— opening of SKILL.md by ipea
name
r-package-check
allowed-tools
Read, Grep, Glob, Bash, Write, Task, Monitor
author
Claude Code Academic Workflow
version
1.0.0
argument-hint
[--no-check to skip R CMD check; defaults to r-package/]
disable-model-invocation
true
effort
high

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/r-package-check of ipea/geobr.

Open the folder on GitHubat commit 0969f92

Compare with similar skills

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

R Package Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
R Package Check this skillipea/geobr959—~1.5kAutomated safety check: NotesNone
Emcaklofas/kicad-happy1.4k1 repos~2.8kAutomated safety check: PassMIT
Swig Testswig/swig6.3k—~2.3kAutomated safety check: PassCustom licence
Generate Test Cases342164796/generate-test-cases1191 repos~2.9kAutomated safety check: PassNone
Verify Cc Safety Netkenryu42/cc-safety-net1.6k—~2kAutomated safety check: PassMIT
Wioworkersio/skills190—~5.8kAutomated safety check: PassMIT

Similar skills

  • Emc

    aklofas/kicad-happy

    EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…

    1.4k GitHub starsUsed in 1 repo~2.8k tokens
    Testing & QAAuto-check passed

  • Swig Test

    swig/swig

    Run SWIG test suite for specific languages. An agent skill from swig/swig.

    6.3k GitHub stars~2.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Generate Test Cases

    342164796/generate-test-cases

    自主学习型测试文档生成器。从需求文档（Markdown）生成测试用例 XMind 文件，支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。

    119 GitHub starsUsed in 1 repo~2.9k tokens
    Testing & QAAuto-check passed

  • Verify Cc Safety Net

    kenryu42/cc-safety-net

    Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.

    1.6k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed

  • Wio

    workersio/skills

    Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.

    190 GitHub stars~5.8k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

  • File Server

    microsoft/WindowsProtocolTestSuites

    Official

    ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…

    567 GitHub stars~4.1k tokensUpdated 22 days ago
    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

  • Diagnose

    ipea/geobr

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

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

  • 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

Categories

Questions about R Package Check

What does R Package Check do?

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. R Package Check is an agent skill from 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.

When should I use R Package Check?

R Package Check fits situations like: the user says check my R package; is this package CRAN-ready; run devtools::check; prepare for CRAN submission.

How do I install R Package Check in Claude Code?

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

How do I install R Package Check in Codex?

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

Can I use R Package Check 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 r-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/r-package-check, .gemini/skills/r-package-check, .github/skills/r-package-check and .opencode/skills/r-package-check in your project.

What does R Package Check need to run?

Going by SKILL.md and its folder, R Package Check needs the command-line tools its instructions call (git). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Write, Task, Monitor.

Does R Package Check access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is R Package Check safe to install?

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.

What licence does R Package Check use?

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

How many tokens does R Package Check use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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 R Package Check?

Skills that share tags, products or a category with R Package Check: Emc (aklofas/kicad-happy, 1.4k stars), Swig Test (swig/swig, 6.3k stars), Generate Test Cases (342164796/generate-test-cases, 119 stars) and Verify Cc Safety Net (kenryu42/cc-safety-net, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains R Package Check?

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.