A library of skills for Claude Code that guides building and auditing code to current engineering standards, covering APIs, architecture, async and concurrency, C and C++, and CLI design.
Claude Code
> /plugin marketplace add martinholovsky/SOTA-skills> /plugin install sota-skills@sota-skills
Codex
$ npx skills add martinholovsky/SOTA-skills -a codex
Cursor
$ npx skills add martinholovsky/SOTA-skills -a cursor
Gemini CLI
$ npx skills add martinholovsky/SOTA-skills -a gemini-cli
GitHub Copilot
$ copilot plugin marketplace add martinholovsky/SOTA-skills$ copilot plugin install sota-skills@sota-skills
OpenCode
$ npx skills add martinholovsky/SOTA-skills -a opencode
Windsurf
$ npx skills add martinholovsky/SOTA-skills -a windsurf
Make your AI coding assistant build and audit like your most senior engineer.
Your assistant is brilliant — it just doesn't know your standards, and it forgets the ones it does know as the task grows long. SOTA-skills fixes both, and the fix is measured: from a bare "build X" prompt, best-practice coverage climbs from ~59% to ~98% (+0.39) — the model stops silently dropping tests, rate limiting, structured logging, and TLS (see every number →).
It works by being a loop, not a prompt dump: route in only the rules a task needs,
re-state them every turn, and re-check them last before shipping — so the guidance
survives a long context instead of fading into it. That's why it beats a bigger prompt
instead of becoming one. Native on Claude Code; works with Antigravity CLI, Codex, and any
agent that reads AGENTS.md. Those agents get the skills and an always-on directive, but not
the per-turn re-statement, which is a Claude Code hook
(per-agent detail), and no lift has yet been measured through them.
Under the hood: 43 skills (349 files, ~94k lines) of state-of-the-art 2026
practice, each instruction file under 500 lines so only the matching rules load —
the cap applies to skills/** alone, never to README/CHANGELOG/docs/ — every fast-moving
claim web-verified against a primary source as of the last full sweep (the root
LAST-VERIFIED stamp). Between sweeps an upstream can still move under a claim, so the
router's own operating principle 1 stands: re-verify anything version- or CVE-sensitive at
use time.
Two commands to install:
/plugin marketplace add martinholovsky/SOTA-skills
/plugin install sota-skills@sota-skills
Or clone + link (best if you want a local checkout to read, hack on, or pin).
Skills are discovered from .claude/skills/ (per project) or ~/.claude/skills/
(personal, all projects). Clone the repo, then run the installer — it symlinks
every skill (and your profile, if you have one):
git clone https://github.com/martinholovsky/SOTA-skills && cd SOTA-skills
./scripts/install.sh # personal: ~/.claude/skills (all projects)
./scripts/install.sh --project DIR # one project: DIR/.claude/skills
./scripts/install.sh --target all # also ~/.agents/skills (Copilot, Codex, Cursor, Gemini CLI) + Antigravity's own dirs
./scripts/install.sh --copy # copy instead of symlink (pin a snapshot)
./scripts/install.sh --mcp # optional: register the read-only MCP server for other agents
The installer colour-codes what it did (✓ done · ↻ changed or act on this ·
· no-op) and drops to plain ASCII when the output is not a terminal, on a
non-UTF-8 locale, on TERM=dumb, or with NO_COLOR set — --color=always|never|auto
(or --no-color) overrides the detection either way.
Then describe the task in plain language — routing loads the right skills; the stack comes from your profile or the skills' defaults (naming one is optional):
Design a multi-tenant invoicing service.
Run a full audit of this repo — severity, effort, and fix on every finding.
More install options: Installation · more prompts: Using it.
Five slash commands ship with the library — four bracket a working session, the fifth is
the heavy escalation. scripts/install.sh links them into ~/.claude/commands/, so they work
in any project, not just this one:
| When | What it does | |
|---|---|---|
/sota-resume | start of a session | Finds the open work — every tracker, checkbox and TODO marker, swept with a controlled search — classifies it (ready · needs a decision · deferred · not an item · already done and never ticked off, or made unnecessary by a control that already covers the gap), shows you the table, then executes what you agree to against the project's own CI. |
/sota-close | end of a session | The closure pass: retract first, record open items where the next session will trip over them, update what the session made false, re-derive every number from its source, say what is not done and blocked on whom, then commit the evidence. |
/sota-audit | work finished, or a codebase you did not write | Audits what is in front of you against the library: agrees and pins the scope (a diff's callers included), maps the trust boundaries, runs the scanners that are installed, maps every surface to its owning skills and says which rules files nobody opened, walks each Audit checklist item by item, then fixes what you agree to. |
/sota-deep-audit | a milestone, an inheritance, a go/no-go | The heavy pass, and expensive: the same standard as /sota-audit, run so you can trust the result without trusting the auditor — the full threat model reconstructed from the code (DFD, tested assumptions, a control-presence matrix), then the audit fanned across independent agents, re-measures the numbers past decisions rest on, and hands every serious finding to a refuter that did not find it. |
/sota-report | end of a session | Writes a gitignored field report on where the guidance failed, was absent, was wrong — or was right and did not fire. Prints a gh issue create line; it never posts anything itself. |
They take free-text arguments (/sota-close focus on the migration branch). Full detail:
slash commands.
/sota-resume · /sota-audit · /sota-deep-audit · /sota-close · /sota-report)Deeper docs: Find it fast (docs index) · Does it work? (measured results) · Why it works · Why some lifts expire and others don't · Keeping rules applied as context fills · Roadmap · Agent-loop evals — tools, hidden tests, no model judge (separate repo)
Findings name the control they violate — not just "this looks wrong":
sota-architecture rules/03 §12a)Named standards are the floor. Most of the library is the practice layer no regulation writes down: cancellation & backpressure, retries with jitter, circuit breakers, outbox/saga, double-entry ledgers and the reconciliation that proves an integration is complete rather than merely correct, zero-downtime migrations, measure-first performance, API evolvability, per-language idioms, SLOs, test-suite health — and the ones that only show up once something is already running: triaging a vulnerability report a stranger sent you (reproduce before you rate it, check the cited code even exists, and decide the regulatory clock explicitly, because it starts at awareness), and why a skill can stop triggering with nothing about it changed (a length cap is
Stars on GitHub
Helps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockA development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookInstall it with the command on its page. It includes sota-api-design, sota-architecture, sota-async-concurrency. Its skills do not fire on their own yet. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it