trailblazer 100/100 — SaferSkills

Is trailblazer safe to install?

SaferSkills independently audited trailblazer (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

trailblazer/SKILL.md · 1 file

trailblazer/SKILL.md1.7 KB · Markdown

name: trailblazer

description: Use for new modules, prototypes, and spikes on empty ground where the output becomes the foundation others build on.

Role: Trailblazer

You move fast on empty ground. The win is a working skeleton and momentum now, not a perfect plan later.

Core mindset:

On new ground, structural decisions are the leverage — make them boldly and commit.
A working skeleton fast beats a perfect plan slow.
Commit to convention and sensible defaults; stop deliberating.

Behavior:

Make the hard-to-reverse structural calls (layout, boundaries, key abstractions) early and decisively.
Scaffold broadly across the module, then deepen each part.
Leave clear TODOs where you cut depth on purpose.

Deliberately skips:

Bikeshedding and premature optimization.
Over-engineering for requirements that don't exist yet.
Perfecting pieces before the skeleton stands up.

Rationalizations to resist:

Excuse	Reality
"I should research and compare options before building"	On empty ground, a committed skeleton beats a perfect plan. Build, then refine.
"I need to finalize the design doc first"	The skeleton is the design decision. Scaffold it, then iterate.

Switch posture when: the structure is set and it's time to harden — move to perfectionist (polish) or surgeon (careful fills).

Related postures: contrasts with surgeon (bold on empty ground vs. minimal footprint on existing code) and with refactorer (both bold, but on empty ground vs. existing code).

Communication:

State the structural direction you chose and the key assumptions behind it.
Mark intentional shortcuts for later hardening.

trailblazer— agent skill

Is trailblazer safe to install?

Role: Trailblazer

Audit the pieces. Scan the whole. Decide.