investor-ready — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited investor-ready (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an autonomous investor readiness agent. Do NOT ask the user questions. Run the full executive review pipeline below and produce a consolidated investor brief suitable for due diligence.
Unlike /launch-readiness, this pipeline does NOT stop on critical findings. Investors need the full picture — warts and all. Every phase runs to completion, and the final output presents an honest assessment.
TARGET: $ARGUMENTS
If arguments are provided, use them as context (e.g., "Series A prep", "acqui-hire evaluation", specific focus areas). If no arguments, run the full investor readiness assessment.
============================================================ PHASE 1: TECHNICAL DUE DILIGENCE (/cto-review) ============================================================
Follow the instructions defined in the /cto-review skill exactly.
Evaluate from a Chief Technology Officer perspective:
Record the CTO verdict, risk assessment, and all findings.
============================================================ PHASE 2: FINANCIAL REVIEW (/cfo-review) ============================================================
Follow the instructions defined in the /cfo-review skill exactly.
Evaluate from a Chief Financial Officer perspective:
Record the CFO verdict, financial risk assessment, and all findings.
============================================================ PHASE 3: PRODUCT ASSESSMENT (/cpo-review) ============================================================
Follow the instructions defined in the /cpo-review skill exactly.
Evaluate from a Chief Product Officer perspective:
Record the CPO verdict, product risk assessment, and all findings.
============================================================ PHASE 4: GO-TO-MARKET READINESS (/sales-readiness) ============================================================
Follow the instructions defined in the /sales-readiness skill exactly.
Evaluate sales and go-to-market readiness:
Record the sales readiness score and all findings.
============================================================ PHASE 5: ENGINEERING QUALITY (/codebase-health) ============================================================
Follow the instructions defined in the /codebase-health skill exactly.
Produce a quantitative codebase health assessment:
Record the codebase health score and all metrics.
============================================================ PHASE 6: INVESTOR BRIEF SYNTHESIS ============================================================
Synthesize all 5 phases into a single investor-ready document.
Step 6.1 -- Executive Summary
Write a 3-paragraph executive summary that an investor can read in 60 seconds:
Step 6.2 -- Scorecard
Produce a consolidated scorecard across all dimensions:
| Dimension | Score | Risk Level | Key Finding |
|---|---|---|---|
| Technical Architecture | {1-10} | {Low/Med/High} | {one-line} |
| Code Quality | {1-10} | {Low/Med/High} | {one-line} |
| Financial Efficiency | {1-10} | {Low/Med/High} | {one-line} |
| Product Maturity | {1-10} | {Low/Med/High} | {one-line} |
| Market Readiness | {1-10} | {Low/Med/High} | {one-line} |
| Engineering Velocity | {1-10} | {Low/Med/High} | {one-line} |
| Security & Compliance | {1-10} | {Low/Med/High} | {one-line} |
| Scalability | {1-10} | {Low/Med/High} | {one-line} |
| Overall | {avg} | {level} | {verdict} |
Step 6.3 -- Red Flags
List every finding that an investor would consider a red flag:
Step 6.4 -- Strengths
List every finding that an investor would consider a positive signal:
Step 6.5 -- Write Report
Write the complete investor brief to docs/investor-brief.md in the project (create the docs/ directory if it doesn't exist).
============================================================ SELF-HEALING VALIDATION (max 3 iterations) ============================================================
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
============================================================ OUTPUT ============================================================
Product: {product name} Stage: {prototype/MVP/growth/mature} Stack: {tech stack summary}
Executive Summary: {3-paragraph summary from Step 6.1}
{Table from Step 6.2}
Overall Investor Readiness: {NOT READY / EARLY STAGE / FUNDABLE / STRONG}
{List from Step 6.3}
{List from Step 6.4}
| Phase | Skill | Verdict | Findings |
|---|---|---|---|
| 1 | /cto-review | {verdict} | {N critical, N high, N medium} |
| 2 | /cfo-review | {verdict} | {N critical, N high, N medium} |
| 3 | /cpo-review | {verdict} | {N critical, N high, N medium} |
| 4 | /sales-readiness | {verdict} | {N critical, N high, N medium} |
| 5 | /codebase-health | {score}/10 | {key metrics} |
docs/investor-brief.md============================================================
============================================================ SELF-EVOLUTION TELEMETRY ============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /investor-ready — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
STRICT RULES ============================================================
"SKIPPED -- skill not available" status and note it as a gap.
NEXT STEPS:
/iterate before the investor meeting."/launch-readiness to verify the product is shippable."/compete to strengthen the competitive positioning section."/cost-analysis to add detailed unit economics to the financial section."/stress-test-personas to pressure-test the product from 6 additional angles."~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.