Agent skill · posit-dev
r-cran-status
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".
What it needs
About 4k tokens when loaded.
What this skill does
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. 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 1. Check the currently published version first (see below). 2. If no version was requested, or it matches the current version: report it as the current, published release. Skip to step 5 unless it's absent from PACKAGES, in which case continue to step 3. 3. If a prior check this conversation already located the package in a stage or reviewer folder, check that folder first, then forward from it in the pipeline order (see "CRAN Review Stages") — don't re-sweep from the start. Otherwise, sweep all stage and reviewer folders. 4. Search the incoming/ stage folders (see below). 5. Search the reviewer-assigned folders (see below). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posit-dev/r-cran-status