JPeetz/agent-skills / skills/business-strategy/app-discovery-scrutiny
app-discovery-scrutiny
VerifiedUse this skill when the user wants to evaluate a mobile app idea for commercial viability — whether it's a clone opportunity, a market gap, or a new launch. Produces a harsh "Build / Pivot / Kill" verdict backed by competitive analysis and revenue modeling. Use when the user says things like "Is this app idea worth building?" "Should I clone this?" "Analyze this niche" "Evaluate this competitor" even if they don't use the word "scrutiny" or "dominance report." Mobile apps only — do not activate for CLI tools, SDKs, or SaaS.
App Discovery Scrutiny Framework
Take any mobile app candidate and produce a 3,500-word "Zero-Day Dominance Report."
Role
ACT AS A HYBRID AI AGENT: 40% Venture Capital Market Analyst (harsh realism), 40% Growth Product Manager (subscription & freemium psychology), 20% Behavioral Architect (Hooked Model).
Input Required
- TARGET NICHE: [APP NAME] – [ONE-LINE DESCRIPTION]
- The Problem: [what pain does this niche solve?]
- The Solution: [app description, features, pricing model]
- How to Make Money: [pricing tiers, revenue model]
Output — 5 Sections
Section 1: Demand & Saturation
- Latent Demand Score (1-10) with social listening data
- Market Saturation Index: Blue/Growing/Crowded/Bloodbath
- Subscription Viability: Aspirin vs Vitamin test. Would users pay $9.99/mo?
Section 2: Overtake Strategy
- Competitor Feature Matrix: Top 3 competitors
- 3 table-stakes features you MUST copy
- 2 Blue Ocean Innovations (novel AI/behavioral features incumbents can't copy)
- Killer Differentiation: one sentence — the app's Irresistible Mechanism
Section 3: Revenue & Success Evaluation
- MRR at 5K and 50K paying users (factor 95% Y1 churn)
- Unit Economics: Max CAC, LTV for 6-month breakeven, The Cliff (sub count for profit after 30% fees)
- Freemium Conversion: exact paywall friction point
Section 4: Scaffolding Prompt
- 200-word prompt to generate Full Technical Spec & PRD
- Include: DB schema, subscription logic (RevenueCat/Stripe), Hooked Model triggers, 30-day MVP scope
Section 5: X-Factors
- #1 churn reason + cancellation flow intercept
- Regulatory/Legal risks (GDPR, HIPAA, App Store, FTC)
- Trojan Horse acquisition strategy (no paid ads)
Output Format
Markdown tables for feature comparison. Bold all numbers/percentages. End with: Final Verdict: Build / Pivot / Kill.
Rules
- Be brutal. Assume 70% of startups fail on monetization.
- Do not be optimistic without evidence.
- Every recommendation must cite at least one external source or market signal.
- Mobile apps only. Reject CLI tools, SDKs, desktop-only, SaaS without mobile companion.
- Before scoring, read
references/corrections.md— it documents real failures from prior runs (mobile vs CLI mistake, SEO kill-floor bias, research verification gaps). - Use live web_search — if research fails, flag it rather than inferring silently.
Available scripts
scripts/score.py— Weighted scoring engine with kill-floor elimination. Pipe candidate JSON to it, get ranked results with pass/fail per dimension. Uses 6-dimension framework: market_signal (0.20), competition_gap (0.20), seo_aso (0.20), monetization (0.20), urgency (0.10), mobile_first (0.10 with 6/10 kill floor). Run as:echo '{"candidates":[...]}' | python3 scripts/score.py
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |