Eslint Migrate Options
biomejs/biome
A skill your agent uses when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures.
Run static analysis on Common Lisp projects with the Mallet command-line linter.
Install Lint Common Lisp
$ npx skills add ultralisp/ultralisp --skill lint-common-lisp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ultralisp/ultralisp lint-common-lisp --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/ultralisp/ultralisp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/lint-common-lisp .claude/skills/lint-common-lisp && 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 "lint-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lisp into .claude/skills/lint-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-common-lisp", 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/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lispType 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 ultralisp/ultralisp --skill lint-common-lisp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ultralisp/ultralisp lint-common-lisp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/lint-common-lisp .agents/skills/lint-common-lisp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lint-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lisp into .agents/skills/lint-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-common-lisp", 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 ultralisp/ultralisp --skill lint-common-lisp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ultralisp/ultralisp lint-common-lisp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/lint-common-lisp .cursor/skills/lint-common-lisp && 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 "lint-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lisp into .cursor/skills/lint-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-common-lisp", 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/ultralisp/ultralisp.git --path .agents/skills/lint-common-lisp--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 ultralisp/ultralisp --skill lint-common-lisp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ultralisp/ultralisp lint-common-lisp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/lint-common-lisp .gemini/skills/lint-common-lisp && 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 "lint-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lisp into .gemini/skills/lint-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-common-lisp", 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 ultralisp/ultralisp lint-common-lispInstalls 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 ultralisp/ultralisp --skill lint-common-lisp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/lint-common-lisp .github/skills/lint-common-lisp && 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 "lint-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lisp into .github/skills/lint-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-common-lisp", 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 ultralisp/ultralisp --skill lint-common-lisp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ultralisp/ultralisp lint-common-lisp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ultralisp/ultralisp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/lint-common-lisp .opencode/skills/lint-common-lisp && 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 "lint-common-lisp" agent skill from https://github.com/ultralisp/ultralisp/tree/master/.agents/skills/lint-common-lisp into .opencode/skills/lint-common-lisp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-common-lisp", 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
lint-common-lisp- GitHub stars
- 258
- Token cost
- ~771 tokens
- SKILL.md length
- 355 words
- Files
- 2
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- None found
At a glance
Run static analysis on Common Lisp projects with the Mallet command-line linter.
- Works in 6 steps: Inspect repository instructions and the… → Determine the scope before linting.… → Record the baseline by file, rule, and… → …
- Fixing lint findings in .lisp
- SKILL.md covers Workflow, Safety checks and Completion criteria
- Calls git and rg
What it does
Lint Common Lisp is an agent skill from ultralisp/ultralisp. Run static analysis on Common Lisp projects with the Mallet command-line linter. Use when reviewing, diagnosing, or fixing lint findings in .lisp or .asd files; when establishing a lint baseline; or when verifying that Common Lisp changes leave no actionable Mallet findings. Supports repositories using Qlot, ASDF, and Rove.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Linting and formatting and Static analysis and SAST. The repository describes itself as: The software behind a Ultralisp.org Common Lisp repository.
When your agent uses it
- Fixing lint findings in .lisp
- Establishing a lint baseline
- Verifying that Common Lisp changes leave no actionable Mallet findings
Example prompts
- “/lint-common-lisp”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Inspect repository instructions and the working tree. Preserve unrelated
- Determine the scope before linting. Prefer tracked project files
- Record the baseline by file, rule, and severity. Read the surrounding code
- Fix one logical issue at a time with the smallest semantics-preserving edit.
- After each changed file, run the repository's relevant test command before
- Re-run the same project-wide Mallet command. Resolve every actionable
What it can do on your machine
Read from SKILL.md and the folder at commit 3439788. 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:
gitrg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Lint Common Lisp loads about 771 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 355 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 355 words (~771 tokens).
“Use Mallet to find likely mistakes, not to impose broad formatting changes.”
- name
- lint-common-lisp
Files
SKILL.md and 1 other file in .agents/skills/lint-common-lisp of ultralisp/ultralisp.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 3439788
Compare with similar skills
Lint Common Lisp 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 |
|---|---|---|---|---|---|---|
| Lint Common Lisp this skillultralisp/ultralisp | 258 | — | ~771 | Automated safety check: Pass | None | |
| Eslint Migrate Optionsbiomejs/biome | 26k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Openqodexopenqodex/openqodex | 470 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Golang Continuous Integrationsamber/cc-skills-golang | 3.4k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Golang Continuous Integrationcontext-labs/whip | 1.1k | — | ~3.5k | Automated safety check: Pass | MIT | |
| FixBUZZARDGTA/Session-Sniffer | 104 | — | ~2.7k | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
Openqodex
openqodex/openqodex
Code review for the current change, before it is pushed. An agent skill from openqodex/openqodex.
Golang Continuous Integration
samber/cc-skills-golang
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release…
Golang Continuous Integration
context-labs/whip
CI/CD with GitHub Actions for Golang — testing, linting, SAST, security scanning, coverage, Dependabot, Renovate, GoReleaser, release pipelines.
Fix
BUZZARDGTA/Session-Sniffer
Diagnose and fix Session Sniffer bugs, errors, tracebacks, logs, lint failures, static-analysis findings, test failures, and IDE-reported problems.
Grails Violation Fixer
apache/grails-core
Guide to running, reading and fixing code style and analysis violations in grails-core with CodeNarc, Checkstyle, PMD, SpotBugs, Spotless and JaCoCo through Gradle.
More from ultralisp/ultralisp
All 14 skills in this repoDispatching Parallel Agents
ultralisp/ultralisp
A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Deep Research
ultralisp/ultralisp
A skill your agent uses when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation.
Atomic Spec Orchestrator
ultralisp/ultralisp
AI-агент — эксперт-оркестратор разработки по методологии Atomic Spec.
Avoiding Common Lisp Pitfalls
ultralisp/ultralisp
A skill your agent uses when writing new or large Common Lisp code where subtle library or language gotchas are likely — event-emitter argument order, parenthesis imbalance in a big file, or a…
Clearing Asdf Fasl Cache
ultralisp/ultralisp
A skill your agent uses when ASDF fasl cache is stale and build tools (build-docs, qlot exec sbcl, etc.) do not pick up source changes — typically after modifying docstrings, adding defgeneric…
Related
Categories
Questions about Lint Common Lisp
What does Lint Common Lisp do?
Run static analysis on Common Lisp projects with the Mallet command-line linter. Lint Common Lisp is an agent skill from ultralisp/ultralisp. Run static analysis on Common Lisp projects with the Mallet command-line linter.
When should I use Lint Common Lisp?
Lint Common Lisp fits situations like: fixing lint findings in .lisp; establishing a lint baseline; verifying that Common Lisp changes leave no actionable Mallet findings.
How do I install Lint Common Lisp in Claude Code?
Run `npx skills add ultralisp/ultralisp --skill lint-common-lisp -a claude-code`. Or copy the skill folder (.agents/skills/lint-common-lisp in ultralisp/ultralisp) into .claude/skills/lint-common-lisp in your project. Claude Code loads it when a task matches its description.
How do I install Lint Common Lisp in Codex?
Run `npx skills add ultralisp/ultralisp --skill lint-common-lisp -a codex`. Or copy the skill folder (.agents/skills/lint-common-lisp in ultralisp/ultralisp) into .agents/skills/lint-common-lisp in your project. Codex loads it when a task matches its description.
Can I use Lint Common Lisp 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 ultralisp/ultralisp --skill lint-common-lisp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lint-common-lisp, .gemini/skills/lint-common-lisp, .github/skills/lint-common-lisp and .opencode/skills/lint-common-lisp in your project.
What does Lint Common Lisp need to run?
Going by SKILL.md and its folder, Lint Common Lisp needs the command-line tools its instructions call (git and rg).
Does Lint Common Lisp access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Lint Common Lisp 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 Lint Common Lisp use?
No licence was found for Lint Common Lisp or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Lint Common Lisp use?
About 771 tokens (SKILL.md is roughly 3.1k 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 Lint Common Lisp?
Skills that share tags, products or a category with Lint Common Lisp: Eslint Migrate Options (biomejs/biome, 26k stars), Openqodex (openqodex/openqodex, 470 stars), Golang Continuous Integration (samber/cc-skills-golang, 3.4k stars) and Golang Continuous Integration (context-labs/whip, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lint Common Lisp?
ultralisp (a GitHub organization) maintains it in ultralisp/ultralisp, which has 258 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 13, 2026.
Source: ultralisp/ultralisp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.