# R Cran Status

Look up an R package's live status on cran.r-project.org - submission/review state...

- Repository: https://github.com/posit-dev/skills (551 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add posit-dev/skills --skill r-cran-status -g -a claude-code -y`
Codex: `npx skills add posit-dev/skills --skill r-cran-status -g -a codex -y`
Cursor: `npx skills add posit-dev/skills --skill r-cran-status -g -a cursor -y`
Gemini CLI: `npx skills add posit-dev/skills --skill r-cran-status -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add posit-dev/skills`

## Description

Look up an R package's live status on cran.r-project.org - submission/review state (queue, human review, waiting, archived, past version's fate) or R CMD check results (OK/NOTE/WARN/ERROR per platform). Use for "what's the CRAN status of X", "did X get accepted/rejected", "is X passing CRAN checks", "when was version Y archived", "did win-builder get my package", "is win-builder processing my submission".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# CRAN Package Status

Check a package's submission/review state, a specific historical version's
fate (e.g. `{package} {version}`, as in `btw v1.4.0`), or its current
`R CMD check` results across CRAN's test platforms.

"CRAN status" is ambiguous between two questions:

- **Submission status**: is/was this package (or version) in review,
  published, archived, or rejected? See "Submission Status".
- **Check results**: is the published version passing `R CMD check` on all
  platforms, or does it have WARN/ERROR/NOTE flags risking removal? See
  "Check Results".

CRAN's servers are a shared, unpaid resource. Never issue requests in
parallel or in a tight loop, pause briefly (e.g. `sleep 1`) between
requests, stop looping as soon as a match is found, and avoid re-fetching a
page you've already checked in this session.

## Workflow

1. Ask for the package name if not provided. A version may also be given
   (e.g. `btw v1.4.0` or `btw 1.4.0`); strip any leading `v`.
2. Decide which question is being asked:
   - Version given, or request mentions submission, review, the queue, or
     rejection/archival → **Submission Status**.
   - Request mentions checks, `R CMD check`, WARN/ERROR/NOTE, or
     platforms/flavors → **Check Results**.
   - Request mentions win-builder, `check_win_devel()`, or whether a
     submission arrived → **Win-Builder**.
   - If genuinely ambiguous (e.g. just "check the CRAN status of x"), ask
     which is meant, or check both and report both.
3. Follow the relevant section below and report the result.

## Submission Status

The rest: https://github.com/posit-dev/skills/blob/HEAD/r-lib/r-cran-status/SKILL.md