Gumroad Prod Console
antiwork/gumroad
Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.
Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic.
$ npx skills add rigortype/rigor --skill rigor-rbs-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rigortype/rigor rigor-rbs-setup --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/rigortype/rigor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rigor-rbs-setup .claude/skills/rigor-rbs-setup && 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 "rigor-rbs-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-rbs-setup into .claude/skills/rigor-rbs-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-rbs-setup", 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/rigortype/rigor/tree/master/skills/rigor-rbs-setupType 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 rigortype/rigor --skill rigor-rbs-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rigortype/rigor rigor-rbs-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rigor-rbs-setup .agents/skills/rigor-rbs-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rigor-rbs-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-rbs-setup into .agents/skills/rigor-rbs-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-rbs-setup", 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 rigortype/rigor --skill rigor-rbs-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rigortype/rigor rigor-rbs-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rigor-rbs-setup .cursor/skills/rigor-rbs-setup && 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 "rigor-rbs-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-rbs-setup into .cursor/skills/rigor-rbs-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-rbs-setup", 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/rigortype/rigor.git --path skills/rigor-rbs-setup--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 rigortype/rigor --skill rigor-rbs-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rigortype/rigor rigor-rbs-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rigor-rbs-setup .gemini/skills/rigor-rbs-setup && 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 "rigor-rbs-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-rbs-setup into .gemini/skills/rigor-rbs-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-rbs-setup", 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 rigortype/rigor rigor-rbs-setupInstalls 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 rigortype/rigor --skill rigor-rbs-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rigor-rbs-setup .github/skills/rigor-rbs-setup && 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 "rigor-rbs-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-rbs-setup into .github/skills/rigor-rbs-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-rbs-setup", 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 rigortype/rigor --skill rigor-rbs-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rigortype/rigor rigor-rbs-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rigortype/rigor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rigor-rbs-setup .opencode/skills/rigor-rbs-setup && 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 "rigor-rbs-setup" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-rbs-setup into .opencode/skills/rigor-rbs-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-rbs-setup", 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.
rigor-rbs-setupInstall community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic.
Rigor Rbs Setup is an agent skill from rigortype/rigor. Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic. Use when rbs collection is missing or untyped gems limit coverage; not for first-time Rigor setup or a gem with no community RBS entry.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Ruby. The repository describes itself as: Inference-first static analysis for Ruby. The licence is MPL-2.0.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 57a67cf. 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.
Shell commands in SKILL.md call:
bundlegemFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom 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.
Rigor Rbs Setup loads about 1.2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 630 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 rigortype/rigor at commit 57a67cf, republished under its MPL-2.0 licence (© rigortype). 630 words, ~1,230 tokens.
.claude/skills/rigor-rbs-setup/SKILL.md (or your agent's skills folder).Most of what Rigor cannot type on a real application is the surface of
third-party gems that ship no RBS: a call into such a gem returns
Dynamic, so every downstream method on the result is unprotected and
some genuine bugs go uncaught. The Ruby ecosystem's answer is the
community RBS collection at
ruby/gem_rbs_collection;
this skill wires it into the project.
This skill's exact commands, flags, and config keys drift between Rigor releases, so follow the copy that ships with the installed Rigor rather than any vendored or frozen copy of this file. Get the complete current procedure in one call:
rigor skill --full rigor-rbs-setupIf you already loaded this skill via rigor skill you have the current
copy — just proceed. If rigor is not on PATH, this task needs it: run
rigor-next-steps to install Rigor first, then come back.
rigor check ends with info: N gem(s) in Gemfile.lock have no RBS available: … — that list is the gap this skill closes.Dynamic and you want Rigor to see through it.rigor-project-init first.rigor-plugin-author (if
it is your own DSL) or a Rigor issue (if it is a popular gem worth
built-in support).Rigor auto-detects rbs_collection.lock.yaml at the project root
(rbs_collection.auto_detect defaults to true) and feeds each gem's
downloaded RBS directory into its signature paths, skipping stdlib
entries it already bundles. No .rigor.yml change is required — the
lockfile's presence is the whole wiring. (Set rbs_collection.lockfile:
only if the lockfile lives somewhere other than the project root.)
rigor checkRead the closing info line listing the gems with no RBS. That is your
target set.
rbs CLI availablerbs collection is part of the rbs gem and reads the project's
Gemfile.lock. Check it is runnable:
rbs --version # or: bundle exec rbs --versionIf it is missing, add it to the project's development group
(bundle add rbs --group development) or install it standalone
(gem install rbs). Prefer bundle exec rbs … when rbs is in the
Gemfile so it matches the project's resolved versions.
rbs collection initThis writes rbs_collection.yaml (which gems to pull, which to ignore).
Skip if the file already exists; review it either way — the default
pulls RBS for every gem in the lockfile that the collection knows.
rbs collection install # bundle exec rbs collection install when bundledThis resolves against ruby/gem_rbs_collection, writes
rbs_collection.lock.yaml, and downloads the .rbs files into
.gem_rbs_collection/.
rigor checkTwo things to confirm:
info "no RBS available" list shrank — the gems now covered
dropped off it.rigor baseline regenerate) so the new envelope is recorded.# rigor:disable <rule> the
site with a reason, or pin the gem out in rbs_collection.yaml.Commit the config + lockfile, gitignore the download dir:
# .gitignore
.gem_rbs_collection/Commit rbs_collection.yaml and rbs_collection.lock.yaml so every
contributor and CI resolves the same RBS. .gem_rbs_collection/ is
regenerable from the lockfile (rbs collection install), so it is not
committed.
Re-run rigor skill describe — with the gem-RBS foundation in place it
will route you to the next move (CI wiring, baseline work, or protection
uplift).
© rigortype, MPL-2.0. 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 skills/rigor-rbs-setup of rigortype/rigor.
Open the folder on GitHubat commit 57a67cf
Rigor Rbs Setup 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 |
|---|---|---|---|---|---|---|
| Rigor Rbs Setup this skillrigortype/rigor | 106 | — | ~1.2k | Automated safety check: Pass | MPL-2.0 | |
| Gumroad Prod Consoleantiwork/gumroad | 9.8k | — | ~2.9k | Automated safety check: Notes | MIT | |
| Fastlane Pull Request Reviewfastlane/fastlane | 42k | — | ~550 | Automated safety check: Pass | MIT | |
| Dependency UpdaterAsvarox/allkaraoke | 261 | 4 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Wise APIlineofflight/frankfurter | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Write RbsDataDog/dd-trace-rb | 417 | — | ~805 | Automated safety check: Pass | Custom licence |
antiwork/gumroad
Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.
fastlane/fastlane
Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.
Asvarox/allkaraoke
Smart dependency management for any language. An agent skill from Asvarox/allkaraoke.
lineofflight/frankfurter
A skill your agent uses when querying Wise for exchange rates (real-time or historical), validating Frankfurter rates against Wise mid-market, debugging rate discrepancies, or when the user mentions…
DataDog/dd-trace-rb
A skill your agent uses when writing, reviewing, or modifying RBS type signatures (sig//.rbs, vendor/rbs//.rbs, or inline : annotations) or running Steep – e.g.
ruby-git/ruby-git
Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…
rigortype/rigor
Measure Rigor's baseline drift across the tagged history of a real OSS Ruby project.
rigortype/rigor
Adjudicate a rigor unused report safely before proposing dead-code removal.
rigortype/rigor
Reduce an existing .rigor-baseline.yml rule by rule by triaging sites, fixing or intentionally suppressing them, and regenerating the baseline.
rigortype/rigor
Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy.
rigortype/rigor
Author a new Rigor plugin, choosing plugins/ for production support or examples/ for a contract walkthrough.
rigortype/rigor
Author a Rigor plugin in an adopting project or standalone rigor- gem for a DSL, framework, or metaprogramming pattern.
Works with
Categories
Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic. Rigor Rbs Setup is an agent skill from rigortype/rigor. Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic.
Rigor Rbs Setup fits situations like: rbs collection is missing; untyped gems limit coverage; not for first-time Rigor setup; A gem with no community RBS entry.
Run `npx skills add rigortype/rigor --skill rigor-rbs-setup -a claude-code`. Or copy the skill folder (skills/rigor-rbs-setup in rigortype/rigor) into .claude/skills/rigor-rbs-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rigortype/rigor --skill rigor-rbs-setup -a codex`. Or copy the skill folder (skills/rigor-rbs-setup in rigortype/rigor) into .agents/skills/rigor-rbs-setup 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 rigortype/rigor --skill rigor-rbs-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rigor-rbs-setup, .gemini/skills/rigor-rbs-setup, .github/skills/rigor-rbs-setup and .opencode/skills/rigor-rbs-setup in your project.
Going by SKILL.md and its folder, Rigor Rbs Setup needs the command-line tools its instructions call (bundle and gem).
SKILL.md names 1 domain. As links in the text: github.com. 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.
Rigor Rbs Setup is published under the MPL-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Rigor Rbs Setup: Gumroad Prod Console (antiwork/gumroad, 9.8k stars), Fastlane Pull Request Review (fastlane/fastlane, 42k stars), Dependency Updater (Asvarox/allkaraoke, 261 stars) and Wise API (lineofflight/frankfurter, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rigortype (a GitHub organization) maintains it in rigortype/rigor, which has 106 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 8, 2026.
Source: rigortype/rigor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.