Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

startup-ideation创业构想

Agent Skill

startup-ideation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

275

周安装

11

GitHub Stars

50

下载量

89
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:startup-ideation(创业构想)
来源仓库:https://github.com/liqiongyu/lenny_skills_plus
仓库路径:skills/startup-ideation
安装命令:
npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill startup-ideation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill startup-ideation

简介

startup-ideation 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 建议结合原始 README 核验具体用法和功能边界。

SKILL.md

Startup Ideation

Scope

Covers

  • Turning vague "startup ideas" into structured opportunity theses
  • Expanding your information diet to find off-the-beaten-path opportunities
  • Running a Why Now analysis based on technology + behavior + distribution shifts
  • Identifying tarpits (ideas that look good but are structurally hard) and pruning early
  • Scoring ideas and producing a top-idea 1‑pager + 2‑week validation plan

When to use

  • "Help me come up with startup ideas in/around."
  • "We have 5 ideas — help us pick one and explain why."
  • "What’s a good *Why Now* for this idea?"
  • "Pressure to do AI — where are real new opportunities?"
  • "How do we avoid idea tarpits and pick something differentiated?"

When NOT to use

  • You already chose an idea and need a delivery-ready PRD (use writing-prds or working-backwards)
  • You need to define the problem space for a specific user pain (use problem-definition)
  • You need to execute research (recruit, interview, synthesize) rather than frame it (use conducting-user-interviews)
  • You need market sizing / pricing / fundraising pitch materials (adjacent work, not covered here)
  • You already have a product but it is stuck or growth stalled and you are considering a direction change (use startup-pivoting)
  • You have a launched product and need to measure whether you have product-market fit (use measuring-product-market-fit)
  • You want to evaluate trade-offs between a small set of known options, not generate new ideas (use evaluating-trade-offs)

Inputs

Minimum required

  • Founder/team context + constraints (time, budget, skills, regulatory constraints)
  • The decision to make + timeline (e.g., "pick 1 idea to validate in the next 2 weeks")
  • Target customer type (B2B/B2C; any preferred industries or segments)
  • Any starting ideas (even rough) + what prompted them

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md.
  • If still missing, proceed with explicit assumptions and list Open questions that could change the recommendation.

Outputs (deliverables)

Produce a Startup Ideation Pack in Markdown (in-chat; or as files if the user requests):

  1. Context snapshot (goal, constraints, decision, timeline)
  2. Unfair advantage + off-the-beaten-path signals (what you know/see that others might not)
  3. Shift scan + Why Now candidates (tech/behavior/distribution/regulatory shifts)
  4. Opportunity theses table (15–30 ideas, each structured + testable)
  5. Tarpit & differentiation check (prune to a shortlist)
  6. Idea scorecard (score top 3–5 with evidence)
  7. Top idea brief (1‑pager) (clear wedge + Why Now + ICP + risks)
  8. 2‑week validation plan (fastest tests for the highest-risk assumptions)
  9. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md Expanded guidance: references/WORKFLOW.md

Workflow (8 steps)

1) Intake + decision framing

  • Inputs: User context; references/INTAKE.md.
  • Actions: Clarify decision, time horizon, and constraints. Define success as "pick 1 idea to validate next" (or similar).
  • Outputs: Context snapshot.
  • Checks: You can restate the decision in one sentence ("We are deciding whether to… by ").

2) Inventory unfair advantage + off-the-beaten-path signals

  • Inputs: Founder/team background; past work; lived experience; access.
  • Actions: List 5–15 unique signals: personal pain, workflows you’ve seen, niche communities, privileged distribution, proprietary data access, or operator insight.
  • Outputs: Unfair advantage + signals list.
  • Checks: Each signal is specific (who/where/when) and could plausibly lead to a differentiated idea.

3) Run a shift scan ("Why now?" raw material)

  • Inputs: Domain + constraints; current trends the user cares about.
  • Actions: Generate 10–20 "shifts" across: technology capability, buyer behavior, regulation, distribution, and cost curves. For each, write: "This enables X that was hard before."
  • Outputs: Shift scan + Why Now candidates.
  • Checks: At least 5 shifts are concrete and falsifiable (not vague hype).

