Explore AI Agent Skills & Claude Prompts

Help users write correct R code for async, parallel, and distributed computing using mirai. Use when users need to: run R code asynchronously or in parallel, write mirai code with correct dependency passing, set up local or remote parallel workers, convert code from future or parallel, use parallel map operations, integrate async tasks with Shiny or promises, or configure cluster/HPC computing.

r-expert

R language expert skill. Use when writing, reviewing, or debugging R code, or when the user asks for R best practices, idiomatic R, or guidance on the R ecosystem. Covers base R, tidyverse style, vectorization, pipe usage, error handling, and performance patterns. Complements r-lib (package dev) and shiny (web apps) — this skill focuses on the language itself.

r-lib-cli-app

Build command-line apps in R using the Rapp package. Use when creating a CLI tool in R, adding argument parsing to an R script, turning an R script into a command-line app, shipping CLIs in an R package, or using Rapp (the alternative Rscript front-end). Also use for shebang scripts, exec/ directory in R packages, or subcommand-based R tools.

r-lib-cli

Comprehensive R package for command-line interface styling, semantic messaging, and user communication. Use this skill when working with R code that needs to: (1) Format console output with inline markup and colors, (2) Display errors, warnings, or messages with cli_abort/cli_warn/cli_inform, (3) Show progress indicators for long-running operations, (4) Create semantic CLI elements (headers, lists, alerts, code blocks), (5) Apply themes and customize output styling, (6) Handle pluralization in user-facing text, (7) Work with ANSI strings, hyperlinks, or custom containers. Also use when migrating from base R message/warning/stop, debugging cli code, or improving existing cli usage.

r-lib-cran-extrachecks

Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback. Covers documentation requirements, DESCRIPTION field standards, URL validation, examples, and administrative requirements.

r-lib-lifecycle

Guidance for managing R package lifecycle according to tidyverse principles using the lifecycle package. Use when: (1) Setting up lifecycle infrastructure in a package, (2) Deprecating functions or arguments, (3) Renaming functions or arguments, (4) Superseding functions, (5) Marking functions as experimental, (6) Understanding lifecycle stages (stable, experimental, deprecated, superseded), or (7) Writing deprecation helpers for complex scenarios.

r-lib-package-dev

Orchestrates the full R package development lifecycle: project creation, directory structure, devtools workflow, documentation with roxygen2, code formatting with air, NEWS.md conventions, and CRAN readiness. Load this skill when the user is building, maintaining, or improving an R package. For deep-dive topics, this skill delegates to specialized siblings: r-lib-testing (testthat patterns), r-lib-cli (user-facing messages), r-lib-lifecycle (deprecation/versioning), and r-lib-cran-extrachecks (CRAN submission checklist).

r-lib-testing

Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.

go-secure

Secure Go error handling and information leakage prevention. Use whenever writing Go code that handles errors in APIs, services, or any code that crosses trust boundaries — HTTP handlers, gRPC services, CLI tools with user-facing output. Also trigger when reviewing Go error handling, implementing structured logging, or when the user mentions security, error sanitization, or preventing data leaks through error messages — even if they don't explicitly say "security". Covers domain error types, trust boundary translation, log redaction with slog, and safe API responses.

report-skill-issue

Report issues with skills to their upstream repository. Use when a skill produces errors, unexpected behavior, incorrect output, or fails silently. Also trigger when the user says things like "this skill is broken", "file a bug for this skill", "report this to the skill author", or when you notice a skill behaving incorrectly during normal use. Even if the user doesn't explicitly ask, offer to report the issue if you observe a clear skill defect.

rust-explain

Teaching assistant for reading and navigating Rust code. Use when reading an unfamiliar Rust codebase, when Rust is pasted with a question, when the borrow checker or a rustc error is confusing, when a generated Rust kernel needs a correctness sanity-check, or when asked to explain a specific Rust construct (lifetimes, trait objects, Arc<Mutex<T>>, a macro, an iterator chain). Also triggers on "explain this Rust", "what does this Rust do", "why doesn't this compile", reading ownership/borrowing, FFI/unsafe blocks, or numeric crates (ndarray, nalgebra, faer, polars, rayon).

schedule Updated 24 days ago

shiny-bslib-theming

Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bs_theme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection, or making R plots match the app theme with thematic.