/idea-validator
Orchestrates business idea validation via parallel sub-agents: Lean Canvas, JTBD, market/competitive/feasibility research, SWOT/PESTLE, and a weighted scorecard with verdict. Triggers on: "validate this idea", "evaluate my startup idea", "is this idea worth pursuing", "score
$ npx -y skills add Mathews-Tom/armory --skill idea-validator --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/idea-validator
Context preview
The summary Claude sees to decide when to auto-load this skill.
Orchestrates business idea validation via parallel sub-agents: Lean Canvas, JTBD, market/competitive/feasibility research, SWOT/PESTLE, and a weighted scorecard with verdict. Triggers on: "validate this idea", "evaluate my startup idea", "is this idea worth pursuing", "score
SKILL.md
idea-validator.SKILL.mdname: idea-validator
description: 'Orchestrates business idea validation via parallel sub-agents: Lean Canvas, JTBD, market/competitive/feasibility research, SWOT/PESTLE, and a weighted scorecard with verdict. Triggers on: "validate this idea", "evaluate my startup idea", "is this idea worth pursuing", "score this business idea", "validate my pitch".'
metadata:
version: 1.0.1
complements: [market-analyzer, competitive-analyzer, feasibility-assessor]
category: review
tags: [idea-validation, lean-canvas, jtbd, swot]
difficulty: advanced
phase: define
Business Idea Validator
Purpose
Perform rigorous, multi-dimensional validation of business ideas by orchestrating parallel research and synthesizing findings into a scored, actionable report. The goal is honest assessment — surfacing what holds up under scrutiny and what does not — rather than cheerleading or reflexive dismissal.
Phase 1: Input Intake & Classification
Classify the input:
| Input Type | Indicators | Adaptation | | ---------------- | ------------------------------------------- | ------------------------------------------- | | Elevator pitch | 1-3 sentences, informal | Extract hypothesis, ask for missing details | | Business plan | Structured, multiple sections | Validate claims against research | | Feature proposal | Technical focus, existing product context | Narrow scope to feature viability | | Repo/codebase | File paths, code references | Technical feasibility + market fit | | Pivot assessment | "Should we pivot to...", comparison context | Compare current vs proposed direction |
Extract core elements from the input:
- **Problem statement** — what pain point exists
- **Proposed solution** — how it addresses the pain
- **Target customer** — who experiences this problem
- **Value proposition** — why this solution over alternatives
- **Revenue model** — how it generates money
If any core element is missing or ambiguous, ask clarifying questions. Cap at 5 questions. Do not proceed with fabricated assumptions for missing elements — get real answers.
Phase 2: Lean Canvas Construction
Build a complete Lean Canvas using `references/lean-canvas.md` as the framework guide.
Populate all 9 boxes:
1. **Problem** — top 3 problems the customer faces 2. **Customer Segments** — target market + early adopter profile 3. **Unique Value Proposition** — single clear compelling message 4. **Solution** — top 3 features addressing the top 3 problems 5. **Channels** — path to reaching customers 6. **Revenue Streams** — pricing model and revenue mechanics 7. **Cost Structure** — fixed and variable costs 8. **Key Metrics** — what to measure for progress 9. **Unfair Advantage** — what cannot be easily copied or bought
For each box:
- Assess completeness and specificity
- Flag vague entries ("everyone" as a segment, "best product" as UVP)
- Check cross-box coherence (solution must address stated problems, channels must reach stated segments)
Phase 3: Jobs-to-be-Done Analysis
Apply the JTBD framework from `references/jtbd-framework.md`:
- **Functional job** — what is the customer trying to accomplish?
- **Emotional job** — how do they want to feel?
- **Social job** — how do they want to be perceived?
- **Current solutions** — what do they use today? (hiring/firing decisions)
- **Switching triggers** — what would cause adoption of a new solution?
Assess whether the proposed solution addresses the core job better than current alternatives. Identify the four forces of progress: push of current situation, pull of new solution, anxiety of change, habit of status quo.
Phase 4: Parallel Research Delegation
Use the Agent tool to spawn three research agents in parallel. Each agent receives a focused research brief derived from the idea context established in Phases 1-3. These agents perform the same analysis covered by the complementary skills (`market-analyzer`, `competitive-analyzer`, `feasibility-assessor`) — when those skills are installed, their reference frameworks inform the analysis depth; when running standalone, the agents use the inline briefs below.
Agent 1 — Market Research
Prompt the agent:
> Analyze the market opportunity for [idea summary with target customer and problem context]. Research TAM/SAM/SOM estimates, market growth trends, customer segment sizing, and timing signals. Use WebSearch to find industry reports, market data, analyst projections, and trend indicators. Produce a structured market analysis with quantified estimates and cited sources. Include: market size estimates with methodology, growth rate and trajectory, key market drivers, timing assessment (too early, right time, too late), and customer willingness to pay signals.
Agent 2 — Competitive Analysis
Prompt the agent:
> Analyze the competitive landscape for [idea summary with solution and value proposition context]. Discover direct competitors (same solution, same customer), indirect competitors (different solution, same job-to-be-done), and potential competitors (adjacent players who could enter). Compare features, pricing, and positioning across competitors. Assess Porter's Five Forces for this industry. Identify moats and defensibility factors. Use WebSearch for competitor data from Product Hunt, G2, Capterra, Crunchbase, and company sites. Produce a structured competitive analysis with competitor matrix, force scores, and positioning assessment.
Agent 3 — Feasibility Assessment
Prompt the agent:
> Assess the financial and technical feasibility of [idea summary with solution details and revenue model]. Calculate unit economics using industry benchmarks: customer acquisition cost (CAC), lifetime value (LTV), LTV:CAC ratio, gross margins, payback period. Evaluate technical complexity: architecture requirements, key technical risks, bui
Read more
name: idea-validator description: 'Orchestrates business idea validation via parallel sub-agents: Lean Canvas, JTBD, market/competitive/feasibility research, SWOT/PESTLE, and a weighted scorecard with verdict. Triggers on: "validate this idea", "evaluate my startup idea", "is this idea worth pursuing", "score this business idea", "validate my pitch".' metadata: version: 1.0.1 complements: [market-analyzer, competitive-analyzer, feasibility-assessor] category: review tags: [idea-validation, lean-canvas, jtbd, swot] difficulty: advanced phase: define
Business Idea Validator
Purpose
Perform rigorous, multi-dimensional validation of business ideas by orchestrating parallel research and synthesizing findings into a scored, actionable report. The goal is honest assessment — surfacing what holds up under scrutiny and what does not — rather than cheerleading or reflexive dismissal.
Phase 1: Input Intake & Classification
Classify the input:
| Input Type | Indicators | Adaptation | | ---------------- | ------------------------------------------- | ------------------------------------------- | | Elevator pitch | 1-3 sentences, informal | Extract hypothesis, ask for missing details | | Business plan | Structured, multiple sections | Validate claims against research | | Feature proposal | Technical focus, existing product context | Narrow scope to feature viability | | Repo/codebase | File paths, code references | Technical feasibility + market fit | | Pivot assessment | "Should we pivot to...", comparison context | Compare current vs proposed direction |
Extract core elements from the input:
- **Problem statement** — what pain point exists
- **Proposed solution** — how it addresses the pain
- **Target customer** — who experiences this problem
- **Value proposition** — why this solution over alternatives
- **Revenue model** — how it generates money
If any core element is missing or ambiguous, ask clarifying questions. Cap at 5 questions. Do not proceed with fabricated assumptions for missing elements — get real answers.
Phase 2: Lean Canvas Construction
Build a complete Lean Canvas using `references/lean-canvas.md` as the framework guide.
Populate all 9 boxes:
1. **Problem** — top 3 problems the customer faces 2. **Customer Segments** — target market + early adopter profile 3. **Unique Value Proposition** — single clear compelling message 4. **Solution** — top 3 features addressing the top 3 problems 5. **Channels** — path to reaching customers 6. **Revenue Streams** — pricing model and revenue mechanics 7. **Cost Structure** — fixed and variable costs 8. **Key Metrics** — what to measure for progress 9. **Unfair Advantage** — what cannot be easily copied or bought
For each box:
- Assess completeness and specificity
- Flag vague entries ("everyone" as a segment, "best product" as UVP)
- Check cross-box coherence (solution must address stated problems, channels must reach stated segments)
Phase 3: Jobs-to-be-Done Analysis
Apply the JTBD framework from `references/jtbd-framework.md`:
- **Functional job** — what is the customer trying to accomplish?
- **Emotional job** — how do they want to feel?
- **Social job** — how do they want to be perceived?
- **Current solutions** — what do they use today? (hiring/firing decisions)
- **Switching triggers** — what would cause adoption of a new solution?
Assess whether the proposed solution addresses the core job better than current alternatives. Identify the four forces of progress: push of current situation, pull of new solution, anxiety of change, habit of status quo.
Phase 4: Parallel Research Delegation
Use the Agent tool to spawn three research agents in parallel. Each agent receives a focused research brief derived from the idea context established in Phases 1-3. These agents perform the same analysis covered by the complementary skills (`market-analyzer`, `competitive-analyzer`, `feasibility-assessor`) — when those skills are installed, their reference frameworks inform the analysis depth; when running standalone, the agents use the inline briefs below.
Agent 1 — Market Research
Prompt the agent:
> Analyze the market opportunity for [idea summary with target customer and problem context]. Research TAM/SAM/SOM estimates, market growth trends, customer segment sizing, and timing signals. Use WebSearch to find industry reports, market data, analyst projections, and trend indicators. Produce a structured market analysis with quantified estimates and cited sources. Include: market size estimates with methodology, growth rate and trajectory, key market drivers, timing assessment (too early, right time, too late), and customer willingness to pay signals.
Agent 2 — Competitive Analysis
Prompt the agent:
> Analyze the competitive landscape for [idea summary with solution and value proposition context]. Discover direct competitors (same solution, same customer), indirect competitors (different solution, same job-to-be-done), and potential competitors (adjacent players who could enter). Compare features, pricing, and positioning across competitors. Assess Porter's Five Forces for this industry. Identify moats and defensibility factors. Use WebSearch for competitor data from Product Hunt, G2, Capterra, Crunchbase, and company sites. Produce a structured competitive analysis with competitor matrix, force scores, and positioning assessment.
Agent 3 — Feasibility Assessment
Prompt the agent:
> Assess the financial and technical feasibility of [idea summary with solution details and revenue model]. Calculate unit economics using industry benchmarks: customer acquisition cost (CAC), lifetime value (LTV), LTV:CAC ratio, gross margins, payback period. Evaluate technical complexity: architecture requirements, key technical risks, bui
Curated, production-grade skills, agents, hooks, rules, commands, utilities, and presets for AI coding agents. No magic, no demos — battle-tested workflows built for developers who use AI seriously.
Repo: Mathews-Tom/armory
Other skills on armory.
- /adr-writer
Generates Architecture Decision Records capturing context, rationale, alternatives, and consequences in numbered status-tracked format. Triggers on: "write an ADR", "document this decision", "architecture decision record", "decision record", "design decision", "ADR for".
Open skill - /agent-builder
Build AI agents and automate Claude Code programmatically via the Claude Agent SDK and headless CLI mode. Covers Python SDK, claude -p, SDK MCP servers, hooks, sessions. Triggers on: "build an agent", "agent SDK", "headless mode", "automate Claude", "programmatic agent".
Open skill - /api-docs-generator
Audits and enhances FastAPI and REST API documentation: missing descriptions, response codes, examples, docstrings, Pydantic models, OpenAPI spec. Triggers on: "generate API docs", "document this API", "OpenAPI for", "FastAPI docs", "document endpoints", "swagger docs".
Open skill - /architecture-diagram
Generate layered architecture diagrams as self-contained HTML with inline SVG icons, CSS Grid containers, and connection overlays. Triggers on: "architecture diagram", "infra diagram", "system diagram", "deployment diagram", "topology", "draw architecture". NOT for architecture
Open skill - /architecture-reviewer
Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports. Triggers on: "review architecture", "critique design", "audit system", "assess scalability", "enterprise readiness", "technical due
Open skill - /arxiv-figures
Optimize and prepare figures for arXiv submission: format conversion (EPS/PDF/PNG/JPG), size reduction, metadata stripping, processor compatibility (DVI vs PDFLaTeX). Triggers on: "optimize figures for arXiv", "reduce figure size", "convert figures for arXiv", "fix arXiv
Open skill

