trailmark-summary
About
The `trailmark-summary` skill provides a quick structural overview of a codebase by running a Trailmark analysis. It returns auto-detected programming languages, counts entry points, and lists dependencies, which is ideal for initial orientation or when a lightweight analysis is needed. Use this skill for preliminary assessments before deeper analysis, but switch to `trailmark-structural` for full analysis with hotspot or taint data.
Quick Install
Claude Code
Recommendednpx skills add trailofbits/skills -a claude-code/plugin add https://github.com/trailofbits/skillsgit clone https://github.com/trailofbits/skills.git ~/.claude/skills/trailmark-summaryCopy and paste this command in Claude Code to install this skill
Documentation
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
trailmarkskill 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 (detected languages, entry points, dependencies) means incomplete analysis | Verify all three are present |
| "Tool isn't installed, I'll skip it" | This skill exists specifically to run trailmark | Report the installation gap instead of skipping |
Usage
The target directory is passed via the args parameter.
Execution
Step 1: Check that trailmark is available.
trailmark analyze --help 2>/dev/null || \
uv run trailmark analyze --help 2>/dev/null
If neither command works, report "trailmark is not installed"
and return. Do NOT run pip install, uv pip install,
git clone, or any install command. The user must install
trailmark themselves.
Optionally record the version if the installed build supports it:
trailmark --version 2>/dev/null || uv run trailmark --version 2>/dev/null || true
Do not fail if the version command is missing; older v0.2.x builds may still support the summary workflow.
Step 2: Detect languages with Trailmark's parse API.
python3 - "{args}" <<'PY'
import json
import sys
try:
from trailmark.parse import detect_languages # canonical location since 0.3.x
except ModuleNotFoundError:
# v0.2.x predates trailmark.parse; the same function lives in query.api
from trailmark.query.api import detect_languages
print(json.dumps(detect_languages(sys.argv[1])))
PY
If the import fails, rerun the same snippet with uv run --with trailmark python - "{args}".
If the result is [], report "Trailmark found no supported languages under
target" and return.
Step 3: Run the summary with auto-detection.
trailmark analyze --language auto --summary {args} 2>&1 || \
uv run trailmark analyze --language auto --summary {args} 2>&1
Step 4: Verify the output.
The output must include ALL THREE of:
- Detected languages from Step 2
Entrypoints:line from the summary outputDependencies:line from the summary output
If any are missing, report the gap. Do not fabricate output.
Return the detected language list plus the full Trailmark summary output. If a version string was available, include it in the returned metadata.
GitHub Repository
Frequently asked questions
What is the trailmark-summary skill?
trailmark-summary is a Claude Skill by trailofbits. Skills package instructions and resources that Claude loads on demand, so Claude can perform trailmark-summary-related tasks without extra prompting.
How do I install trailmark-summary?
Use the install commands on this page: add trailmark-summary to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does trailmark-summary belong to?
trailmark-summary is in the Design category.
Is trailmark-summary free to use?
Yes. trailmark-summary is listed on AIMCP and free to install.
Related Skills
Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
This skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.
This skill provides a comprehensive guide for developers to connect MCP servers to Claude Code using HTTP, stdio, or SSE transports. It covers installation, configuration, authentication, and security for integrating external services like GitHub, Notion, and custom APIs. Use it when setting up MCP integrations, configuring external tools, or working with Claude's Model Context Protocol.
This skill helps developers choose between Claude Code Web and CLI interfaces based on task analysis, then enables seamless session teleportation between these environments. It optimizes workflow by managing session state and context when switching between web, CLI, or mobile. Use it for complex projects requiring different tools at various stages.
