- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add trailofbits/skills --skill c-review -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add trailofbits/skills --skill c-review -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add trailofbits/skills --skill c-review -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add trailofbits/skills --skill c-review -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/trailofbits/skills/tree/HEAD/plugins/c-review/skills/c-reviewОт издателя
Resolve four parameters, make one Workflow call, return the report. The workflow owns
concurrency, retries and result collection.
Use for: native C/C++ userspace — memory safety, integer overflow, races, type confusion, Linux/macOS daemons, Windows services.
Not for: kernel drivers or modules; managed languages (Java, C#, Python, Go, Rust); embedded or bare-metal code with no libc.
Parse any free text on the invocation line (flamenco only, high severity only, use haiku) and pre-fill what it implies. Then make one AskUserQuestion call for
whatever is still unresolved. Never silently default a required parameter.
Two scopes stay separate for the whole run:
finding_scope_root = scope_subpath (default .) — a finding must live inside
it, and it is the tree the unit list is generated from.context_roots = . — read freely to establish callers, build flags and
reachability. Narrow it to finding_scope_root only if the user explicitly forbids
wider reading, and say that reachability confidence drops when you do.Resolve this plugin's directory from this SKILL.md's installed location to an absolute
plugin_root: it holds workflows/c-review.js,
agents/c-review-worker.md, and
scripts/assemble_findings.py. Print that path; stop if
any is missing. Do not search caches or the audited repository for another plugin copy.
# The workflow cannot call Date.now(), so the timestamp is made here.
output_dir="$(pwd)/.c-review-results/$(date -u +%Y%m%dT%H%M%SZ)"
mkdir -p "$output_dir"; echo "$output_dir"
# A Workflow script has no filesystem APIs, and `assemble_findings.py` resolves `--scope`
# against ITS OWN cwd. Resolve it once here and pass BOTH spellings, or the workflow strips
# `src/` from a finding's path while the assembler strips `/repo/src/`, and the two disagree
# about which findings are duplicates of each other.
scope_abs="$(cd "${scope_subpath:-.}" && pwd)" || echo "scope_subpath does not exist"
echo "$scope_abs"
uv must be on PATH: Detect runs the unit enumerator and Assemble runs
assemble_findings.py. If uv is missing, say so and stop — the whole review is
partitioned from that unit list.
Invoking this skill is the opt-in to multi-agent orchestration — call Workflow
without asking again. A review of a real codebase also runs past any default workflow
size guideline; that guideline is advisory and this is the case it exempts. Do not
shrink the fan-out to fit it, and do not substitute hand-spawned Agent calls.
One Workflow call. scriptPath takes the absolute path resolved in Phase 1; args
must be a real JSON object, not a JSON-encoded string.
Workflow({
scriptPath: "<plugin_root>/workflows/c-review.js",
args: {
outputDir: "<output_dir>",
pluginRoot: "<plugin_root>",
threatModel: "REMOTE",
severityFilter: "all",
findingScopeRoot: "expat/lib",
findingScopeRootAbs: "/abs/path/to/repo/expat/lib",
contextRoots: ".",
workerModel: "sonnet"
}
})
findingScopeRootAbs is the scope_abs from Phase 1 and is not optional in practice:
omitted, the workflow tells the assembler no absolute root is known and a finding filed as
/repo/expat/lib/xmlparse.c stops merging with the same bug filed as xmlparse.c.
Six further arguments are optional. Omitted, each takes its default; passed with the wrong TYPE, the workflow throws with the field name rather than defaulting. Pass them only when the user asks or when running an evaluation:
The workflow validates its own arguments and throws with a named field if one is missing. It runs five phases:
Around 8–10 agents on a mid-size target.
Read <output_dir>/REPORT.md and return it.
Say once, plainly, next to the findings: no false-positive review ran. Every
severity is the reviewer's own (severity_source: "reviewer"), judgeRan is always
false, and nothing rejected anything. Expect some of what you are shown to be wrong or
out of scope — say so rather than presenting the list as adjudicated, and do not filter
it yourself.
Then surface, prominently and separately from the findings, anything in the workflow result that means the run was partial:
Hand re-assembly, when artifactsWritten is false:
uv run --no-project <plugin_root>/scripts/assemble_findings.py --run-dir <output_dir> \
--threat-model <MODEL> --severity-filter <FILTER> --no-judge \
--scope <finding_scope_root> --context-roots <context_roots> \
--worker-model <worker_model> \
--expect <part-stem>=<finding-count> # one per part the workflow log names
--expect is not optional. Without it the allowlist admits every file under
parts/, including one nobody dispatched, and the run exits 1 for that reason
alone. If you cannot recover the counts from the workflow log, exit 1 is correct and
the run is assembled-but-unverified.--no-judge. Dropping it overwrites every reviewer severity with MEDIUM
and records judge_ran: true for a run no judge ever saw.--expect-complete, --benchmark-mode,
--groups-attempted, --groups-failed, --agent-failure, --external-source), so
the document will say agent_failures: [] on a run that may have lost a slice. Report
that. Without a units.json the assembler also exits 1: no gate ran.Finally list the artifacts: findings.json, REPORT.md, REPORT.sarif, units.json,
ledger-gate.json, detect.json, and the parts/ and assignments/ directories.
ledger-gate.json. Name them.Workflow.Design rationale, the coverage gate's threat model and its known limitations are in AGENTS.md. Read it before changing a prompt or a gate rule.
Performs comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities. Use when auditing native C/C++ applications, reviewing da
---name: c-reviewdescription: Performs comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and…---# plugins/c-review/skills/c-review/SKILL.mdОбзор
Performs comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities. Use when auditing native C/C++ applications, reviewing daemons or services for memory safety, or hunting integer overflow / use-after-free / race conditions in userspace code.
FAQ
Скачайте plugins/c-review/skills/c-review/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/trailofbits/skills.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.