trailmark-structural
Runs full Trailmark structural analysis by building a graph, running `preanalysis()`, and reporting hotspots, taint, blast radius, privilege boundaries, attack surface, and version-gated Trailmark 0.4+/0.5+ data such as proxy counts, subgraph edges, type/reference summaries, and entrypoint attributes. Use when vivisect needs detailed structural data for a target. Triggers: structural analysis, blast radius, taint analysis, complexity hotspots, proxy nodes, type references.
npx skills add trailofbits/skills --skill trailmark-structural --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Trailmark Structural Analysis Builds a Trailmark graph and runs `engine.preanalysis()` to compute all four pre-analysis passes. The core workflow is v0.2-safe; v0.4-only details are included only after checking method availability, and newer builds enrich the same output (0.5.0+ adds an `attributes` key to attack-surface entries and `proxy.external:*` nodes from `.trailmark/links.toml`) without any workflow change. ## When to Use - Vivisect Phase 1 needs full structural data (hotspots, taint, blast radius, privilege boundaries) - Detailed pre-analysis passes for a specific target scope - Generating complexity and taint data for audit prioritization - Inspecting proxy/unresolved-call counts, subgraph edges, or type-reference summaries when Trailmark 0.4.0+ is installed ## When NOT to Use - Quick overview only (use `trailmark-summary` instead) - Ad-hoc code graph queries (use the main `trailmark` skill directly) - Target is a single small file where structural analysis adds no value ## Rationalizations to Reject | Rationalization | Why It's Wrong | Required Action | |-----------------|----------------|-----------------| | "Summary analysis is enough" | Summary skips taint, blast ra
- When to Use
- When NOT to Use
- Rationalizations to Reject
- Usage
- Execution
trailmark analyze --help 2>/dev/null || \
uv run trailmark analyze --help 2>/dev/null
trailmark --version 2>/dev/null || uv run trailmark --version 2>/dev/null || true
python3 - "{args}" <<'PY'What does the trailmark-structural skill do?
Runs full Trailmark structural analysis by building a graph, running `preanalysis()`, and reporting hotspots, taint, blast radius, privilege boundaries, attack surface, and version-gated Trailmark 0.4+/0.5+ data such as proxy counts, subgraph edges, type/reference summaries, and entrypoint attributes. Use when vivisect needs detailed structural data for a target. Triggers: structural analysis, blast radius, taint analysis, complexity hotspots, proxy nodes, type references.
How do I install it?
Run `npx skills add trailofbits/skills --skill trailmark-structural --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From trailofbits/skills, a repository with 6,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.