New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Rigor Unused Adjudicate

by rigortype in rigortype/rigor

Adjudicate a rigor unused report safely before proposing dead-code removal.

MPL-2.0Auto-check passedDevelopment

Install Rigor Unused Adjudicate

skills CLI
$ npx skills add rigortype/rigor --skill rigor-unused-adjudicate -a claude-code

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

GitHub CLI
$ gh skill install rigortype/rigor rigor-unused-adjudicate --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-unused-adjudicate .claude/skills/rigor-unused-adjudicate && 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-unused-adjudicate
GitHub stars
106
Token cost
~1.1k tokens
SKILL.md length
606 words
Files
3 (incl. scripts)
Skills in repo
36
Repo updated
First seen
Licence
MPL-2.0

At a glance

Adjudicate a rigor unused report safely before proposing dead-code removal.

  • Reviewing Rigors unused classes/modules/constants
  • SKILL.md covers Establish the ground first, Then hand off to the chapter and Two habits that keep the…
  • Runs Shell scripts from its folder
  • A cleanup is based on that report

What it does

Rigor Unused Adjudicate is an agent skill from rigortype/rigor. Adjudicate a rigor unused report safely before proposing dead-code removal. Use when interpreting or reviewing Rigor's unused classes/modules/constants, or when a cleanup is based on that report; not for a specific deletion already known to be safe or for ordinary rigor check diagnostics.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `evals/evals.json` and `scripts/evidence.sh`).

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

  • Reviewing Rigors unused classes/modules/constants
  • A cleanup is based on that report
  • Not for a specific deletion already known to be safe
  • For ordinary rigor check diagnostics

Example prompts

  • “/rigor-unused-adjudicate”

Requirements

  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit 85200dd. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

    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 Unused Adjudicate loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 606 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from rigortype/rigor at commit 85200dd, republished under its MPL-2.0 licence (© rigortype). 606 words, ~1,094 tokens.

Download SKILL.mdSave it as .claude/skills/rigor-unused-adjudicate/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
rigor-unused-adjudicate
description
Adjudicate a `rigor unused` report safely before proposing dead-code removal. Use when interpreting or reviewing Rigor's unused classes/modules/constants, or when a cleanup is based on that report; not for a specific deletion already known to be safe or for ordinary `rigor check` diagnostics.
license
MPL-2.0
metadata.version
0.2.0
metadata.homepage
https://github.com/rigortype/rigor

Adjudicating rigor unused

rigor unused answers which project classes and modules does no reachable code name? — not what can I delete. Closing that gap is the work, and the manual chapter has the method:

sh
rigor docs 18-removing-dead-code

Read it before adjudicating anything. It carries the false-positive shapes with their measured frequencies, the pre-deletion checklist, and how to report the result. This skill exists for the part the chapter cannot do for you: work out what the report can and cannot see on this particular project, before you trust a single row.

Do that first, because every check below changes how the output should be read — and skipping one is how a live class ends up on a deletion list.

Establish the ground first

Run the report and answer these against the project in front of you.

Are framework roots actually supplied? When a plugin contributes roots, the summary's roots: line grows a parenthetical: roots: N (M from plugins, K matched no declaration). The parenthetical is omitted entirely when no plugin contributed — so on a framework application, a bare roots: N with no (… from plugins …) note means nothing is naming your controllers, jobs or policies, and most of the report is noise. Stop and fix the plugin configuration — rigor docs 07-plugins — rather than adjudicating hundreds of rows.

Does the project ship signatures? If signature_paths: is configured, also run with it emptied and compare:

sh
rigor unused                            # normal
rigor unused --config /tmp/no-sig.yml   # a copy of your config with signature_paths: []

Adjudicate the union. On one application the signature-free run surfaced three genuinely dead classes that the default run never showed. Rows that appear only without signatures are still worth checking — signatures reference classes, and a reference the report counts is not always one a human would.

What do paths: actually cover? Only Ruby under those paths is analysed. Views are the common gap: a helper called from app/views/**/*.erb has no Ruby caller at all, and will land in the report looking unused. Before believing any helper or presenter row, grep the view tree for it.

