Agent skill

trailmark-summary

Runs a Trailmark summary analysis on a codebase. Returns auto-detected languages, entry point count, and dependency list. Use when vivisect or galvanize needs a quick structural overview. Triggers: trailmark summary, code summary, structural overview.

trailofbitsgithub.com/trailofbitsGitHub ↗
claude-codecan modify filesCC-BY-SA-4.0
Install
npx skills add trailofbits/skills --skill trailmark-summary --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 4 KB
Bundled scripts: none
Allowed tools: BashReadGrepGlob
Path: plugins/trailmark/skills/trailmark-summary/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,426
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Trailmark Summary Runs `trailmark analyze --language auto --summary` on a target directory. This is a v0.2-safe workflow; do not require Trailmark 0.4.0 just to produce a summary. ## When to Use - Vivisect Phase 0 needs a quick structural overview before decomposition - Galvanize Phase 1 needs detected languages and entry point count - Quick orientation on an unfamiliar codebase before deeper analysis ## When NOT to Use - Full structural analysis with all passes needed (use `trailmark-structural`) - Detailed code graph queries (use the main `trailmark` skill directly) - You need hotspot scores or taint data (use `trailmark-structural`) ## Rationalizations to Reject | Rationalization | Why It's Wrong | Required Action | |-----------------|----------------|-----------------| | "I can read the code manually instead" | Manual reading misses parser-based language detection, dependency data, and entry point enumeration | Install and run trailmark | | "Language detection doesn't matter" | Wrong language selection produces empty or partial analysis | Use Trailmark's parser-based detection or `--language auto` | | "Partial output is good enough" | Missing any of the three required outputs

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Rationalizations to Reject
  4. Usage
  5. Execution
Ships with 2 files
  • agents/openai.yaml
  • assets/trail-of-bits-mark.svg
Commands it runs
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'
trailmark analyze --language auto --summary {args} 2>&1 || \
uv run trailmark analyze --language auto --summary {args} 2>&1
More from skills
All skills →
About this skill
What does the trailmark-summary skill do?

Runs a Trailmark summary analysis on a codebase. Returns auto-detected languages, entry point count, and dependency list. Use when vivisect or galvanize needs a quick structural overview. Triggers: trailmark summary, code summary, structural overview.

How do I install it?

Run `npx skills add trailofbits/skills --skill trailmark-summary --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.

Keep going