dot_claude/skills/trend-arbitrage/SKILL.md
End-to-end workflow for finding content, app, service, or product opportunities where search demand is high but quality supply is low (trend arbitrage). Use when: finding content gaps, keyword opportunities, niche research, analyzing whether a topic or idea is worth pursuing, or competitive gap analysis.
npx skillsauth add paveg/dots trend-arbitrageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Find "Volume: High / Difficulty: Low" gaps in any market and turn them into actionable content or product strategies. Based on the methodology of identifying demand-supply mismatches before competitors notice them.
Trend Arbitrage = Finding topics where search demand is growing but quality supply is scarce.
Three conditions must ALL be true:
Before starting any phase, use ask_user_input to classify the opportunity type unless
the user has already made it clear. This determines which discovery methods, validation
criteria, and strategy templates to use.
Always ask upfront:
What type of gap are you looking for?
What market or niche? (free text if not already specified)
What's your time horizon?
The answers shape every subsequent phase — discovery sources, validation criteria, strategy templates, and execution plans all differ by type.
The skill operates in 4 phases. Run them sequentially or jump to any phase.
CLASSIFY → Phase 1: DISCOVER → Phase 2: VALIDATE → Phase 3: STRATEGIZE → Phase 4: EXECUTE
(Ask type) (Find signals) (Confirm the gap) (Design the play) (Create the plan)
Read references/phases.md for the detailed procedure of each phase.
Goal: Generate a list of 5-10 candidate opportunities showing breakout signals.
Inputs: Determined by classification above. If anything is ambiguous, ask via ask_user_input.
Methods by type (use web_search for all):
Output: A ranked table of candidates:
| # | Opportunity | Type | Signal Source | Trend Direction | Initial Assessment |
|---|-------------|------|--------------|-----------------|-------------------|
| 1 | ... | App | ... | ↑↑ Breakout | Promising |
Goal: For top 3 candidates from Phase 1, produce a quantified gap score.
Validation criteria shift by opportunity type:
Demand Score (1-5): Based on search volume and community interest Supply Score (1-5, inverted): Based on quality/freshness of existing content Intent Score (1-5): From casual browsing (1) to purchase-ready (5)
Demand Score (1-5): Based on how many people are asking for this tool, workaround complexity Supply Score (1-5, inverted): Based on existing tools' quality, UX, and pricing gaps Feasibility Score (1-5): Can the user realistically build this? (replaces Intent for apps)
Demand Score (1-5): Based on hiring posts, freelancer marketplace activity, complaint volume Supply Score (1-5, inverted): Based on existing service providers' quality, speed, pricing Margin Score (1-5): Is the willingness-to-pay high enough for sustainable solo delivery?
Demand Score (1-5): Based on how often people search for / ask about this resource Supply Score (1-5, inverted): Does a good version of this product already exist? Packaging Score (1-5): How easily can scattered information be packaged into a sellable unit?
Arbitrage Score = Metric1 × Metric2 × Metric3 (max 125)
Produce a validation report. Read references/validation-template.md for the format.
Thresholds:
Goal: For each GO topic, create a concrete strategy.
Determine the optimal format based on the gap type:
| Gap Type | Best Format | Example | |----------|-------------|---------| | No comprehensive guide exists | Long-form article/guide | "Complete Guide to X" | | Info is scattered across forums | Curated resource list | "Internet Pipes" style | | Existing tools are too complex | Simple tool/template | PhotoAI model | | No localized version exists | Localized adaptation | JapanDrop-style newsletter | | Information changes frequently | Newsletter/subscription | Milk Road model | | People need ongoing help | Community or service | Designjoy model |
Strategy output must include:
Goal: Produce a concrete, time-boxed execution plan the user can start today.
Output a week-by-week plan:
Week 1: Foundation
Week 2-3: Creation
Week 4: Launch & Measure
If the user's project context is known (e.g., JapanDrop, Tuck), tailor the execution plan to fit their existing infrastructure and tech stack.
Quick scan: User says "find opportunities in [niche]" → Classify, then run Phase 1 only Full analysis: User says "analyze [specific topic/idea]" → Classify, then run Phase 2 + 3 End-to-end: User says "find and plan a new project" → Classify, then run all 4 phases Validation only: User says "is [topic/app idea] worth pursuing?" → Classify, then Phase 2 only Recon: User says "what gaps exist in [market]?" → Classify all 4 types, run Phase 1 across types
references/phases.md — Detailed procedures for each phasereferences/validation-template.md — Gap validation report templatereferences/examples.md — Real-world arbitrage case studies for pattern matchingdevelopment
Iteratively improve agent-facing text instructions (skills, slash commands, task prompts, CLAUDE.md sections, code-generation prompts) by having a bias-free executor run them and evaluating from both sides (executor self-report + caller-side metrics). Repeat until improvement plateaus. Use immediately after creating or significantly revising a skill/prompt, or when unexpected agent behavior is suspected to stem from ambiguous instructions.
development
UI design quality standards and principles for frontend implementation and code review. Use when (1) implementing UI from design specs or mockups, (2) reviewing frontend/UI code, (3) creating new UI components, (4) building user interfaces for web or mobile apps. Complements frontend-design skills with quality enforcement.
development
Pre-submission review for iOS App Store. Scans the codebase for common rejection reasons and generates a pass/fail report with fixes. Use this skill when the user mentions App Store submission, review, release, 審査, 提出, or phrases like "ready to submit", "before submitting to Apple", "submission review", "rejection check". Also trigger when the user is preparing a TestFlight build for external review or discussing App Store rejection issues. Supports Swift/SwiftUI, UIKit, and React Native projects with Apple IAP and RevenueCat.
data-ai
Delegate an interrupt task to a background agent in an isolated worktree. The main session continues uninterrupted. The agent implements, commits, pushes, and creates a PR. Use when a quick fix or small task needs to happen without losing current context.