spec-to-code-compliance

Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.

by trailofbits 6.6k GitHub stars CC-BY-SA-4.0 Updated Aug 18, 2026
spec-to-code-compliance skill by trailofbits
spec-to-code-compliance — Security skill by trailofbits

Overview

spec-to-code-compliance is an open-source security skill for Claude Code and compatible agents, published by trailofbits. Its author describes it as: “Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation ag…”. The project has 6.6k stars on GitHub and is available under the CC-BY-SA-4.0 license. Add it to your setup with `/plugin marketplace add trailofbits/skills`.

What spec-to-code-compliance does

Two artifacts disagree, and the job is to find where. The documentation says what the system does; the code decides what it actually does. Every gap between them is either a bug or a documentation fix, and which one it is is the finding.

Best for

What’s inside

The SKILL.md for spec-to-code-compliance is organised into these sections:

  • When to Use
  • When NOT to Use
  • Do not check requirements in this context
  • What comes back, and how to read it
  • Judgment the workflow does not make for you
  • The target does not have to be a contract
  • Reference

Installation

Add spec-to-code-compliance to your agent with:

/plugin marketplace add trailofbits/skills

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Claude Code — ships a claude code plugin marketplace

License

spec-to-code-compliance is published under the CC-BY-SA-4.0 license.

Strengths

  • Clear CC-BY-SA-4.0 license — safe to read and adapt within its terms
  • Ships in trailofbits/skills, an established project with 6,646 GitHub stars
  • Works with Claude Code
  • Actively maintained — repository updated in the last 90 days

Author

trailofbits 41 skills in the catalog · GitHub profile ↗
View skills

Topics

Alternatives to spec-to-code-compliance

Similar skills from other repositories:

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does spec-to-code-compliance do?
Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.
How do I install spec-to-code-compliance?
Run /plugin marketplace add trailofbits/skills in your agent, then reload your skills. Review the source at https://github.com/trailofbits/skills before installing.
Is spec-to-code-compliance free to use?
Yes. spec-to-code-compliance is free and open source under the CC-BY-SA-4.0 license, so you can read, run, and adapt it within that license's terms.
Which agents does spec-to-code-compliance work with?
spec-to-code-compliance lists Claude Code — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does spec-to-code-compliance come from?
spec-to-code-compliance ships inside trailofbits/skills, a repository that contains 41 catalogued skills in total. The repository's 6,646 GitHub stars apply to that whole collection, not to this skill on its own.

Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

Official Claude CodeCodexGemini CLI
6.6k GitHub stars CC-BY-SA-4.0 Updated Aug 18, 2026 Free

Understand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere. Use when starting an audit, threat model, or architecture review on unfamiliar code, and before any vulnerability-hunting pass.

Official Claude Code
6.6k GitHub stars CC-BY-SA-4.0 Updated Aug 18, 2026 Free

Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).

Official Claude Code
6.6k GitHub stars CC-BY-SA-4.0 Updated Aug 18, 2026 Free

Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).

Official Claude Code
6.6k GitHub stars CC-BY-SA-4.0 Updated Aug 18, 2026 Free

Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.

Official Claude Code
6.6k GitHub stars CC-BY-SA-4.0 Updated Aug 18, 2026 Free