Install any skill in seconds. Free to start, no credit card required.
Get Started Free →posit-dev/r-cli-app
Build command-line apps in R using the Rapp package.
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
and 19 more in the full report
13 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
After installing the Rapp package on a system, what R command should be run once to put the Rapp executable launcher on the system PATH for the current user?
| Checked | Without skill | With skill |
|---|---|---|
| The launcher is installed using Rapp::install_pkg_cli_apps("Rapp"). | Missed | Passed |
The instructions your model reads when the skill loads.
Rapp (v0.3.0) is an R package that provides a drop-in replacement for Rscript
that automatically parses command-line arguments into R values. It turns simple
R scripts into polished CLI apps with argument parsing, help text, and subcommand
support — with zero boilerplate.
R ≥ 4.1.0 | CRAN: install.packages("Rapp") | GitHub: r-lib/Rapp
After installing, put the Rapp launcher on PATH:
Rapp::install_pkg_cli_apps("Rapp")
This places the Rapp executable in ~/.local/bin (macOS/Linux) or
%LOCALAPPDATA%\Programs\R\Rapp\bin (Windows).
Rapp scans top-level expressions of an R script and converts specific patterns into CLI constructs. This means:
source() and as a CLI tool.Only top-level assignments are recognized. Assignments inside functions, loops, or conditionals are not parsed as CLI arguments.
This table is the heart of Rapp — each R pattern automatically maps to a CLI surface:
| R Top-Level Expression | CLI Surface | Notes |
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.