Coding agent skills for Inspect AI and its ecosystem (inspect_ai, inspect_evals, inspect_flow, inspect_scout, inspect_viz, inspect_swe, inspect_harbor, sandboxes).
/plugin marketplace add meridianlabs-ai/inspect-skills
/plugin install inspect-skills@meridian
Third-party marketplaces are manual-update by default. To get our changes automatically (every push to main lands in your next Claude Code session), toggle auto-update on for the meridian marketplace from /plugin > Marketplaces, or add to your ~/.claude/settings.json:
{
"extraKnownMarketplaces": {
"meridian": { "autoUpdate": true }
}
}To update manually instead: /plugin marketplace update meridian then /reload-plugins.
codex plugin marketplace add meridianlabs-ai/inspect-skills
codex plugin add inspect-skills@meridianTo update: codex plugin marketplace upgrade meridian (Codex has no auto-update equivalent; updates are manual).
npx skills add meridianlabs-ai/inspect-skills --agent <agent> -g -y-y installs every skill non-interactively; add --skill <skill-name> to install just one. Updates: npx skills update. Run npx skills add --help for the full list of supported agents.
| Skill | When it fires |
|---|---|
map-inspect-packages |
Starting work in the Inspect AI ecosystem. Picks the right package for a given task and points at its docs. |
reading-logs |
Reading, inspecting, or processing Inspect AI eval log files (.eval or .json). Covers the inspect_ai.log API and memory-safe patterns. |
babysitting-evals |
Monitoring and diagnosing running Inspect AI evals via inspect ctl (the read-only control-channel CLI). Covers stall diagnosis, error triage, launch-and-watch workflows, and graceful stops. |
PR titles must follow Conventional Commits (enforced via the pr-title-lint workflow). The repo squashes PRs on merge, so the PR title becomes the main-branch commit.
Common prefixes and what they do:
| Prefix | Effect on releases | Visible in CHANGELOG? |
|---|---|---|
feat: |
minor version bump on next Codex release | yes (Features) |
fix: |
patch version bump on next Codex release | yes (Bug Fixes) |
perf: |
patch version bump on next Codex release | yes (Performance Improvements) |
revert: |
patch version bump on next Codex release | yes (Reverts) |
docs: |
none on its own; piggybacks the next feat: / fix: |
yes (Documentation) |
refactor: / chore: / ci: / test: |
none | no |
Important: SKILL.md content changes should use fix:, not docs:. The skills ARE the user-facing artifact, so corrections and refinements are fixes to it. docs: is reserved for repo-level documentation that isn't shipped to users.
Claude Code and Codex have different release flows because their plugin update models differ:
-
Claude Code uses the commit SHA as the implicit plugin version. If a user has enabled auto-update for the
meridianmarketplace, every push tomainreaches them on their next session. By default, third-party marketplaces are manual-update, so users either toggle auto-update on (see Install) or run/plugin marketplace update meridian+/reload-pluginsto pull changes. -
Codex caches each plugin by the
versionfield in.codex-plugin/plugin.json. New commits tomaindo not reach Codex users viacodex plugin marketplace upgrade meridianuntil the version bumps.
We use release-please primarily to keep Codex users on the latest content. On every push to main, release-please opens (or updates) a "Release PR" that proposes a version bump and a CHANGELOG entry based on the Conventional Commits in the new commits. Merging the Release PR bumps the version in plugins/inspect-skills/.codex-plugin/plugin.json, after which Codex users can run codex plugin marketplace upgrade meridian to pull the new content.