Is prototype safe to install?

SaferSkills independently audited prototype (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/prototype/SKILL.md · 1 file

.claude/skills/prototype/SKILL.md1.6 KB · Markdown

name: prototype

description: Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts. Use when the user wants to prototype, wireframe, map a user flow, or plan/run usability testing.

Skill: Prototype & Research

Guide work through the right fidelity level with validation.

Steps

Read workflows/prototyping.md (5-level fidelity ladder, journey mapping template, usability-testing script, sample data).
Identify the current need and pick the lowest fidelity that answers it — never skip levels:

Content-first (info needs) → Wireframe (layout/nav) → Low-fi (task completion) → High-fi (visual/a11y) → Code (feasibility/perf).

For flows: produce a user-journey map with decision points, error paths, and edge cases.
For validation: define the usability test (tasks, success criteria, 5-user rule) using the script.
High-fi/code steps pull tokens (tokens/*), components (components/*), taste (taste/*), and a11y (accessibility/*).

Output

The artifact at the chosen fidelity + an explicit "what we validate next" plan.

Verification (before declaring done)

The fidelity matches the question being answered — no level skipped.
Flows include decision points, error paths, and edge cases (empty/loading/overflow), not just the happy path.
A concrete validation step is named (tasks + success criteria), not "test later".
High-fi/code artifacts pass the same token + a11y bar as design-code (no hardcoded values, contrast, states).

prototype— agent skill

Is prototype safe to install?

Skill: Prototype & Research

Steps

Output

Verification (before declaring done)

Audit the pieces. Scan the whole. Decide.