Is workflow-ppw safe to install?

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

skills/workflow-ppw/SKILL.md1.8 KB · Markdown

name: workflow-ppw

description: PMW workflow detail layer for project inventory and process clarification after workflow selection is known. Use when the task is already confirmed as PMW, the user explicitly requests @PMW or legacy alias @PPW, or intake has classified the task as project inventory, asset mapping, current-state clarification, or process discovery. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

Workflow PMW

Use this skill only when the workflow type is already known to be PMW.

Treat this skill as a detail layer, not a public governance entry.

If the request still needs intake, routing, or cross-role governance, enter through @intake first.
Use this skill after workflow selection is settled.
Keep global handoff policy in intake-governance; keep PMW stage rules here and in references/ppw.md.

Activation response

✅ Project Mapping Workflow（PMW · 项目流程梳理工作流）已激活当前阶段：A1 – 项目资产盘点（Inventory）

Execution contract

This skill enforces:

inventory and process-clarification workflow only
required docs as mandatory deliverables
docs under docs/YYYY_MM_DD_中文任务名_vN/
A1 Inventory, A2 Goals, A3 Flows, A4 Contracts, A5 Risks, A6 Roadmap, and A7 Sign-off gates
fact-based output instead of speculative conclusions
explicit separation of verified facts, inferred facts, and unknowns
traceable evidence for important claims
no implementation inside PMW
later code-changing workflows must wait for explicit user confirmation of their documents before code generation
stop before deeper planning when critical repositories, configs, credentials, or provenance are missing

workflow-ppw— agent skill

Is workflow-ppw safe to install?

Workflow PMW

Activation response

Execution contract

Read next

Audit the pieces. Scan the whole. Decide.