AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

trailmark-review-gate

Runs a Trailmark structural review gate over a branch, pull request, fix commit, release diff, or git ref range to detect new entrypoints, new tainted paths, removed validation or authorization calls, privilege-boundary drift, blast-radius growth, complexity growth, and newly reachable sensitive sinks. Use when reviewing a PR, branch, remediation commit, or release diff where graph-level security regressions should be checked before merge.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read trailofbits--trailmark-review-gate at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 4

references/output-format.md

Output Format

Use Markdown unless the user asks for JSON.

# Trailmark Review Gate

## Verdict

Gate: PASS | WARN | FAIL | UNKNOWN
Confidence: High | Medium | Low

## Triggered Rules

| Rule | Verdict | Evidence |
|---|---|---|

## Structural Changes

| Change | Before | After | Review target |
|---|---|---|---|

## Entrypoint And Reachability Changes

## Privilege And Taint Changes

## Blast Radius And Complexity Changes

## Limitations

## Recommended Reviewer Actions

Evidence Requirements

For each triggered rule, include:

  • changed node or edge identifier
  • source file or symbol when available
  • entrypoint path when relevant
  • before/after metric when metric-based
  • manual review target

Wording Requirements

  • Say "gate fired" instead of "vulnerability found".
  • Say "review target" instead of "exploit path" unless exploitability is separately established.
  • Say UNKNOWN when Trailmark fails or parser support is too incomplete.
  • Do not claim a PASS means the change is secure.