cran — resear surveycore, community, resear, ide skills, survey-analysis, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Essential for R Package Developer Agents requiring automated CRAN submission compliance checks. Core Survey Analysis Infrastructure

# Core Topics

resear survey-analysis
JDenn0514 JDenn0514
[0]
[0]
Updated: 3/3/2026

Agent Capability Analysis

The cran skill by JDenn0514 is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for resear, survey-analysis.

Ideal Agent Persona

Essential for R Package Developer Agents requiring automated CRAN submission compliance checks.

Core Value

Enables rigorous R package validation against CRAN's strict standards through automated `devtools::check()` execution and pre-approved note management. Provides infrastructure for comprehensive survey analysis and ensures adherence to R CMD check targets (0 errors, 0 warnings, ≤2 notes) as defined in r-package-conventions.md.

↓ Capabilities Granted for cran

Automating CRAN submission pre-flight checks
Validating R package documentation and DESCRIPTION files
Managing pre-approved CRAN submission notes
Executing comprehensive R CMD check routines

! Prerequisites & Limits

  • R-specific ecosystem only
  • Requires devtools dependency
  • Follows CRAN-specific conventions from r-package-conventions.md
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

cran

Install cran, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

CRAN Submission

Surveyverse projects: R CMD check targets (0 errors, 0 warnings, ≤2 notes), pre-approved notes, and devtools::check() cadence are defined in r-package-conventions.md §3. Those rules take precedence over generic guidance here.

The four-stage arc

StageWhat you're doingReference
PrepareDESCRIPTION, docs, URLs, admin — the things devtools::check() won't catchpreflight-checklist.md
CheckR CMD check --as-cran, platform testing, NOTE triagecheck-and-triage.md
SubmitBuild tarball, devtools::submit_cran(), write cran-comments.mdsubmit-and-respond.md
RespondPoint-by-point reviewer responses, resubmissionsubmit-and-respond.md

Tool map

TaskTool
Full local checkdevtools::check()
CRAN-style check (fast iteration)devtools::check(args = "--as-cran")
CRAN-style check (submission confidence)R CMD build . then R CMD check --as-cran pkg_x.y.z.tar.gz
Docs and examples onlydevtools::check_man()
Windows + R-develdevtools::check_win_devel()
Multi-platform preflightrhub::check_for_cran()
URL validationurlchecker::url_check()
Submit to CRANdevtools::submit_cran()
Generate release issue checklistusethis::use_release_issue()
Create cran-comments.mdusethis::use_cran_comments()
Create NEWS.mdusethis::use_news_md()
Bump versionusethis::use_version()

The CRAN mindset

CRAN checks run in a minimal, non-interactive environment with no hidden dependencies. Write code as if:

  • There is no network access during checks (examples, tests, vignettes)
  • Nothing is written outside tempdir()
  • There are no interactive prompts
  • Examples run in a few seconds each — not minutes
  • No binary executables are bundled in the source package

Prefer fixes that make checks green everywhere over explanations that justify fragility.

ERROR / WARNING / NOTE triage

  • ERRORs: Always blockers. Fix before submission.
  • WARNINGs: Almost always blockers. Very rare contextual exceptions.
  • NOTEs: Split into two types:
    • Actionable — fix it (undeclared dependency, broken URL, too-long examples)
    • Contextual — explain in cran-comments.md (incoming feasibility NOTE on new submissions)

When keeping a NOTE, cran-comments.md must answer:

  1. What is the NOTE?
  2. Why does it happen?
  3. Why is it safe / expected?
  4. What did you do to minimize it?
  1. devtools::check() is clean — 0 errors, 0 warnings
  2. Preflight checklist complete — see preflight-checklist.md
  3. Tarball check: R CMD build . → R CMD check --as-cran pkg_x.y.z.tar.gz
  4. Cross-platform: devtools::check_win_devel() at minimum; R-hub for broader coverage
  5. cran-comments.md written and reviewed
  6. Ready to respond point-by-point if CRAN asks

High-frequency failure surfaces

  • DESCRIPTION metadata: Title case, forbidden phrases, missing cph role
  • Documentation: Missing @return or @examples on exported functions
  • Examples: network calls, unseeded randomness, writes outside tempdir, commented-out code
  • URLs: HTTP instead of HTTPS, redirecting links
  • Undeclared dependencies: packages used in code/examples/tests but absent from DESCRIPTION
  • Package size / runtime: large embedded data, slow vignettes or examples

External resources

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is cran?

Essential for R Package Developer Agents requiring automated CRAN submission compliance checks. Core Survey Analysis Infrastructure

How do I install cran?

Run the command: npx killer-skills add JDenn0514/surveycore/cran. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for cran?

Key use cases include: Automating CRAN submission pre-flight checks, Validating R package documentation and DESCRIPTION files, Managing pre-approved CRAN submission notes, Executing comprehensive R CMD check routines.

Which IDEs are compatible with cran?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for cran?

R-specific ecosystem only. Requires devtools dependency. Follows CRAN-specific conventions from r-package-conventions.md.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add JDenn0514/surveycore/cran. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use cran immediately in the current project.

Related Skills

Looking for an alternative to cran or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI