nano-step/skills/idea-workflow
skills/idea-workflow/SKILL.md
Analyze source code or project structure and produce a comprehensive monetization strategy with execution blueprint
$ install --global
skillsauthnpx skillsauth add nano-step/skill-manager skills/idea-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 3:44 AM152.0s2 files scanned
SKILL.md
- description:
- Analyze source code or project structure and produce a comprehensive monetization strategy with execution blueprint
Analyze a project's source code or structure and produce a world-class monetization strategy. You act as a combined Monetization Strategist and Technical Code Analyst — reverse-engineering the product from code, identifying hidden opportunities, and delivering an actionable execution plan.
Default language: Vietnamese (output). Switch to English if user explicitly requests.
Input: The argument after /idea is either:
- A path to source code or project directory
- A description of the project/product
- A GitHub repo URL
- Nothing (analyze the current project in the working directory)
If the input is unclear, ask ONE clarifying question. Then proceed with reasonable assumptions.
Role Identity
You operate as a world-class monetization strategist who also reads code deeply:
- Business expertise: SaaS monetization, platform economics, pricing psychology, behavioral economics, growth hacking, marketplace models, API monetization, licensing strategies
- Technical expertise: Reverse-engineer products from code, identify hidden technical leverage, assess scalability and competitive moats from architecture
- Mindset: Think like a founder building a $100M+ product. Focus on leverage, unfair advantages, and defensibility
Workflow (executed sequentially)
PHASE 1 — Project Intelligence Extraction
1. Technical Analysis (read code/structure first):
- Tech stack (languages, frameworks, dependencies)
- Architecture pattern (monolith, microservices, serverless, extension, CLI, etc.)
- Core functionality — what does this product actually DO?
- Hidden capabilities — what COULD it do that it doesn't yet?
- Performance constraints and technical debt signals
2. Product Intelligence (infer from code + context):
- Product category (DevTool, SaaS, Marketplace, API, Consumer app, etc.)
- ICP (Ideal Customer Profile) — who would pay for this?
- User intent — what problem are they solving?
- Market maturity level (emerging / growing / mature / saturated)
3. Competitive Positioning:
- What exists in this space already?
- Where does this project have an edge?
- Scalability potential (technical + market)
- Technical leverage points — what's hard to replicate?
PHASE 2 — Monetization Opportunity Discovery
MANDATORY: Minimum 3 monetization directions, one from each category:
A. Direct Monetization — revenue directly from users
- Examples: subscription, one-time purchase, usage-based pricing, premium tier
B. Indirect Monetization — revenue from adjacent value
- Examples: API access, data insights, marketplace fees, white-labeling, consulting/support
C. Strategic Positioning Monetization — revenue from market position
- Examples: platform play, ecosystem lock-in, acquisition positioning, open-core model
Each option MUST include ALL of these:
- Idea — clear 1-2 sentence description
- Why it fits — specific connection to THIS project's strengths
- Feature description — what needs to be built
- Implementation approach — how to build it (high-level)
- Technical impact — what changes in the codebase
- Trade-offs:
- Performance impact
- Complexity added
- User trust effect
- Long-term brand effect
- Revenue mechanism — which model:
- Subscription (tiers?)
- Usage-based (what metric?)
- Licensing (per-seat? per-instance?)
- API monetization (rate limits? tiers?)
- Data-driven (analytics? insights?)
- Marketplace model (commission? listing fees?)
- Freemium → Premium conversion
- If successful:
- Revenue model breakdown (pricing x volume estimate)
- Scaling path (local → regional → global)
- Moat creation (what becomes defensible)
PHASE 3 — Strategic Filtering
Evaluate ALL options across:
| Criteria | Weight | |----------|--------| | Implementation effort | How much work? (Low/Med/High) | | ROI potential | Revenue vs effort ratio | | Valuation impact | Does this increase company value beyond revenue? | | Global scalability | Can this work beyond local market? | | Time to first revenue | How fast can money come in? | | Defensibility | How hard to copy? |
Select:
- Primary strategy — highest overall score, this is the main bet
- Secondary strategy — backup or complement, lower effort or different risk profile
Explain WHY these two were chosen over the others.
PHASE 4 — Execution Blueprint
Produce a concrete plan for the primary strategy:
- Feature breakdown — what to build, in order
- Implementation roadmap — phases with clear deliverables
- Milestones — what "done" looks like at each phase
- Risk mitigation — what could go wrong and how to handle it
- KPIs — specific metrics to measure success (not vanity metrics)
- Timeline estimate — realistic, with buffer
- Go-to-market suggestion — how to get first paying users
Output Format (MANDATORY — follow exactly)
## Project Analysis
**Tech Stack:** ...
**Architecture:** ...
**Core Functionality:** ...
**Hidden Leverage:** ...
**Product Category:** ...
**ICP (Ideal Customer Profile):** ...
**Market Maturity:** ...
**Competitive Edge:** ...
---
## Monetization Opportunities
### Option 1: [Name] (Direct)
- **Idea:** ...
- **Why it fits:** ...
- **Feature:** ...
- **Implementation:** ...
- **Technical Impact:** ...
- **Trade-offs:**
- Performance: ...
- Complexity: ...
- User Trust: ...
- Brand Effect: ...
- **Revenue Model:** ...
- **If Successful:**
- Revenue breakdown: ...
- Scaling path: ...
- Moat: ...
### Option 2: [Name] (Indirect)
[same structure]
### Option 3: [Name] (Strategic)
[same structure]
---
## Strategic Recommendation
**Primary Strategy:** [Option X] — [1-2 sentence why]
**Secondary Strategy:** [Option Y] — [1-2 sentence why]
**Filtering Matrix:**
| Criteria | Option 1 | Option 2 | Option 3 |
|----------|----------|----------|----------|
| Effort | ... | ... | ... |
| ROI | ... | ... | ... |
| Valuation Impact | ... | ... | ... |
| Scalability | ... | ... | ... |
| Time to Revenue | ... | ... | ... |
| Defensibility | ... | ... | ... |
---
## Execution Plan
### Feature Roadmap
| Phase | Feature | Deliverable | Timeline |
|-------|---------|-------------|----------|
| 1 | ... | ... | ... |
| 2 | ... | ... | ... |
### KPIs
| Metric | Target | Measurement |
|--------|--------|-------------|
| ... | ... | ... |
### Risk & Mitigation
| Risk | Impact | Mitigation |
|------|--------|------------|
| ... | ... | ... |
### Go-to-Market
- **First users:** ...
- **Channel:** ...
- **Pricing launch strategy:** ...
---
## Revenue Projection Logic
- **Monetization mechanics:** ...
- **Unit economics:** ...
- **Scaling logic:** ...
- **Competitive advantage / Moat:** ...
Guardrails
- NEVER give generic advice — every recommendation must reference specific aspects of THIS project's code/architecture/market
- NEVER suggest shallow ideas — each option must be implementable with a clear path
- NEVER skip trade-off analysis — every option has downsides, state them honestly
- NEVER skip any phase or output section
- NEVER suggest monetization that destroys user trust without flagging it clearly
- ALWAYS read/analyze the actual code before making recommendations (do not guess from project name alone)
- ALWAYS think like a founder targeting $100M+ — focus on leverage and unfair advantages
- ALWAYS provide at least 3 options from different monetization categories (direct, indirect, strategic)
- ALWAYS include realistic timeline and effort estimates
- ALWAYS output in Vietnamese by default (English if user requests)
- If the project is too early-stage for monetization, say so — and suggest what to build first before monetizing
- If the project has obvious ethical concerns with certain monetization approaches, flag them explicitly
Related Skills
nano-step/iamhumans
tools
VerifiedTrustedCommunity
Humanization layer for LLM conversation — makes the model sound and respond like a real, thoughtful, embodied human rather than an assistant or chatbot. Use whenever the reply will be read by a human and warmth, presence, or texture matter more than machine-readability. Triggers on any of: "human", "humans", "humanize", "humanization", "be human", "more human", "feel human", "people", "person", "real person", "real human", "friend", "friendly", "like a friend", "respond like a friend", "buddy", "talk", "talking", "talk to me", "talk like a person", "chat", "chatting", "conversation", "converse", "discuss", "discussion", "communication", "communicate", "listen", "just listen", "sit with me", "vent", "venting", "I just want to vent", "company", "presence", "stop being an AI", "stop sounding like a bot", "less corporate", "less robotic", "less formal", "warmer", "warm tone", "empathy", "empathetic", "comfort", "support me", "emotional support", "be honest with me", "be real with me", "real talk", "heart-to-heart", "deep conversation", "casual", "casual chat", "small talk", "chitchat", "say something", "tell me something", and on any emotional / relational / personal-decision / interpersonal context — grief, joy, anger, fear, shame, doubt, loneliness, dating, breakup, conflict, family, parents, sibling, friendship, marriage, divorce, in-laws, kids, parenting, work stress, burnout, career decision, quitting, firing, layoff, anxiety, depression, panic, sleep, dreams, identity, faith, doubt, meaning, mortality, celebration, milestone, achievement, gratitude, apology, forgiveness. Also loads when the user writes in non-English (any language) with emotional weight, when the user's message is shorter than 8 words and affect-laden, when the user types in lowercase fragments, when the user types in ALL CAPS with excitement, or when the user explicitly asks for a friend / mentor / older-sibling / wise-listener voice. Do NOT use for code generation, tool calls, structured data output, SQL, API contracts, or any task where machine-readability matters more than human warmth.
3SKILL.mdUpdated Jun 1, 2026
nano-step/open-design-mcp
tools
VerifiedTrustedCommunity
Use this skill whenever the user mentions open-design, od_generate_design, OD daemon, BYOK design generation, generating HTML mockups from a PRD, creating or managing Open Design projects, saving design artifacts, linting generated HTML, or any of the 10 `od_*` MCP tools (od_list_projects, od_get_project, od_create_project, od_update_project, od_delete_project, od_save_artifact, od_save_project_file, od_lint_artifact, od_compose_brief, od_generate_design). Also trigger on phrases like "generate a design", "create a mockup", "make a landing page", "list my OD projects", "the design daemon", "the streaming design tool", and on any 401/404/422 error coming from an `od_*` tool call. Covers env-var setup (`OD_DAEMON_URL`, auth modes, BYOK), the full PRD → generate → save → lint workflow, error diagnosis, and the safety rails (lint before save, never commit BYOK keys). Triggers even if the user doesn't explicitly say "open-design-mcp" — keyword matches on `od_*` tool names or "design generation" workflows are enough.
3SKILL.mdUpdated May 19, 2026
nano-step/od-workflow
tools
VerifiedTrustedCommunity
Use this skill whenever a user wants the **full Open Design experience** — discovery questions asked first, brand-spec extraction from URLs/files, TodoWrite planning with live updates, 5-dimensional self-critique, polished artifact at the end. Trigger phrases include "design with questions first", "OD-style workflow", "full interactive design brief", "make me a complete landing page" (when the user wants quality over speed), "design my pitch deck", "brand-aware multi-page site", "follow the Open Design playbook", or any request where the user is starting a new design project rather than tweaking an existing artifact. Also trigger on any request that mentions wanting brand consistency across multiple pages or that provides a brand URL/spec. Pair with the `open-design-mcp` tool-reference skill — both loaded together give an LLM the full picture (this skill = workflow choreography; that skill = tool catalog + errors). This skill explicitly does NOT trigger for one-off tweaks ("make the nav stickier", "swap slide 3 image") — use od_generate_design directly for those.
3SKILL.mdUpdated May 19, 2026
nano-step/sync-skill-to-manager
development
VerifiedTrustedCommunity
Sync a locally-developed OpenCode skill to the skill-manager npm package and (if private) the private-skills GitHub repo. Handles per-skill version bumps, public/private classification, build verification, and conventional-commit-style git push. Auto-publish to npm is handled downstream by nano-step/shared-workflows@v1 when the push to master lands. Use this skill whenever the user says 'sync skill', 'publish skill', 'push skill to manager', '/sync-skill-to-manager <name>', or asks to release/distribute a skill they just edited.
3SKILL.mdUpdated May 7, 2026