Agent skill

Rigor Rbs Setup

by rigortype in rigortype/rigor

Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic.

MPL-2.0Auto-check passedDevelopment

Install Rigor Rbs Setup

skills CLI
$ npx skills add rigortype/rigor --skill rigor-rbs-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rigortype/rigor rigor-rbs-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
rigor-rbs-setup
GitHub stars
106
Token cost
~1.2k tokens
SKILL.md length
630 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
MPL-2.0

At a glance

Install community RBS for a project's gems so Rigor can type dependencies that currently become Dynamic.

  • Works in 6 steps: see the gap → make the rbs CLI available → initialise the collection config (first… → …
  • Rbs collection is missing
  • SKILL.md covers First: load the…, When to use, When NOT to use and How Rigor consumes it (so you…, plus 2 more sections
  • Calls bundle and gem

What it does

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.

When your agent uses it

  • Rbs collection is missing
  • Untyped gems limit coverage
  • Not for first-time Rigor setup
  • A gem with no community RBS entry

Example prompts

  • “/rigor-rbs-setup”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. see the gap
  2. make the rbs CLI available
  3. initialise the collection config (first time only)
  4. install
  5. verify (re-check; watch for new diagnostics)
  6. commit

What it can do on your machine

Read from SKILL.md and the folder at commit 57a67cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • bundle
    • gem

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from rigortype/rigor at commit 57a67cf, republished under its MPL-2.0 licence (© rigortype). 630 words, ~1,230 tokens.

Download SKILL.mdSave it as .claude/skills/rigor-rbs-setup/SKILL.md (or your agent's skills folder).
name
rigor-rbs-setup
description
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.
license
MPL-2.0
metadata.version
0.1.0
metadata.homepage
https://github.com/rigortype/rigor

Rigor RBS Setup

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.

First: load the version-current copy

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:

sh
rigor skill --full rigor-rbs-setup

If 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.

When to use

  • rigor check ends with info: N gem(s) in Gemfile.lock have no RBS available: … — that list is the gap this skill closes.
  • A deep call chain into a gem (an HTTP client, a parser, a service object) types as Dynamic and you want Rigor to see through it.

When NOT to use

  • The project has no Rigor config yet — run rigor-project-init first.
  • A specific gem you need is not in the community collection — RBS setup will not cover it. That residue is for rigor-plugin-author (if it is your own DSL) or a Rigor issue (if it is a popular gem worth built-in support).

How Rigor consumes it (so you know what "done" looks like)

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.)

Procedure

Phase 1 — see the gap
sh
rigor check

Read the closing info line listing the gems with no RBS. That is your target set.

Phase 2 — make the rbs CLI available

rbs collection is part of the rbs gem and reads the project's Gemfile.lock. Check it is runnable:

sh
rbs --version            # or: bundle exec rbs --version

If 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.

Show full SKILL.md (231 more words)Show less
Phase 3 — initialise the collection config (first time only)
sh
rbs collection init

This 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.

Phase 4 — install
sh
rbs collection install      # bundle exec rbs collection install when bundled

This resolves against ruby/gem_rbs_collection, writes rbs_collection.lock.yaml, and downloads the .rbs files into .gem_rbs_collection/.

Phase 5 — verify (re-check; watch for new diagnostics)
sh
rigor check

Two things to confirm:

  1. The info "no RBS available" list shrank — the gems now covered dropped off it.
  2. No surprising new diagnostics. Community RBS occasionally ships a signature stricter than the gem's real runtime behaviour, which can surface a false positive. Treat the diff like any other:
    • In acknowledge mode, regenerate the baseline (rigor baseline regenerate) so the new envelope is recorded.
    • For a genuine new error the sharper types caught, that is a win — fix it.
    • For a clear RBS-quality false positive, # rigor:disable <rule> the site with a reason, or pin the gem out in rbs_collection.yaml.
Phase 6 — commit

Commit the config + lockfile, gitignore the download dir:

sh
# .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.

Next step

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

Files

Just SKILL.md in skills/rigor-rbs-setup of rigortype/rigor.

Open the folder on GitHubat commit 57a67cf

Compare with similar skills

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.

Rigor Rbs Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rigor Rbs Setup this skillrigortype/rigor106—~1.2kAutomated safety check: PassMPL-2.0
Gumroad Prod Consoleantiwork/gumroad9.8k—~2.9kAutomated safety check: NotesMIT
Fastlane Pull Request Reviewfastlane/fastlane42k—~550Automated safety check: PassMIT
Dependency UpdaterAsvarox/allkaraoke2614 repos~3.5kAutomated safety check: PassMIT
Wise APIlineofflight/frankfurter2k—~1.1kAutomated safety check: PassMIT
Write RbsDataDog/dd-trace-rb417—~805Automated safety check: PassCustom licence

Similar skills

  • Gumroad Prod Console

    antiwork/gumroad

    Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.

    9.8k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.

    42k GitHub stars~550 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Dependency Updater

    Asvarox/allkaraoke

    Smart dependency management for any language. An agent skill from Asvarox/allkaraoke.

    261 GitHub starsUsed in 4 repos~3.5k tokens
    DevelopmentAuto-check passed
  • Wise API

    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…

    2k GitHub stars~1.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Write Rbs

    DataDog/dd-trace-rb

    Official

    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.

    417 GitHub stars~805 tokensUpdated today
    DevelopmentAuto-check passed
  • Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…

    1.8k GitHub stars~657 tokensUpdated 6 days ago
    DevelopmentAuto-check passed

More from rigortype/rigor

All 36 skills in this repo
  • Rigor Regression Sweep

    rigortype/rigor

    Measure Rigor's baseline drift across the tagged history of a real OSS Ruby project.

    106 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Adjudicate a rigor unused report safely before proposing dead-code removal.

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Rigor Baseline Reduce

    rigortype/rigor

    Reduce an existing .rigor-baseline.yml rule by rule by triaging sites, fixing or intentionally suppressing them, and regenerating the baseline.

    106 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Rigor Doctor

    rigortype/rigor

    Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy.

    106 GitHub stars~767 tokensUpdated today
    Auto-check passed
  • Rigor Plugin Author

    rigortype/rigor

    Author a new Rigor plugin, choosing plugins/ for production support or examples/ for a contract walkthrough.

    106 GitHub stars~3.3k tokensUpdated today
    Auto-check: notes
  • Rigor Plugin Author

    rigortype/rigor

    Author a Rigor plugin in an adopting project or standalone rigor- gem for a DSL, framework, or metaprogramming pattern.

    106 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Rigor Rbs Setup

What does Rigor Rbs Setup do?

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.

When should I use Rigor Rbs Setup?

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.

How do I install Rigor Rbs Setup in Claude Code?

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.

How do I install Rigor Rbs Setup in Codex?

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.

Can I use Rigor Rbs Setup in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Rigor Rbs Setup need to run?

Going by SKILL.md and its folder, Rigor Rbs Setup needs the command-line tools its instructions call (bundle and gem).

Does Rigor Rbs Setup access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Rigor Rbs Setup safe to install?

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.

What licence does Rigor Rbs Setup use?

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.

How many tokens does Rigor Rbs Setup use?

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.

What are the alternatives to Rigor Rbs Setup?

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.

Who maintains Rigor Rbs Setup?

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.