Is architect-first safe to install?

SaferSkills independently audited architect-first (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.

.claude/skills/architect-first/SKILL.md · 1 file

.claude/skills/architect-first/SKILL.md1.8 KB · Markdown

name: architect-first

description: Forces a planning phase before any code is written. Triggers on /architect or at the start of BUILD sessions. Requires the student to articulate inputs, outputs, failure modes, and data flow before implementation begins. Inspired by Copilot Plan Mode and production engineering practices.

Architect First -- Plan Before Code

No code gets written until the architecture is clear. If you can't explain the data flow, you're not ready to code.

Trigger

/architect or /architect <exercise>
Automatically before BUILD: sessions

Execution

Read the exercise to understand what's being built.

The student articulates the plan (not Claude):

What are the inputs? (types, formats, edge cases)
What are the outputs? (exact format, error states)
What are the failure modes? (what can go wrong?)
What's the data flow? (step by step, plain English)
What standard library modules will you use and why?

Challenge the plan:

"What happens when the input is empty?"
"What happens at 10x scale?"
"Where would you add logging?"
"How would you test this?"
"In a production data pipeline, how would this work?"
"How will you structure your functions so each can be tested independently?"

Gate: Only after the student has a clear, challenged plan → "Go build it."

Rules

This skill is a gate, not a guide. The student articulates the plan.
Do NOT write pseudocode, code, or architecture diagrams.
The plan is in natural language only.
Ask "why" for every design decision.
The plan doesn't need to be perfect. It needs to exist.
If the student skips this and jumps to code, stop them: "Architecture first."

Production Patterns Reference

See PATTERNS.md for common architecture patterns to ask about during planning.

architect-first— agent skill

Is architect-first safe to install?

Architect First -- Plan Before Code

Trigger

Execution

Rules

Production Patterns Reference

Audit the pieces. Scan the whole. Decide.