New: 97,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 Editor Setup

by rigortype in rigortype/rigor

Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor.

MPL-2.0Auto-check passedDevelopment

Install Rigor Editor Setup

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

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

GitHub CLI
$ gh skill install rigortype/rigor rigor-editor-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-editor-setup .claude/skills/rigor-editor-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-editor-setup
GitHub stars
106
Token cost
~1.4k tokens
SKILL.md length
706 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
MPL-2.0

At a glance

Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor.

  • Works in 4 steps: confirm the analyzer works from the CLI… → identify the editor → apply the matching config → …
  • Wiring rigor lsp into VS Code
  • SKILL.md covers First: load the…, When to use, When NOT to use and The one stable fact, plus 2 more sections
  • Calls bundle

What it does

Rigor Editor Setup is an agent skill from rigortype/rigor. Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor. Use when wiring rigor lsp into VS Code, Neovim, Helix, Emacs, or another LSP client; not for CI or first-time project setup.

Its SKILL.md is about 1.4k 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 Visual Studio Code. The repository describes itself as: Inference-first static analysis for Ruby. The licence is MPL-2.0.

When your agent uses it

  • Wiring rigor lsp into VS Code
  • Another LSP client
  • First-time project setup

Example prompts

  • “/rigor-editor-setup”

Workflow steps

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

  1. confirm the analyzer works from the CLI first
  2. identify the editor
  3. apply the matching config
  4. verify

What it can do on your machine

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

    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 Editor Setup loads about 1.4k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 706 words of instructions outside code blocks.

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

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 c7b6b60, republished under its MPL-2.0 licence (© rigortype). 706 words, ~1,352 tokens.

