MVP
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only MVP planning guide with no code, credentials, or system access; the main cautions are ethical use of validation tactics and a minor role-file path mismatch.
This skill appears safe to install as a business guidance aid. Treat its MVP testing ideas as advisory, make sure any user-facing experiments are honest about early-stage limitations, and be aware that the role-specific file links may need path correction.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used carelessly, the advice could lead to misleading early users about how a product works or how their data is handled.
The guide recommends a common MVP validation technique where users may believe a process is automated when it is manual. This is purpose-aligned product advice, but it can create trust or disclosure issues if followed literally.
Wizard of Oz 1. Build the UI/interface 2. You manually do the work behind the scenes 3. User thinks it's automated
Use fake-door and Wizard-of-Oz tests with clear early-access language, avoid false claims, and disclose manual processing where privacy, payment, or user expectations could be affected.
Role-specific guidance may fail to load or may require manual navigation if the skill runtime expects the referenced paths exactly.
The role table references files under a roles/ directory, but the provided manifest lists the role files at the package root, such as technical.md and pm.md. This is a coherence/package-path issue, not evidence of malicious behavior.
| Technical Founder | Scope control, stop over-engineering | `roles/technical.md` |
Correct the references to the packaged file paths or move the files into the referenced roles/ directory.