Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Guidelines and best practices for creating, extending, and refactoring linters in the r-lib/lintr package.
Install Developing Linters
$ npx skills add r-lib/lintr --skill developing-linters -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install r-lib/lintr developing-linters --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/r-lib/lintr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/developing-linters .claude/skills/developing-linters && 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 "developing-linters" agent skill from https://github.com/r-lib/lintr/tree/main/.agents/skills/developing-linters into .claude/skills/developing-linters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-linters", 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/r-lib/lintr/tree/main/.agents/skills/developing-lintersType 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 r-lib/lintr --skill developing-linters -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install r-lib/lintr developing-linters --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r-lib/lintr.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/developing-linters .agents/skills/developing-linters && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developing-linters" agent skill from https://github.com/r-lib/lintr/tree/main/.agents/skills/developing-linters into .agents/skills/developing-linters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-linters", 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 r-lib/lintr --skill developing-linters -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install r-lib/lintr developing-linters --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r-lib/lintr.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/developing-linters .cursor/skills/developing-linters && 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 "developing-linters" agent skill from https://github.com/r-lib/lintr/tree/main/.agents/skills/developing-linters into .cursor/skills/developing-linters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-linters", 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/r-lib/lintr.git --path .agents/skills/developing-linters--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 r-lib/lintr --skill developing-linters -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install r-lib/lintr developing-linters --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r-lib/lintr.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/developing-linters .gemini/skills/developing-linters && 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 "developing-linters" agent skill from https://github.com/r-lib/lintr/tree/main/.agents/skills/developing-linters into .gemini/skills/developing-linters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-linters", 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 r-lib/lintr developing-lintersInstalls 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 r-lib/lintr --skill developing-linters -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/r-lib/lintr.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/developing-linters .github/skills/developing-linters && 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 "developing-linters" agent skill from https://github.com/r-lib/lintr/tree/main/.agents/skills/developing-linters into .github/skills/developing-linters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-linters", 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 r-lib/lintr --skill developing-linters -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install r-lib/lintr developing-linters --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/r-lib/lintr.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/developing-linters .opencode/skills/developing-linters && 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 "developing-linters" agent skill from https://github.com/r-lib/lintr/tree/main/.agents/skills/developing-linters into .opencode/skills/developing-linters/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developing-linters", 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
developing-linters- GitHub stars
- 1.3k
- Token cost
- ~5.1k tokens
- SKILL.md length
- 2,444 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guidelines and best practices for creating, extending, and refactoring linters in the r-lib/lintr package.
- Works in 11 steps: Minimalist API Surface & Defaults ("On… → Helper Functions, Readability, & Safe… → Minimal Diffs & Logical Execution Order → …
- Modifying linter functions
- SKILL.md covers 1. Minimalist API Surface &…, 2. Helper Functions,…, 3. Minimal Diffs & Logical… and 4. Self-Linting, Repository…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Developing Linters is an agent skill from r-lib/lintr. Guidelines and best practices for creating, extending, and refactoring linters in the r-lib/lintr package. Use this skill whenever implementing or modifying linter functions, XPath queries, and linter helpers.
Its SKILL.md is about 5.1k 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, covering Linting and formatting. The repository describes itself as: Static Code Analysis for R.
When your agent uses it
- Modifying linter functions
- Tasks that involve Linting and formatting
Example prompts
- “Use the developing-linters skill to guideline and best practices for creating, extending, and refactoring linters in the r-lib/lintr package”
- “/developing-linters”
Workflow steps
11 steps, taken from the step headings in SKILL.md.
- Minimalist API Surface & Defaults ("On by Default")
- Helper Functions, Readability, & Safe Fallbacks
- Minimal Diffs & Logical Execution Order
- Self-Linting, Repository Health, & NEWS.md
- Respecting Contract Boundaries & Avoiding Unexported Internals (:::)
- Simple & Idiomatic AST and Condition Checks
- Data Engineering, Centralized State, & Readability First
- Idiomatic R Vectorization over Loops
- Handling Sequences, Ranges, Directionality, & Boundary Conditions
- Robust Handling of Literate R Formats & Readable Transitions
- Direct Documentation Workflow & roxygen2 Example Style
What it can do on your machine
Read from SKILL.md and the folder at commit 42f73ec. 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 r).
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
Developing Linters loads about 5.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 2,444 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,444 words (~5,127 tokens).
“When implementing, extending, or refactoring linters in lintr, adhere to the following architectural, design, and production-readiness guidelines established by project maintainers:”
- name
- developing-linters
Files
Just SKILL.md in .agents/skills/developing-linters of r-lib/lintr.
Open the folder on GitHubat commit 42f73ec
Compare with similar skills
Developing Linters 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 |
|---|---|---|---|---|---|---|
| Developing Linters this skillr-lib/lintr | 1.3k | — | ~5.1k | Automated safety check: Pass | Custom licence | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Babysit PR To Pass CIsgl-project/sglang | 37k | 2 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Go Pedantrychromedp/chromedp | 13k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
WooCommerce Markdown Guidelines
woocommerce/woocommerce
Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks.
More from r-lib/lintr
Literate R Formats
r-lib/lintr
Guidelines and architecture for handling literate R documents (.Rmd, .qmd, .Rnw, .Rhtml) and source extraction in the r-lib/lintr package.
Testing Linters
r-lib/lintr
Guidelines and conventions for writing unit tests for linters in the r-lib/lintr package using testthat.
Xpath Style
r-lib/lintr
Guidelines and conventions for writing, composing, and formatting XPath expressions when building or refactoring linters.
Related
Categories
Questions about Developing Linters
What does Developing Linters do?
Guidelines and best practices for creating, extending, and refactoring linters in the r-lib/lintr package. Developing Linters is an agent skill from r-lib/lintr. Guidelines and best practices for creating, extending, and refactoring linters in the r-lib/lintr package.
When should I use Developing Linters?
Developing Linters fits situations like: modifying linter functions; tasks that involve Linting and formatting.
How do I install Developing Linters in Claude Code?
Run `npx skills add r-lib/lintr --skill developing-linters -a claude-code`. Or copy the skill folder (.agents/skills/developing-linters in r-lib/lintr) into .claude/skills/developing-linters in your project. Claude Code loads it when a task matches its description.
How do I install Developing Linters in Codex?
Run `npx skills add r-lib/lintr --skill developing-linters -a codex`. Or copy the skill folder (.agents/skills/developing-linters in r-lib/lintr) into .agents/skills/developing-linters in your project. Codex loads it when a task matches its description.
Can I use Developing Linters 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 r-lib/lintr --skill developing-linters -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developing-linters, .gemini/skills/developing-linters, .github/skills/developing-linters and .opencode/skills/developing-linters in your project.
What does Developing Linters need to run?
SKILL.md names no scripts, command-line tools or credentials: Developing Linters is instructions for the agent only.
Does Developing Linters 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 Developing Linters 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 Developing Linters use?
Developing Linters has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Developing Linters use?
About 5.1k tokens (SKILL.md is roughly 21k 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 Developing Linters?
Skills that share tags, products or a category with Developing Linters: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars), Rust Best Practices (farm-fe/farm, 5.6k stars) and Go Pedantry (chromedp/chromedp, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developing Linters?
r-lib (a GitHub organization) maintains it in r-lib/lintr, which has 1,296 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: r-lib/lintr on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.