Csharp Async
github/awesome-copilot
Get best practices for C async programming. An agent skill from github/awesome-copilot.
Help users write correct R code for async, parallel, and distributed computing using mirai.
$ npx skills add quarto-dev/quarto-r --skill mirai -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install quarto-dev/quarto-r mirai --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/quarto-dev/quarto-r.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mirai .claude/skills/mirai && rm -rf skills-srcUse ~/.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/
Install the "mirai" agent skill from https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/mirai into .claude/skills/mirai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirai", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/miraiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add quarto-dev/quarto-r --skill mirai -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install quarto-dev/quarto-r mirai --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarto-dev/quarto-r.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mirai .agents/skills/mirai && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mirai" agent skill from https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/mirai into .agents/skills/mirai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirai", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarto-dev/quarto-r --skill mirai -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install quarto-dev/quarto-r mirai --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarto-dev/quarto-r.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mirai .cursor/skills/mirai && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mirai" agent skill from https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/mirai into .cursor/skills/mirai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirai", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/quarto-dev/quarto-r.git --path .claude/skills/mirai--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add quarto-dev/quarto-r --skill mirai -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install quarto-dev/quarto-r mirai --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarto-dev/quarto-r.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mirai .gemini/skills/mirai && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mirai" agent skill from https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/mirai into .gemini/skills/mirai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirai", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install quarto-dev/quarto-r miraiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add quarto-dev/quarto-r --skill mirai -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/quarto-dev/quarto-r.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mirai .github/skills/mirai && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mirai" agent skill from https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/mirai into .github/skills/mirai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirai", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add quarto-dev/quarto-r --skill mirai -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install quarto-dev/quarto-r mirai --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/quarto-dev/quarto-r.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mirai .opencode/skills/mirai && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mirai" agent skill from https://github.com/quarto-dev/quarto-r/tree/main/.claude/skills/mirai into .opencode/skills/mirai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirai", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
miraiHelp users write correct R code for async, parallel, and distributed computing using mirai.
Mirai is an agent skill from quarto-dev/quarto-r. 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 parallel workers, convert from future or parallel, use miraimap, integrate with Shiny or promises, or configure cluster/HPC computing.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: R interface to quarto-cli. The licence is MIT.
Read from SKILL.md and the folder at commit bd2329a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are r).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mirai loads about 3k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 616 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from quarto-dev/quarto-r at commit bd2329a, republished under its MIT licence (© quarto-dev). 616 words, ~3,029 tokens.
.claude/skills/mirai/SKILL.md (or your agent's skills folder).mirai is a minimalist R framework for async, parallel, and distributed evaluation, built on nanonext.
mirai evaluates expressions in a clean environment on a daemon process. Nothing from the calling environment is available unless passed explicitly — this is the #1 source of mistakes.
# WRONG: my_data and my_func are not available on the daemon
m <- mirai(my_func(my_data))There are two ways to pass objects, and the names used must match the names referenced in the expression.
.args (recommended)Objects in .args populate the expression's local evaluation environment — available directly by name inside the expression.
m <- mirai(my_func(my_data), .args = list(my_func = my_func, my_data = my_data))... (dot-dot-dot)Objects passed via ... are assigned to the daemon's global environment. Use this when objects need to be found by R's standard scoping rules (e.g., helper functions called by other functions).
m <- mirai(my_func(my_data), my_func = my_func, my_data = my_data)# .args form — populates local eval env
process <- function(x, y) mirai(x + y, .args = environment())
# ... form — single unnamed environment, populates daemon global env
df_matrix <- function(x, y) mirai(as.matrix(rbind(x, y)), environment())| Scenario | Use |
|---|---|
| Data and simple functions | .args |
| Helper functions called by other functions that need lexical scoping | ... |
| Pass entire local scope to local eval env | .args = environment() |
| Pass entire local scope to daemon global env | mirai(expr, environment()) |
| Large objects shared across many tasks | everywhere() first, then reference by name |
Daemons start with no user packages loaded. Same applies inside mirai_map() callbacks.
# WRONG: dplyr is not loaded on the daemon
m <- mirai(filter(df, x > 5), .args = list(df = my_df))
# CORRECT: namespace-qualify
m <- mirai(dplyr::filter(df, x > 5), .args = list(df = my_df))
# CORRECT: load inside the expression
m <- mirai({
library(dplyr)
filter(df, x > 5)
}, .args = list(df = my_df))
# CORRECT: pre-load on all daemons
everywhere(library(dplyr))
m <- mirai(filter(df, x > 5), .args = list(df = my_df))m$data accesses the value but may still be unresolved. Use m[] (or collect_mirai(m)) to block until done; use unresolved(m) for a non-blocking check.
m <- mirai(slow_computation())
result <- m[] # blocks until resolved
if (!unresolved(m)) result <- m$data # non-blockingmirai() works without calling daemons() first — it launches a transient background process per call. Setting up daemons is only needed for persistent pools of workers.
# Start 4 local daemon processes (with dispatcher, the default)
daemons(4)
# Direct connection (no dispatcher) — lower overhead, round-robin scheduling
daemons(4, dispatcher = FALSE)
# Concise programmatic statistics (vs. the richer status())
info()
# Reset (daemons otherwise persist for the session)
daemons(0)with(daemons(...), {...}) creates daemons and automatically cleans them up when the block exits.
with(daemons(4), {
m <- mirai(expensive_task())
m[]
})local_daemons() and with_daemons() switch the active compute profile to one that already exists — they do not create daemons.
daemons(4, .compute = "workers")
# Switch active profile for the duration of the calling function
my_func <- function() {
local_daemons("workers")
mirai(task())[] # uses "workers" profile
}
# Switch active profile for a block
with_daemons("workers", {
m <- mirai(task())
m[]
})daemons(4, .compute = "cpu")
daemons(2, .compute = "gpu")
m1 <- mirai(cpu_work(), .compute = "cpu")
m2 <- mirai(gpu_work(), .compute = "gpu")memory + try_mirai())For high-throughput producers (Shiny, promises, ingest pipelines), use the memory argument to daemons() to cap the queued task payload at dispatcher (MB, metric). Pair it with try_mirai() so the host R thread never blocks on submission.
# 100 MB queue cap. mirai() blocks on submission once the queue is full.
daemons(4, memory = 100)
# try_mirai() returns NULL (invisibly) instead of blocking when the cap is hit.
m <- try_mirai(work(x), .args = list(x = x))
if (is.null(m)) {
# backpressure: drop, retry later, or signal upstream
} else {
# m is a regular mirai
}
# Inspect current and peak queue usage
status()$memorymemory requires dispatcher. Without dispatcher (or with memory = NULL), try_mirai() always returns a mirai.
Requires daemons to be set. Maps .x element-wise over a function, distributing across daemons. Namespace-qualify any package functions used inside the callback (see Mistake 2).
daemons(4)
# Basic map — collect with []
results <- mirai_map(1:10, function(x) x^2)[]
# Constants via .args, helpers via ... (same passing rules as mirai())
results <- mirai_map(
data_list,
function(x, power) helper(x, power),
.args = list(power = 3),
helper = my_helper_func
)[]
# Flatten results to a vector
results <- mirai_map(1:10, sqrt)[.flat]
# Progress bar (requires cli package)
results <- mirai_map(1:100, slow_task)[.progress]
# Early stopping on error
results <- mirai_map(1:100, risky_task)[.stop]
# Combine options
results <- mirai_map(1:100, task)[.stop, .progress]# Each row becomes arguments to the function
params <- data.frame(mean = 1:5, sd = c(0.1, 0.5, 1, 2, 5))
results <- mirai_map(params, function(mean, sd) rnorm(100, mean, sd))[]race_mirai)race_mirai() returns the integer index of the first resolved mirai in a list (or 0L if empty). Useful when you want to handle results in completion order rather than submission order.
remaining <- mirai_map(jobs, run)
while (length(remaining) > 0) {
idx <- race_mirai(remaining)
process(remaining[[idx]]$data)
remaining <- remaining[-idx]
}daemons(4)
# Load packages on all daemons
everywhere(library(DBI))
# Set up persistent connections
everywhere(con <<- dbConnect(RSQLite::SQLite(), db_path), db_path = tempfile())
# Export objects to daemon global environment via ...
# The empty {} expression is intentional — the point is to export objects via ...
everywhere({}, api_key = my_key, config = my_config)
# .min = N forces a synchronization point: the call must complete on at least
# N daemons before subsequent mirai evaluations proceed. Useful when launching
# remote daemons that connect over time.
everywhere(library(arrow), .min = 4)m <- mirai(stop("something went wrong"))
m[]
is_mirai_error(m$data) # TRUE for execution errors
is_mirai_interrupt(m$data) # TRUE for cancelled tasks
is_error_value(m$data) # TRUE for any error/interrupt/timeout
m$data$message # Error message
m$data$stack.trace # Full stack trace
m$data$condition.class # Original error classes
# Timeouts (requires dispatcher)
m <- mirai(Sys.sleep(60), .timeout = 5000) # 5-second timeout
# Cancellation (requires dispatcher)
m <- mirai(long_running_task())
stop_mirai(m)library(shiny)
library(bslib)
library(mirai)
daemons(4)
onStop(function() daemons(0))
ui <- page_fluid(
input_task_button("run", "Run Analysis"),
plotOutput("result")
)
server <- function(input, output, session) {
task <- ExtendedTask$new(
function(n) mirai(rnorm(n), .args = list(n = n))
) |> bind_task_button("run")
observeEvent(input$run, task$invoke(input$n))
output$result <- renderPlot(hist(task$result()))
}For high-traffic apps, set daemons(4, memory = ...) and submit with try_mirai() to apply backpressure without stalling the Shiny event loop.
library(promises)
mirai({Sys.sleep(1); "done"}) %...>% cat()daemons(
url = host_url(tls = TRUE),
remote = ssh_config(c("ssh://user@node1", "ssh://user@node2"))
)daemons(
n = 4,
url = local_url(tcp = TRUE),
remote = ssh_config("ssh://user@node1", tunnel = TRUE)
)daemons(
n = 1,
url = host_url(),
remote = cluster_config(
command = "sbatch",
options = "#SBATCH --job-name=mirai\n#SBATCH --mem=8G\n#SBATCH --array=1-50",
rscript = file.path(R.home("bin"), "Rscript")
)
)daemons(n = 2, url = host_url(), remote = http_config())| future | mirai |
|---|---|
| Auto-detects globals | Must pass all dependencies explicitly |
future({expr}) | mirai({expr}, .args = list(...)) |
value(f) | m[] or collect_mirai(m) |
plan(multisession, workers = 4) | daemons(4) |
plan(sequential) / reset | daemons(0) |
future_lapply(X, FUN) | mirai_map(X, FUN)[] |
future_map(X, FUN) (furrr) | mirai_map(X, FUN)[] |
future_promise(expr) | mirai(expr, ...) (auto-converts to promise) |
The key conversion step: identify all objects the expression uses from the calling environment and pass them explicitly via .args or ....
| parallel | mirai |
|---|---|
makeCluster(4) | daemons(4) or make_cluster(4) |
clusterExport(cl, "x") | Pass via .args / ..., or use everywhere() |
clusterEvalQ(cl, library(pkg)) | everywhere(library(pkg)) |
parLapply(cl, X, FUN) | mirai_map(X, FUN)[] |
parSapply(cl, X, FUN) | mirai_map(X, FUN)[.flat] |
mclapply(X, FUN, mc.cores = 4) | daemons(4); mirai_map(X, FUN)[] |
stopCluster(cl) | daemons(0) |
For code that already uses the parallel package extensively, make_cluster() provides a drop-in backend:
cl <- mirai::make_cluster(4)
parallel::parLapply(cl, 1:100, my_func)
mirai::stop_cluster(cl)
# R >= 4.5: native integration
cl <- parallel::makeCluster(4, type = "MIRAI")# Default: L'Ecuyer-CMRG stream per daemon (statistically safe, non-reproducible)
daemons(4)
# Reproducible: L'Ecuyer-CMRG stream per mirai call.
# Results are the same regardless of daemon count or scheduling.
daemons(4, seed = 42)# Synchronous mode — runs in the host process, supports browser()
daemons(sync = TRUE)
m <- mirai({
browser()
result <- tricky_function(x)
result
}, .args = list(tricky_function = tricky_function, x = my_x))
daemons(0)
# Capture daemon stdout/stderr
daemons(4, output = TRUE)Inside daemon callbacks (e.g., mirai_map), use local_url() + launch_local() instead of daemons(n) to avoid conflicting with the outer daemon pool.
mirai_map(1:10, function(x) {
daemons(url = local_url())
launch_local(2)
result <- mirai_map(1:5, function(y, x) x * y, .args = list(x = x))[]
daemons(0)
result
})[]© quarto-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/mirai of quarto-dev/quarto-r.
Open the folder on GitHubat commit bd2329a
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in quarto-dev/quarto-r, which our catalogue first saw on October 7, 2026.
Mirai 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mirai this skillquarto-dev/quarto-r | 160 | 1 repos | ~3k | Automated safety check: Pass | MIT | |
| Csharp Asyncgithub/awesome-copilot | 40k | 2 repos | ~466 | Automated safety check: Pass | MIT | |
| Correctcursor/plugins | 10k | 3 repos | ~612 | Automated safety check: Pass | None | |
| Parallels Discord Roundtripopenclaw/openclaw | 392k | — | ~788 | Automated safety check: Pass | MIT | |
| Openclaw Parallels Smokeopenclaw/openclaw | 392k | — | ~8.4k | Automated safety check: Notes | MIT | |
| CorrectionNxcoreAI/EverRoom | 3k | — | ~290 | Automated safety check: Pass | Custom licence |
github/awesome-copilot
Get best practices for C async programming. An agent skill from github/awesome-copilot.
cursor/plugins
Find the mistakes agents keep repeating in this repo and make each one impossible.
openclaw/openclaw
Run macOS Parallels smoke with Discord send, host verification, host reply, and guest readback proof.
openclaw/openclaw
Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.
NxcoreAI/EverRoom
Compute Room overview corrections—citation corrections as per-claim edits and general corrections as a single proposal.
onsi/gomega
Polling assertions in Gomega — Eventually (poll until it passes) and Consistently (must keep passing), the func(g Gomega) callback idiom, WithTimeout/WithPolling/Within/ProbeEvery, WithContext and…
quarto-dev/quarto-r
Create professional package release blog posts following Tidyverse or Shiny blog conventions.
quarto-dev/quarto-r
Create a release checklist and GitHub issue for an R package.
quarto-dev/quarto-r
Generate and improve accessible alt text for data visualizations and images in R packages and Quarto documents.
quarto-dev/quarto-r
Comprehensive R package for command-line interface styling, semantic messaging, and user communication.
quarto-dev/quarto-r
A skill your agent uses when the user is explicitly working with Quarto, .qmd files, quarto.yml, Quarto projects, or Quarto features such as callouts, cross-references, citations, Mermaid diagrams…
quarto-dev/quarto-r
Best practices for writing R package tests using testthat version 3+.
Help users write correct R code for async, parallel, and distributed computing using mirai. Mirai is an agent skill from quarto-dev/quarto-r. Help users write correct R code for async, parallel, and distributed computing using mirai.
Mirai fits situations like: users need to run R code asynchronously; write mirai code with correct dependency passing; set up parallel workers; convert from future.
Run `npx skills add quarto-dev/quarto-r --skill mirai -a claude-code`. Or copy the skill folder (.claude/skills/mirai in quarto-dev/quarto-r) into .claude/skills/mirai in your project. Claude Code loads it when a task matches its description.
Run `npx skills add quarto-dev/quarto-r --skill mirai -a codex`. Or copy the skill folder (.claude/skills/mirai in quarto-dev/quarto-r) into .agents/skills/mirai in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add quarto-dev/quarto-r --skill mirai -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mirai, .gemini/skills/mirai, .github/skills/mirai and .opencode/skills/mirai in your project.
SKILL.md names no scripts, command-line tools or credentials: Mirai is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Mirai is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Mirai: Csharp Async (github/awesome-copilot, 40k stars), Correct (cursor/plugins, 10k stars), Parallels Discord Roundtrip (openclaw/openclaw, 392k stars) and Openclaw Parallels Smoke (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
quarto-dev (a GitHub organization) maintains it in quarto-dev/quarto-r, which has 160 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 10, 2026.
Source: quarto-dev/quarto-r on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.