Installation

via skills CLI (recommended)
Manual

From the root of your project, install the skill with npx skills:
Terminal window
```
npx skills add Grisselbav/dbLinter
```
If you don’t pass -a, this asks you interactively which agent(s) to install the skill for — see Which agent(s) should I select? below before answering.
Make sure the dblinter CLI itself is installed and authenticated — see the CLI Overview. The skill assumes dblinter is already on your PATH.

Copy or symlink the skills/dblinter directory from the dbLinter GitHub repository into .agents/skills/dblinter/ at the root of your project (or ~/.agents/skills/dblinter/ to make it available in every project). This shared, “universal” location is read directly by most Agent-Skills-compatible agents, including OpenAI Codex and GitHub Copilot — see Which agent(s) should I select?.
Claude Code is the exception: it only reads its own .claude/skills/ directory, not .agents/skills/. If you use Claude Code, also copy or symlink skills/dblinter into .claude/skills/dblinter/ (or ~/.claude/skills/dblinter/ for every project).
Make sure the dblinter CLI itself is installed and authenticated — see the CLI Overview.

Which agent(s) should I select?

Running npx skills add Grisselbav/dbLinter without -a prompts you to choose which agent(s) to install for. That prompt lists every agent the tool supports (dozens of them) — it does not narrow the list down to only the agents already set up in your project, so don’t be surprised to see a long list even if you only use one or two of them day to day. If the tool detects it is itself being run from inside a supported agent (for example, you asked Claude Code to run the install command for you), it may skip the prompt entirely and install non-interactively instead — worth double-checking the result if that happens and it’s not what you expected.

Pick explicitly to skip the prompt:

# install for Claude Code and Codex only
npx skills add Grisselbav/dbLinter -a claude-code -a codex

# install for every supported agent
npx skills add Grisselbav/dbLinter -a '*'

Not every agent needs its own dedicated directory. The tool creates one real copy of the skill at ./.agents/skills/dblinter/ — a shared location that most agents, including OpenAI Codex and GitHub Copilot, read directly, with no per-agent copy needed. Claude Code is the exception: it only reads its own .claude/skills/, so the tool additionally creates a symlink from .claude/skills/dblinter/ back to the shared copy for it (and, similarly, for the handful of other agents that also require their own dedicated directory). Either way, a single npx skills update keeps everything — the shared copy and every symlink — in sync; you don’t need to think about which agents got a real copy versus a symlink.

See Compatibility for the per-agent directory details.

Update the skill to the latest published version:
Terminal window
```
npx skills update dblinter -p
```

Re-copy the skills/dblinter directory from the dbLinter GitHub repository, overwriting the version in your agent’s skills directory.

Verifying the installation

Ask your agent what skills are available to it — for example, in Claude Code run /skills — and confirm dblinter is listed. Check your agent’s own docs (linked in Compatibility) for the equivalent command if you’re not using Claude Code. Then give it a prompt that matches an everyday task, for example:

Check my SQL files with dblinter and summarize the issues.

A working installation picks this up without you having to name the skill or the CLI flags yourself. See Usage for more examples.