AGENTIC MEMORY

Skills

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

← Back to Skills

trailmark-finding-triage

Performs graph-assisted triage of a single security finding, SARIF result, weAudit annotation, suspicious function, or report excerpt using Trailmark reachability, entrypoint paths, taint, privilege-boundary, blast-radius, caller/callee, and neighborhood evidence. Use when deciding whether one candidate issue is reachable, prioritizing a finding before PoC work, preparing evidence for exploit validation, or checking whether a static-analysis result is actionable.

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-finding-triage 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

Return a concise evidence packet. Use Markdown unless the user asks for JSON.

# Trailmark Finding Triage: <title>

## Verdict

Status: Promote | Needs manual review | Deprioritize | Blocked
Confidence: High | Medium | Low

## Candidate

- Source:
- Location:
- Bound node:
- Claimed issue:

## Graph Evidence

- Entrypoint reachable:
- Entry paths:
- Tainted:
- Privilege boundary:
- Blast radius:
- Direct callers:
- Direct callees:
- Relevant sinks:

## Manual Review Targets

| Target | Why it matters |
|---|---|

## Limitations

## Recommended Next Step

Verdict Criteria

| Verdict | Use when | |---|---| | Promote | The candidate binds cleanly, has reachable entrypoint paths, and graph evidence supports plausible impact | | Needs manual review | The candidate is reachable but exploitability depends on validation, authorization, type, or state semantics | | Deprioritize | The candidate is not entrypoint-reachable, is only trusted-internal, or sits in test/generated/vendor code outside scope | | Blocked | The candidate cannot be bound, Trailmark fails, or the language/parser is unsupported |

Confidence Criteria

| Confidence | Use when | |---|---| | High | Binding is exact, paths are explicit, and graph evidence is consistent | | Medium | Binding is clear but path or sink evidence has uncertainty | | Low | Binding is ambiguous, dynamic dispatch/proxy edges dominate, or important graph features are unavailable |

Wording Requirements

  • Say "graph evidence supports" instead of "Trailmark proves".
  • Say "manual review target" for validators, auth checks, and sanitizers.
  • Separate "reachable" from "attacker controlled".
  • Separate "candidate" from "confirmed vulnerability".