Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to rigor skill describe.
Install Rigor Next Steps
$ npx skills add rigortype/rigor --skill rigor-next-steps -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rigortype/rigor rigor-next-steps --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-next-steps .claude/skills/rigor-next-steps && 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-next-steps" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-next-steps into .claude/skills/rigor-next-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-next-steps", 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-next-stepsType 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-next-steps -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rigortype/rigor rigor-next-steps --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-next-steps .agents/skills/rigor-next-steps && 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-next-steps" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-next-steps into .agents/skills/rigor-next-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-next-steps", 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-next-steps -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rigortype/rigor rigor-next-steps --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-next-steps .cursor/skills/rigor-next-steps && 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-next-steps" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-next-steps into .cursor/skills/rigor-next-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-next-steps", 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-next-steps--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-next-steps -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rigortype/rigor rigor-next-steps --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-next-steps .gemini/skills/rigor-next-steps && 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-next-steps" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-next-steps into .gemini/skills/rigor-next-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-next-steps", 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-next-stepsInstalls 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-next-steps -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-next-steps .github/skills/rigor-next-steps && 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-next-steps" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-next-steps into .github/skills/rigor-next-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-next-steps", 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-next-steps -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-next-steps --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-next-steps .opencode/skills/rigor-next-steps && 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-next-steps" agent skill from https://github.com/rigortype/rigor/tree/master/skills/rigor-next-steps into .opencode/skills/rigor-next-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rigor-next-steps", 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.
Facts
- Skill name
rigor-next-steps- GitHub stars
- 106
- Token cost
- ~1.3k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to rigor skill describe.
- Works in 5 steps: Resolve the rigor command → Install Rigor (only if Step 1 failed) → Set the project up if it has no Rigor… → …
- The user asks where to start
- SKILL.md covers Autonomous / non-interactive…, Step 1 — Resolve the rigor…, Step 2 — Install Rigor (only… and Step 3 — Set the project up if…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rigor Next Steps is an agent skill from rigortype/rigor. Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to rigor skill describe. Use when the user asks where to start or what to do next with Rigor; not instead of a task-specific skill the route selects.
Its SKILL.md is about 1.3k 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. The repository describes itself as: Inference-first static analysis for Ruby. The licence is MPL-2.0.
When your agent uses it
- The user asks where to start
- What to do next with Rigor
- Not instead of a task-specific skill the route selects
Example prompts
- “/rigor-next-steps”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
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):
rigor.typedduck.fail
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 Next Steps loads about 1.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 704 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.
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). 704 words, ~1,306 tokens.
Download SKILL.mdSave it as
.claude/skills/rigor-next-steps/SKILL.md (or your agent's skills folder).- name
- rigor-next-steps
- description
- Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to `rigor skill describe`. Use when the user asks where to start or what to do next with Rigor; not instead of a task-specific skill the route selects.
- license
- MPL-2.0
- metadata.version
- 0.1.0
- metadata.homepage
- https://github.com/rigortype/rigor
Rigor Next Steps
The single entry point for "what should we do next with Rigor on this
project?" This skill is deliberately thin: it only does the
bootstrap that must happen before rigor can speak for itself, then it
hands the decision to the installed rigor binary via
rigor skill describe. That keeps the advice current to the
installed version — the routing intelligence lives in the gem, not
frozen in this file (ADR-73).
Work top to bottom. Stop at the first step that is not yet satisfied, complete it, then continue.
Autonomous / non-interactive runs
When the user has delegated the journey up front ("set this project up and get it healthy; don't wait for me"), the skills below still contain ask-the-user points. Handle them like this:
- A choice the user already made in their instruction (e.g. the adoption mode) is settled — record it and proceed; do not re-ask.
- A low-risk, reversible, in-repo action a skill says to confirm
(installing an RBS collection, a
.gitignoreaddition) is covered by the standing delegation — do it, and note the self-answer in your report. - Committing, pushing, or publishing is never covered by a general delegation — leave the files uncommitted and list them for the user.
- A step only a human can complete or verify (watching a CI run execute, confirming live diagnostics inside an editor) is a handoff, not a stall: do the file-level part if it is safe, then report what remains for the user instead of waiting.
Step 1 — Resolve the rigor command
rigor --versionIf it prints a version (rigor 0.x.y), rigor is installed — go to
Step 3. If the command is not found, go to Step 2.
Step 2 — Install Rigor (only if Step 1 failed)
Rigor is a standalone tool, not a project dependency — do not add it
to the Gemfile. Fetch and follow the install guide, which is written
for an AI agent and picks the right channel (mise / asdf / gem / Docker)
for the environment:
Follow it until rigor --version succeeds, then continue to Step 3.
(This is the one step that cannot be driven by rigor skill describe —
there is no binary to ask yet. It is the only install knowledge this
skill carries, kept as a pointer rather than a copy so it does not go
stale.)
Step 3 — Set the project up if it has no Rigor config
Check the project root for .rigor.yml or .rigor.dist.yml. If
neither exists, the project has never been onboarded — set it up
first:
rigor skill --full rigor-project-init(rigor skill <name> prints the skill body alone; --full inlines its
references/ files too, so one call fetches the complete procedure.)
Follow that skill's body top to bottom (it detects the stack, picks
plugins, writes .rigor.dist.yml, and snapshots a baseline if needed),
then come back to Step 4.
Show full SKILL.md (248 more words)Show less
Step 4 — Ask rigor skill describe what to do next
Once rigor is installed and the project is configured, let the live
command pick the next move:
rigor skill describeIts output reports the project's current state (config / baseline /
sig/ / CI), names a recommended next skill with a one-line reason,
and lists every skill you can run next with its current description.
Step 5 — Route and act
Read the ## Recommended next step and ## For the agent sections of
the describe output, then:
Present the recommendation to the user proactively — e.g. "Rigor is set up but not wired into CI; I suggest the
rigor-ci-setupskill to lock in the regression guard. Shall I?" — rather than only asking an open question.If the user has a different goal, ask which skill they want from the listed catalog.
Then load the chosen skill and follow it:
sh rigor skill --full <chosen-skill>
Re-run rigor skill describe any time you want the next step again — it
always reflects the project's current state, so this skill stays useful
across the whole adoption journey, not just the first run.
Reading the docs offline
Once Rigor is installed (Step 1 succeeded), the full manual and handbook ship inside the gem — read any chapter without the network:
rigor docs # the offline doc index (what's available)
rigor docs <name> # a chapter, e.g. `rigor docs editor-integration`
rigor docs --list # name + absolute path for every bundled doc
rigor docs --list handbook # just the handbook chaptersPrefer this over fetching the same page from the web: it is the exact
copy that shipped with the installed rigor, so it always matches the
binary's behaviour. (The web copy at https://rigor.typedduck.fail/llms.txt
is for the contributor-facing corpus and for reading before install.)
© 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-next-steps of rigortype/rigor.
Open the folder on GitHubat commit 57a67cf
Compare with similar skills
Rigor Next Steps 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 Next Steps this skillrigortype/rigor | 106 | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from rigortype/rigor
All 36 skills in this repoRigor Regression Sweep
rigortype/rigor
Measure Rigor's baseline drift across the tagged history of a real OSS Ruby project.
Rigor Unused Adjudicate
rigortype/rigor
Adjudicate a rigor unused report safely before proposing dead-code removal.
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.
Rigor Doctor
rigortype/rigor
Validate that a project's Rigor configuration, plugins, paths, and baseline are actually healthy.
Rigor Plugin Author
rigortype/rigor
Author a new Rigor plugin, choosing plugins/ for production support or examples/ for a contract walkthrough.
Rigor Plugin Author
rigortype/rigor
Author a Rigor plugin in an adopting project or standalone rigor- gem for a DSL, framework, or metaprogramming pattern.
Related
Categories
Questions about Rigor Next Steps
What does Rigor Next Steps do?
Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to rigor skill describe. Rigor Next Steps is an agent skill from rigortype/rigor. Route a project to its next Rigor step, installing or onboarding Rigor when needed and then delegating to rigor skill describe.
When should I use Rigor Next Steps?
Rigor Next Steps fits situations like: the user asks where to start; what to do next with Rigor; not instead of a task-specific skill the route selects.
How do I install Rigor Next Steps in Claude Code?
Run `npx skills add rigortype/rigor --skill rigor-next-steps -a claude-code`. Or copy the skill folder (skills/rigor-next-steps in rigortype/rigor) into .claude/skills/rigor-next-steps in your project. Claude Code loads it when a task matches its description.
How do I install Rigor Next Steps in Codex?
Run `npx skills add rigortype/rigor --skill rigor-next-steps -a codex`. Or copy the skill folder (skills/rigor-next-steps in rigortype/rigor) into .agents/skills/rigor-next-steps in your project. Codex loads it when a task matches its description.
Can I use Rigor Next Steps 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-next-steps -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-next-steps, .gemini/skills/rigor-next-steps, .github/skills/rigor-next-steps and .opencode/skills/rigor-next-steps in your project.
What does Rigor Next Steps need to run?
SKILL.md names no scripts, command-line tools or credentials: Rigor Next Steps is instructions for the agent only. Our summary lists: Docker.
Does Rigor Next Steps access the network?
SKILL.md names 1 domain. As links in the text: rigor.typedduck.fail. This is read from the text; nothing was executed.
Is Rigor Next Steps 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 Next Steps use?
Rigor Next Steps 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 Next Steps use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Next Steps?
Skills that share tags, products or a category with Rigor Next Steps: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rigor Next Steps?
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.