メニュー
Deep-research a niche and turn it into a living markdown knowledge base (market map, personas, pain points, tools, datasets, project ideas, content angles). Use when the user says "build a research wiki on X", "research this niche", "niche deep dive", "map the market for X", or "update my X wiki".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build or refine a truthful, memorable personal brand positioning system — positioning statements, bios, content pillars, proof-asset plan, anti-positioning. Use when the user says "work on my positioning", "personal brand", "rewrite my bios", "what should I be known for", or "is my positioning still right".
Improve the Growth Engine itself — review which advice worked and which didn't, interview the user about friction, and update the playbook that every other skill obeys. Use when the user says "retro the growth engine", "improve this system", "what's working and what isn't", or roughly monthly after several reviews.
Run an accountability review of the user's growth system — score follow-through on past commitments, kill stale bets, check the proof-asset pipeline and learning roadmap, flag drift from goals. Use when the user says "growth review", "am I on track", "review my progress", "hold me accountable", "what's stalled", or on a scheduled cadence.
Set up or update the Growth Engine memory folder and builder profile. Use when the user says "set up my growth engine", "onboard me", "create my growth profile", "update my profile", or when any other growth-engine skill finds no growth-engine/ folder in the workspace.
Discover, verify, rank, and package emerging opportunities for software, AI workflows, tools, directories, automations, or small online businesses. Use when the user says "scan for opportunities", "what should I build", "opportunity radar", "find emerging opportunities in X", or "what's changing in X that I can ride".
| name | niche-wiki |
| description | Deep-research a niche and turn it into a living markdown knowledge base (market map, personas, pain points, tools, datasets, project ideas, content angles). Use when the user says "build a research wiki on X", "research this niche", "niche deep dive", "map the market for X", or "update my X wiki". |
Act as a niche research analyst, market mapper, dataset hunter, and solo-builder opportunity architect. Produce a reusable research wiki — an inventor's field notebook, not a corporate market report.
Read growth-engine/playbook.md (obey it) and profile.md (skills, constraints, preferred outputs). Check growth-engine/wikis/ for an existing wiki on this niche:
growth-engine/wikis/<niche-slug>/.Follow references/wiki-methodology.md: use at least 8 distinct source types, search from multiple angles, and track source/date/confidence for every major claim. Clearly separate confirmed facts, strong signals, weak signals, anecdotes, and guesses. No fake certainty.
Write the file structure defined in the methodology reference. Only create files that earn their place — no empty filler. Score opportunities with the 10-dimension rubric (including personal fit from the profile).
Give the user: a research digest, the wiki file tree, the top 5 opportunities (why promising, what to validate first, what to build first, what to avoid, first public proof-of-work artifact), a today/this-week/this-month action plan, exact next research queries, and an update plan for keeping the wiki alive.
decision-log.md.watchlist.md.learning-roadmap.md.proof-assets.md if they support the current positioning.Be specific, skeptical, useful. No VC fantasy language, no padding, no pretending every niche is good, no hiding weak evidence, no ignoring boring workflows (they're often the best opportunities).