Is mvp-workflow safe to install?

SaferSkills independently audited mvp-workflow (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.

skills/mvp-workflow/SKILL.md · 1 file

skills/mvp-workflow/SKILL.md2.0 KB · Markdown

name: mvp-workflow

description: Orchestrate a Codex-first Web MVP planning workflow from rough idea to build-ready artifacts. Use when the user wants to turn an app idea into a structured MVP plan, PRD, technical blueprint, AGENTS.md context, and implementation tickets.

MVP Workflow

Guide the user through the full Web MVP Blueprint workflow.

Workflow

Idea Brief - clarify the first user, problem, smallest useful outcome, and MVP boundary.
Evidence Research - collect competitor, user, pricing, and feasibility evidence.
Buildable PRD - define pages, features, data objects, acceptance criteria, and success metrics.
Technical Blueprint - choose a practical stack and implementation route.
Agent Context - generate AGENTS.md and agent_docs/.
Build Tickets - generate task files that Codex can execute one at a time.

State Check

Inspect the current project before choosing the next step:

Artifact	Meaning
`docs/IdeaBrief-*.md`	Step 0 complete
`docs/EvidencePack-*.md`	Step 1 complete
`docs/BuildablePRD-*.md`	Step 2 complete
`docs/TechBlueprint-*.md`	Step 3 complete
`AGENTS.md` and `agent_docs/`	Step 4 complete
`tasks/*.md`	Step 5 complete

Routing

If no idea brief exists, use $mvp-idea-brief.
If idea brief exists but no evidence pack exists, use $mvp-research.
If evidence exists but no buildable PRD exists, use $mvp-prd.
If PRD exists but no technical blueprint exists, use $mvp-tech-design.
If technical blueprint exists but no agent context exists, use $mvp-agent-context.
If agent context exists but no task tickets exist, use $mvp-build-tickets.

Rules

Keep the user oriented with the current step and next artifact.
Ask one question at a time when inputs are missing.
Favor small Web MVP scope over broad product ambition.
Preserve explicit "Not in MVP" decisions.
Do not start implementation until agent context and tickets exist, unless the user explicitly skips planning.

mvp-workflow— agent skill

Is mvp-workflow safe to install?

MVP Workflow

Workflow

State Check

Routing

Rules

Audit the pieces. Scan the whole. Decide.