Download SKILL.mdSave it as .claude/skills/rigor-editor-setup/SKILL.md (or your agent's skills folder).
name
rigor-editor-setup
description
Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor. Use when wiring `rigor lsp` into VS Code, Neovim, Helix, Emacs, or another LSP client; not for CI or first-time project setup.
license
MPL-2.0
metadata.version
0.1.0
metadata.homepage
https://github.com/rigortype/rigor

Rigor Editor Setup

rigor lsp is the in-process Language Server bundled with the rigortype gem. It speaks LSP over stdio and turns Rigor's analyzer into a live editor experience: diagnostics as you type, hover-to-type, an outline view, and type-aware completion. This skill wires it into the developer's editor.

The authoritative, per-editor configuration lives in the manual. With Rigor installed, read it offline with no network round-trip:

sh
rigor docs editor-integration

(Web fallback, only before Rigor is installed: Rigor LSP — Editor Integration.) This skill is the workflow around it (identify the editor → apply the manual's snippet → verify), so it does not duplicate (and cannot stale-out) the config details.

First: load the version-current copy

The config details already come live from rigor docs; this section keeps the workflow itself current too. Prefer the copy of this skill that ships with the installed Rigor over any vendored or frozen copy of this file:

sh
rigor skill --full rigor-editor-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

  • A developer wants Rigor feedback live in their editor, not just from rigor check on the command line.
  • A project commits a shared editor config (e.g. .vscode/) and you want to add Rigor's LSP to it so the whole team gets it.

When NOT to use

  • Wiring Rigor into CI — that is rigor-ci-setup.
  • The project has no Rigor config yet — run rigor-project-init first (the LSP uses the same .rigor.yml discovery as rigor check).

The one stable fact

Every editor snippet simply launches rigor lsp (stdio) and needs rigor on the editor's PATH — the same executable rigor check uses. For GUI editors that do not inherit your shell, the mise shim path is the most reliable channel (see rigor docs install, or Installing Rigor on the web). Do not add rigortype to the project's Gemfile — it is a tool, not a library.

Procedure

Phase 1 — confirm the analyzer works from the CLI first
sh
rigor check <a-file-or-dir>

The LSP shares rigor check's config discovery and analysis. If check works from the project root, the LSP will too; if it fails, fix that first — the editor would only surface the same failure.

Show full SKILL.md (336 more words)Show less
Phase 2 — identify the editor

Ask the developer which editor they use, or detect it (a committed .vscode/, a Neovim init.lua, ~/.config/helix/, an Emacs config). The manual chapter covers:

  • Neovim (nvim-lspconfig)
  • VS Code (generic LSP-client wrapper / minimal extension)
  • Helix (languages.toml)
  • Emacs (Eglot and lsp-mode)

The editors are not equally cheap to wire. Neovim / Helix / Emacs are plain config snippets. VS Code has no first-party Rigor extension yet — its path means authoring and side-loading a minimal extension (a LanguageClient wrapper), which is a development task, not a settings.json edit. Say so before starting: the developer may prefer to wait for a first-class extension, and an autonomous agent should treat the VS Code path as a user handoff (report the manual's recipe; do not scaffold an unrequested extension). Phase 4's verification (live diagnostics, hover) also requires a human in front of the editor — an agent stops there and reports, for every editor.

Phase 3 — apply the matching config

Open the manual's Editor wiring section and apply the snippet for the developer's editor verbatim:

sh
rigor docs editor-integration

(or, pre-install, the web copy: https://github.com/rigortype/rigor/blob/master/docs/manual/09-editor-integration.md)

All snippets invoke rigor lsp directly. (Only if the project still uses a legacy bundler-local install do you swap in bundle exec rigor lsp — the manual notes this per editor.)

If the project commits a shared editor config (e.g. .vscode/), add the Rigor LSP wiring there and commit it, so every contributor gets the same setup rather than configuring it individually.

Phase 4 — verify

Open a Ruby file inside a Rigor-configured project and confirm:

  • diagnostics appear (on save / as you type), and
  • hover over a method or local shows its inferred type.

If the server starts but nothing appears, work the manual's Troubleshooting section (most often: rigor not on the editor's PATH, or no .rigor.yml at the project root). Capture the LSP log with rigor lsp --log=/tmp/rigor-lsp.log when filing an issue.

Next step

Re-run rigor skill describe for the next move — with live feedback in the editor, raising protection (rigor-protection-uplift) or reducing a baseline (rigor-baseline-reduce) is a tighter loop.

© 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-editor-setup of rigortype/rigor.

Open the folder on GitHubat commit c7b6b60

Compare with similar skills

Rigor Editor 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 Editor Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rigor Editor Setup this skillrigortype/rigor106—~1.4kAutomated safety check: PassMPL-2.0
Workthreadsspecstoryai/getspecstory1.3k—~1.3kAutomated safety check: NotesApache-2.0
Excalidraw Diagram Studiotech-leads-club/agent-skills7k—~3.6kAutomated safety check: PassCC-BY-4.0
Git Worktree Managermicrosoft/WindowsAppSDK4.7k—~2kAutomated safety check: PassMIT
Roo Conflict Resolutionzgsm-ai/costrict4.4k—~2.3kAutomated safety check: PassApache-2.0
Interactive Extension TestingPowerShell/vscode-powershell1.9k—~824Automated safety check: PassMIT

Similar skills

  • Workthreads

    specstoryai/getspecstory

    SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more).

    1.3k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Excalidraw Diagram Studio

    tech-leads-club/agent-skills

    Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.

    7k GitHub stars~3.6k tokensUpdated 17 days ago
    DevelopmentAuto-check passed

  • Git Worktree Manager

    microsoft/WindowsAppSDK

    Official

    Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.

    4.7k GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Roo Conflict Resolution

    zgsm-ai/costrict

    Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.

    4.4k GitHub stars~2.3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Interactive Extension Testing

    PowerShell/vscode-powershell

    Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.

    1.9k GitHub stars~824 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release

    PowerShell/vscode-powershell

    Guide for preparing a release of the PowerShell VS Code extension.

    1.9k GitHub stars~1.1k tokensUpdated 1 mo 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 5 days ago
    Auto-check passed

  • Rigor Unused Adjudicate

    rigortype/rigor

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

    106 GitHub stars~1.1k tokensUpdated 5 days ago
    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 5 days ago
    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 5 days ago
    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 5 days ago
    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 5 days ago
    Auto-check passed

Works with

Categories

Questions about Rigor Editor Setup

What does Rigor Editor Setup do?

Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor. Rigor Editor Setup is an agent skill from rigortype/rigor. Set up Rigor's bundled language server for live diagnostics, hover, outline, and completion in a developer's editor.

When should I use Rigor Editor Setup?

Rigor Editor Setup fits situations like: wiring rigor lsp into VS Code; another LSP client; first-time project setup.

How do I install Rigor Editor Setup in Claude Code?

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

How do I install Rigor Editor Setup in Codex?

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

Can I use Rigor Editor 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-editor-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-editor-setup, .gemini/skills/rigor-editor-setup, .github/skills/rigor-editor-setup and .opencode/skills/rigor-editor-setup in your project.

What does Rigor Editor Setup need to run?

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

Does Rigor Editor Setup 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 Editor 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 Editor Setup use?

Rigor Editor 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 Editor Setup use?

About 1.4k tokens (SKILL.md is roughly 5.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 Editor Setup?

Skills that share tags, products or a category with Rigor Editor Setup: Workthreads (specstoryai/getspecstory, 1.3k stars), Excalidraw Diagram Studio (tech-leads-club/agent-skills, 7k stars), Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars) and Roo Conflict Resolution (zgsm-ai/costrict, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rigor Editor 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 2, 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.