CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trailmark

Builds and queries multi-language source and binary code graphs for security analysis. Includes pre-analysis passes for blast radius, taint propagation, privilege boundaries, entry point enumeration, proxy/unresolved-call tracking, type/reference queries, structural traversal, graph diffs, audit augmentation, declared cross-language/FFI/external links via `.trailmark/links.toml`, and SQL schema graphs. Use when analyzing call paths, mapping attack surface, finding complexity hotspots, enumerating entry points, tracing taint propagation, measuring blast radius, importing SARIF/weAudit/binary findings, linking source graphs across language or RPC boundaries, or building a code graph for audit prioritization. Feature-gate version-specific Trailmark APIs before using them; prefer `trailmark.parse.detect_languages()` or `--language auto` when the target language is unknown or polyglot.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable skill body: executable commands, complete version-gated code, a rationalization table with required actions, and real reference files one level deep. Its main weaknesses are repetition (the detect_languages fallback and preanalysis-handoff guidance each appear multiple times) and inline version-enumeration content that inflates token cost and would fit better in a reference file.

Suggestions

Consolidate the detect_languages/supported_languages 0.2.x import-fallback guidance into one section (Language Selection) and reference it from the others instead of repeating it three times.

Move the v0.2-safe baseline method list and the per-version (0.2.2/0.3.x/0.4+/0.5+) feature enumerations into a references/version-compat.md file, keeping only the version-check command and gating principle in SKILL.md.

State the end-to-end workflow once as a short numbered sequence (install → verify version → parse with --language auto → preanalysis → query) so the section order becomes an explicit checklist.

DimensionReasoningScore

Conciseness

The body is dense and operational rather than padded, but repeats guidance in multiple places — the detect_languages 0.2.x import fallback is explained in the Version Gate section ("detect_languages() itself is v0.2-safe via from trailmark.query.api import detect_languages"), again as a comment in Programmatic API, and again in Language Selection — and inlines long version-specific enumerations (the ~20-method "v0.2-safe baseline" list, the 27-language parser list) that could be tightened or split out.

3 / 5

Actionability

Commands are copy-paste ready ("uv tool install trailmark", "uv run trailmark analyze --language auto --summary {targetDir}") and the Python snippets are complete and executable, including hasattr()-gated fallbacks and a fully specified .trailmark/links.toml example with all fields and defaults documented. Version checking is given as an exact command with instructions to compare numerically.

5 / 5

Workflow Clarity

A clear implied sequence (install → version check → parse → preanalysis → query) with genuine checkpoints: numeric version comparison, "distinguish with trailmark analyze --help" for diagnosing a missing tool vs. old install, and "Always run engine.preanalysis() before handing off". It falls short of a 5 because there is no explicit end-to-end numbered workflow tying the sections together, and error-recovery guidance is spread across sections rather than a feedback loop.

4 / 5

Progressive Disclosure

Two real, one-level-deep reference files are well signaled with markdown links at natural points ([references/preanalysis-passes.md], [references/query-patterns.md]), and section structure is clear. However, substantial reference-style material is inlined in SKILL.md itself — the v0.2-safe baseline API list, the 0.3/0.4/0.5 feature enumerations, and the full parser-name list — which belongs in a version-compatibility reference file.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person voice, comprehensive concrete capabilities, an explicit Use-when clause with natural trigger terms, and a distinct code-graph-security niche. The only soft spot is slight breadth ("analyzing call paths", "security analysis") that could overlap with adjacent code-review skills, and its length is at the upper bound of what a description needs.

DimensionReasoningScore

Specificity

"Builds and queries multi-language source and binary code graphs for security analysis" is followed by a comprehensive list of concrete capabilities: "blast radius, taint propagation, privilege boundaries, entry point enumeration, proxy/unresolved-call tracking, type/reference queries, structural traversal, graph diffs, audit augmentation... and SQL schema graphs" — far beyond the minor-gaps level of anchor 4, with no vague filler.

5 / 5

Completeness

It explicitly answers both questions: the "what" is a full capability inventory in third person ("Builds and queries..."), and the "when" is an explicit "Use when..." clause with concrete trigger phrases, matching the anchor-5 example pattern exactly rather than the merely-explicit "when" of anchor 4.

5 / 5

Trigger Term Quality

The "Use when" clause covers natural phrases a security auditor would actually say — "analyzing call paths, mapping attack surface, finding complexity hotspots, enumerating entry points, tracing taint propagation, measuring blast radius, importing SARIF/weAudit/binary findings" — including synonyms (source graphs / code graph, language or RPC boundaries) rather than only technical jargon.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — code-graph construction for security analysis with specialized triggers (taint propagation, blast radius, SARIF import) — but phrases like "analyzing call paths" and "security analysis" have minor overlap risk with general code-exploration or security-review skills, so it sits at anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

trailofbits/skills

Path

plugins/trailmark/skills/trailmark/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.