Trailmark Summary

Runs

trailmark analyze --summary

on a target directory.

When to Use

Vivisect Phase 0 needs a quick structural overview before decomposition
Galvanize Phase 1 needs language detection 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 dependency graph shape and entry point enumeration	Install and run trailmark
"Language detection doesn't matter"	Wrong language flag produces empty or incorrect analysis	Detect language from file extensions first
"Partial output is good enough"	Missing any of the three required outputs (language, 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.

bash

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.

Step 2: Detect the primary language.

bash

find {args} -type f \( -name '*.rs' -o -name '*.py' \
  -o -name '*.go' -o -name '*.js' -o -name '*.jsx' \
  -o -name '*.ts' -o -name '*.tsx' -o -name '*.sol' \
  -o -name '*.c' -o -name '*.h' -o -name '*.cpp' \
  -o -name '*.hpp' -o -name '*.hh' -o -name '*.cc' \
  -o -name '*.cxx' -o -name '*.hxx' \
  -o -name '*.rb' -o -name '*.php' -o -name '*.cs' \
  -o -name '*.java' -o -name '*.hs' -o -name '*.erl' \
  -o -name '*.cairo' -o -name '*.circom' \) 2>/dev/null | \
  sed 's/.*\.//' | sort | uniq -c | sort -rn | head -5

Map the most common extension to a language flag:

```
.rs
```
->
```
--language rust
```
```
.py
```
-> (no flag, Python is default)
```
.go
```
->
```
--language go
```
```
.js
```
/
```
.jsx
```
->
```
--language javascript
```
```
.ts
```
/
```
.tsx
```
->
```
--language typescript
```
```
.sol
```
->
```
--language solidity
```
```
.c
```
/
```
.h
```
->
```
--language c
```
```
.cpp
```
/
```
.hpp
```
/
```
.hh
```
/
```
.cc
```
/
```
.cxx
```
/
```
.hxx
```
->
```
--language cpp
```
```
.rb
```
->
```
--language ruby
```
```
.php
```
->
```
--language php
```
```
.cs
```
->
```
--language c_sharp
```
```
.java
```
->
```
--language java
```
```
.hs
```
->
```
--language haskell
```
```
.erl
```
->
```
--language erlang
```
```
.cairo
```
->
```
--language cairo
```
```
.circom
```
->
```
--language circom
```

Step 3: Run the summary.

bash

trailmark analyze --summary {language_flag} {args} 2>&1 || \
  uv run trailmark analyze --summary {language_flag} {args} 2>&1

Step 4: Verify the output.

The output must include ALL THREE of:

Language detection (at least one language name)
Entry point count (or "no entry points found")
Dependency graph shape (module count or "single module")

If any are missing, report the gap. Do not fabricate output.

Return the full trailmark output.

trailmark-summary

NPX Install

Tags

SKILL.md Content

Trailmark Summary

When to Use

When NOT to Use

Rationalizations to Reject

Usage

Execution