From business-idea-eval
For ideas that involve a physical product, sketch a bill of materials, identify the hardest engineering risks, propose feasibility tests, and estimate prototyping cost. Only use when the idea has a hardware component — skip for pure-software ideas.
How this skill is triggered — by the user, by Claude, or both
Slash command
/business-idea-eval:hardware-feasibilityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Hardware ideas die on three rocks: BOM cost at volume, regulatory / certification, and manufacturing tolerance. Surface them early.
Hardware ideas die on three rocks: BOM cost at volume, regulatory / certification, and manufacturing tolerance. Surface them early.
<workspace_path>/ideas/<slug>/analysis/hardware-feasibility.md with frontmatter:
---
lens: hardware-feasibility
generated: YYYY-MM-DD
bom_estimate_v1_usd: <number>
hardest_risk: <one-line>
---
npx claudepluginhub danielrosehill/claude-code-plugins --plugin business-idea-evalProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.