メニュー
Review a product codebase and landing page against 32 viral principles and produce a Virality Score plus ranked fixes. Use to audit virality or prioritize growth. Don't use for SEO, ASO, copywriting, or code review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review or improve code — one skill, four modes: bug/security review (default), performance, clean-code audit, slop cleanup. Pass mode:review|perf|clean|cleanup or infer. Don't use for writing features or generating tests (use test-coverage).
Generate professional diagrams as valid draw.io XML — flowcharts, architecture, C4 models, ER diagrams, sequence diagrams, mind maps, and swimlanes. Don't use for Excalidraw or Mermaid output, hand-drawn sketch styles, or slide decks/presentations.
Generate diagrams as valid Excalidraw JSON — flowcharts, architecture, ER diagrams, mind maps, sequence diagrams, wireframes, C4 models, and more. Don't use for draw.io/Mermaid output, slide decks, or pixel-perfect brand graphics.
Generate a diagram and route to the right engine — draw.io XML (precise, editable, C4, swimlanes) or Excalidraw JSON (hand-drawn, sketch, wireframes). One entry for flowcharts, architecture, ER, sequence, mind maps. Don't use for Mermaid or slides.
Generate landing pages with PAS, AIDA, or StoryBrand — marketing copy from a product brief, or a scannable landing-page rewrite of an existing README. The one skill for landing-page work. Not for blog posts, UX audits, or HTML builds.
Review UI for usability issues using Steve Krug's principles and produce a scannable report. Use when asked for a usability audit, UX review, or UI feedback on screenshots, URLs, or code. Don't use for visual/brand design critique, accessibility (WCAG) audits, or backend/API review.
| name | viral-product-evaluator |
| description | Review a product codebase and landing page against 32 viral principles and produce a Virality Score plus ranked fixes. Use to audit virality or prioritize growth. Don't use for SEO, ASO, copywriting, or code review. |
| license | MIT |
| effort | high |
| metadata | {"version":"1.2.4","author":"Luong NGUYEN <luongnv89@gmail.com>"} |
Grade a product against the 32 principles of viral products. Two inputs — a codebase and a landing page — produce one output: a scored report of what's already satisfied and, in priority order, what to do next to make it more viral.
Trigger when the user wants to:
Do not use for: technical SEO (seo-ai-optimizer), App Store ASO (aso-marketing),
turning a README into a page (landing-page-generator), or bug-hunting code review
(code-review). This skill
evaluates and prioritizes; it does not rewrite the product.
references/*.md files present for the rubric and output shape.Missing prerequisites → stop and report before gathering evidence.
It reads the codebase, fetches the landing page, and writes one report file
(viral-evaluation.md). It does not edit the user's source, change copy, or commit
anything — so no repo-sync/branch guardrail is needed. If the user then asks you to apply
fixes, that is a separate task (hand off to a copy/frontend skill); this skill stops at the
prioritized plan.
Accept any combination the user provides; ask only for what's missing and truly needed.
/browse skill (headless). Capture rendered copy,
headline, CTAs, pricing section, testimonials, nav, and <head> meta (og:image,
twitter:image, description, <title>).index.html, a JSX/TSX/MDX page, a built dist/) → read it directly.index.html, app/page.tsx, pages/index.*, src/App.*, landing/, marketing/,
public/). Confirm the candidate with the user if ambiguous.If neither a URL, a file, nor a detectable page exists, stop and ask the user where the landing page lives — do not invent one.
Run these in sequence. Emit the matching Step Completion Report (see
references/step-reports.md) after each.
/browse; file → read; else auto-detect).price, plan, tier, checkout,
subscription, free, trial, stripe, paddle.references/principles.md — the full rubric. Score every principle PASS / PARTIAL /
FAIL using its criteria. Do not skip any; absence of a thing a viral product would ship
(pricing, testimonials, demo) is a real FAIL, not "unknown".judgment/visual principle (hero punch, emotional headline, OG-image design,
founder presence, novelty, price-vs-competitor) as low-confidence and record what a human
must eyeball.PASS=1, PARTIAL=0.5, FAIL=0, summed over 32, ×100/32,
rounded. Assign the tier (Viral-ready / Promising / Needs work / Not viral yet).references/report-template.md and produce the report in that exact shape:
verdict block → scorecard (all 32) → top fixes (prioritized) → what's working → caveats.viral-evaluation.md (repo root or beside the landing-page source) and
also print the verdict block + top fixes inline.This is a critique tool — its value is candor. Do not inflate scores to be encouraging. If the hero fails, say it fails and show the fix. At the same time, do not invent flaws: a genuine PASS is a PASS. Low-confidence verdicts must be labeled, never laundered into false certainty. When extra instructions justify a deliberate deviation (e.g. a strategic free tier), score the principle as written and explain the trade-off in the caveats — don't silently pass it.
On any failure to fetch inputs or read evidence, report the concrete error and stop — do not guess or continue with incomplete data. Confirm with the user on every gate and before finalizing the report. If a principle cannot be evidenced, mark FAIL or low-confidence; never invent.
After each phase, emit the report from references/step-reports.md. The three phases are
Gather Evidence, Evaluate, and Prioritize & Report.
A report containing:
references/principles.md — the 32-principle rubric: per-principle checks, evidence source,
PASS/PARTIAL/FAIL bars, confidence flags, and the scoring formula. Load every run.references/report-template.md — exact output shape (verdict block, scorecard, prioritized
fixes, strengths, caveats) with a calibration example.references/step-reports.md — Step Completion Report formats for the three phases.