Is the git history usable? The chapter's checklist uses "when did this file last change" as evidence. In a shallow clone, or one whose history is all dependency bumps, that signal is empty — notice it and say so rather than reporting a bot commit as the file's age.

Show full SKILL.md (234 more words)Show less

Then hand off to the chapter

With that established, follow the chapter. Two things worth holding onto as you go, because they are what the report's own design is built around:

Framework conventions and configuration reach code without naming it. The chapter lists the shapes; the ones that recur hardest are a class named as a string in config/*.yml (a recurring-job schedule, a queue definition), a convention that derives one name from another (FooHelper from FooController, a decorator from a model, a join model from has_many :speakers_talks), and a registration DSL called inside the class body. None of these appear as a constant anywhere.

Wrong rows cascade. A class used only by a wrongly-classified class follows it into the report. When a row turns out to be live, re-check what it references before treating those rows as independent findings.

Two habits that keep the answer honest

A search that finds nothing proves nothing until it has found something. Before concluding a name appears nowhere, run the same search against a name you know is used. Silence from a broken command and silence from dead code look identical.

Over-claiming hides dead code; under-claiming does not. If you cannot settle a row, leave it in the report and say you could not settle it. A row left on the list is visible to a human; a row you dismissed on a hunch is invisible to everyone.

© 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

SKILL.md and 2 other files (scripts) in skills/rigor-unused-adjudicate of rigortype/rigor.

  • SKILL.md
  • evals/evals.json
  • scripts/evidence.sh

Open the folder on GitHubat commit 85200dd

Compare with similar skills

Rigor Unused Adjudicate 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 Unused Adjudicate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rigor Unused Adjudicate this skillrigortype/rigor106—~1.1kAutomated safety check: PassMPL-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

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

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

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

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

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

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

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

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

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

    32k GitHub starsUsed in 4 repos~3.3k tokens
    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

  • 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

  • Rigor Plugin Review

    rigortype/rigor

    Audit an existing Rigor plugin against the current authoring contract and produce a prioritized upgrade path.

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

Categories

Questions about Rigor Unused Adjudicate

What does Rigor Unused Adjudicate do?

Adjudicate a rigor unused report safely before proposing dead-code removal. Rigor Unused Adjudicate is an agent skill from rigortype/rigor. Adjudicate a rigor unused report safely before proposing dead-code removal.

When should I use Rigor Unused Adjudicate?

Rigor Unused Adjudicate fits situations like: reviewing Rigors unused classes/modules/constants; A cleanup is based on that report; not for a specific deletion already known to be safe; for ordinary rigor check diagnostics.

How do I install Rigor Unused Adjudicate in Claude Code?

Run `npx skills add rigortype/rigor --skill rigor-unused-adjudicate -a claude-code`. Or copy the skill folder (skills/rigor-unused-adjudicate in rigortype/rigor) into .claude/skills/rigor-unused-adjudicate in your project. Claude Code loads it when a task matches its description.

How do I install Rigor Unused Adjudicate in Codex?

Run `npx skills add rigortype/rigor --skill rigor-unused-adjudicate -a codex`. Or copy the skill folder (skills/rigor-unused-adjudicate in rigortype/rigor) into .agents/skills/rigor-unused-adjudicate in your project. Codex loads it when a task matches its description.

Can I use Rigor Unused Adjudicate 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-unused-adjudicate -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-unused-adjudicate, .gemini/skills/rigor-unused-adjudicate, .github/skills/rigor-unused-adjudicate and .opencode/skills/rigor-unused-adjudicate in your project.

What does Rigor Unused Adjudicate need to run?

Going by SKILL.md and its folder, Rigor Unused Adjudicate needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Rigor Unused Adjudicate access the network?

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.

Is Rigor Unused Adjudicate 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Rigor Unused Adjudicate use?

Rigor Unused Adjudicate 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 Unused Adjudicate use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Unused Adjudicate?

Skills that share tags, products or a category with Rigor Unused Adjudicate: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k 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 Unused Adjudicate?

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 11, 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.