4) Generate opportunity theses (structured ideas)

  • Inputs: Signals + shifts.
  • Actions: Produce 15–30 opportunity theses using the template: *Customer → Job → Pain → Why now → Wedge → First test*.
  • Outputs: Opportunity theses table.
  • Checks: Every idea includes a Why Now statement and a proposed first validation test.

5) Tarpit & differentiation check (prune)

  • Inputs: Opportunity theses table.
  • Actions: Flag tarpits and thinly differentiated ideas. Apply "off-the-beaten-path" pressure: if an idea is widely discussed, require a strong wedge or discard.
  • Outputs: Pruned list + notes on tarpits/differentiation.
  • Checks: The remaining shortlist has at least one concrete advantage (distribution, insight, data, speed, regulatory, workflow depth).

6) Score + shortlist top 3–5

  • Inputs: Pruned list; references/RUBRIC.md.
  • Actions: Score each shortlisted idea with evidence and assumptions. Highlight the 1–2 criteria that dominate the outcome (sensitivity).
  • Outputs: Idea scorecard + top 3–5 recommendation.
  • Checks: Scores cite specific evidence or clearly labeled assumptions (no hand-wavy numbers).

7) Draft the top idea 1‑pager + 2‑week validation plan

  • Inputs: Top idea; references/TEMPLATES.md.
  • Actions: Write a crisp 1‑pager (ICP, problem, Why Now, wedge, GTM motion hypothesis). Then design the fastest validation plan focused on the riskiest assumptions.
  • Outputs: Top idea brief + validation plan.
  • Checks: The plan includes: who to talk to, what to build (if anything), success criteria, and a stop/pivot rule.

8) Quality gate + finalize pack

  • Inputs: Full draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks / Open questions / Next steps.
  • Outputs: Final Startup Ideation Pack.
  • Checks: A stakeholder can review async and decide "validate / park / discard" without a meeting.

Anti-patterns (common failure modes)

  1. Idea brainstorm without structure: Generating a long list of ideas with no Why-Now analysis, no tarpit check, and no scoring. Volume without evaluation is noise, not ideation.
  2. Tarpit blindness: Falling in love with ideas that sound exciting but have well-known structural traps (marketplace cold-start, consumer social network effects, hardware-dependent plays). Always run the tarpit check before shortlisting.
  3. Missing founder-market fit: Evaluating ideas purely on market attractiveness without considering the team’s unfair advantages, domain expertise, or distribution access. An objectively good idea is bad if this team cannot win it.
  4. Vague Why-Now claims: Citing broad trends ("AI is hot", "remote work is growing") without connecting them to a specific enabling shift that makes this idea possible or necessary now vs. two years ago.
  5. Skipping validation design: Producing a polished top-idea brief but no concrete 2-week validation plan, leaving the founder with a thesis but no next action to test it.

Quality gate (required)

Examples

Example 1 (B2B): "We’re ex-operators in logistics. Generate and score startup ideas; pick 1 to validate in 2 weeks." Expected: opportunity theses rooted in real workflows + a shortlist + a top idea 1-pager with a concrete validation plan.

Example 2 (AI shift): "We think new LLM capabilities enable something new in customer support; help us find a differentiated idea and Why Now." Expected: shift scan -> structured theses -> tarpit check -> top idea brief with a tight wedge and clear risks.

Boundary example 1: "Give me 100 startup ideas with no context." Response: ask intake questions first; if the user won’t provide any, produce a small set of generic theses with explicit assumptions and advise on how to ground them in real signals.

Boundary example 2: "Our SaaS product has stalled at 50 customers and we are thinking about changing direction. Help us figure out what to do." Response: this is a pivot decision, not greenfield ideation. Use startup-pivoting to diagnose what is stuck, run an exhaustion check, and evaluate pivot options before generating new ideas.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.95%
按下载量换算30

Claude

31.86%
按下载量换算28

Cursor

18.41%
按下载量换算16

Gemini CLI

8.29%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills