Token导航 LogoToken导航

Agent Skill · 研究检索

discovery-question-generator(发现问题生成器)

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

discovery-question-generator 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 52,043。

总安装 564周安装 24GitHub Stars 73下载 198核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:discovery-question-generator(发现问题生成器)
来源仓库:https://github.com/zanecole10/software-tailor-skills
仓库路径:skills/discovery-question-generator
安装命令:
npx skills add https://github.com/zanecole10/software-tailor-skills --skill discovery-question-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/zanecole10/software-tailor-skills --skill discovery-question-generator

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

discovery-question-generator 针对特定行业生成高价值痛点问题集,助力挖掘可商业化解决的场景。输入企业类型即可输出分类问题库,覆盖工作流程、技术栈缺口与预算授权等维度。适用于早期创业团队验证市场假设,或顾问开展客户诊断前的快速破冰。

生成的内容需二次验证,避免将推测性结论误作事实陈述影响商业判断。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/discovery-question-generator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/zanecole10/software-tailor-skills --skill disc…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

discovery-question-generator 怎么安装?

在终端执行 npx skills add https://github.com/zanecole10/software-tailor-skills --skill discovery-ques…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

discovery-question-generator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

discovery-question-generator 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

discovery-question-generator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

discovery-question-generator 用的人多吗?

公开数据是累计安装 564 次,近一周安装 24 次,下载 198 次,GitHub 73 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

discovery-question-generator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
discovery-question-generator

发现问题生成器 · 本页

56473只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Discovery Question Generator

Uncover the real problems businesses are willing to pay $15K+ to solve.

What This Skill Does

You input a business type (dentist, gym, contractor, restaurant, etc.), and this skill generates 30-50 strategic discovery questions organized by category to help you:

✅ Uncover Hidden Pain Points - Find problems they didn't know could be solved ✅ Understand Current Workflows - Map their actual daily operations ✅ Identify Tech Stack Gaps - Discover what tools they're struggling with ✅ Quantify Cost of Problem - Calculate hours wasted, revenue lost ✅ Qualify Budget & Authority - Ensure they can afford and approve $15K+ ✅ Build Trust & Credibility - Sound like an expert who understands their business

Who This Is For

Software Tailors who need to:

  • Conduct effective discovery calls with potential clients
  • Find the $15K opportunities hidden in "we need help with scheduling"
  • Ask questions that reveal the real problem, not surface symptoms
  • Qualify whether a lead is worth pursuing
  • Position themselves as strategic advisors, not just code monkeys

How To Use This Skill

Input Format

Simply provide:

  1. Business Type - Industry or niche (e.g., "fire inspection company", "personal training gym", "dental practice")
  2. Optional Context - Any specific pain points you already know about

Example Input:

Business Type: Fire inspection company
Context: They mentioned they're using Excel to track inspections and losing track of which buildings are due for reinspection.

Output Format

The skill generates organized question sets like this:


Discovery Questions for: Fire Inspection Company

Category 1: Current Workflow & Pain Points (10-12 questions)

Purpose: Understand their day-to-day operations and identify friction points

  1. Walk me through a typical day for one of your inspectors from start to finish.

- *Why this works:* Gets them narrating their workflow naturally, revealing inefficiencies they've normalized

  1. How do you currently assign inspections to your field team?

- *Listen for:* Manual processes, phone calls, group chats, spreadsheet updates

  1. What happens when an inspector arrives on-site? What's their first step?

- *Listen for:* Paper forms, tablet confusion, missing information

  1. How long does it typically take an inspector to complete an inspection report after finishing on-site?

- *Listen for:* "2-3 hours of paperwork", "they do it at home after dinner"

  1. Tell me about the last time something went wrong with an inspection - what happened?

- *Listen for:* Missed inspections, lost paperwork, angry clients

  1. How do you know which buildings are due for their next inspection?

- *Listen for:* "We check Excel every Monday", "Sometimes we forget and clients call us"

  1. What's your process when a client calls asking for their inspection report?

- *Listen for:* Time wasted searching files, inconsistent report formats

  1. How many hours per week would you estimate your team spends on paperwork vs. actual inspections?

- *Listen for:* Shocking ratios like 30% admin work

  1. What do your inspectors complain about most?

- *Listen for:* Real frustrations from the people doing the work

  1. If you could wave a magic wand and fix one thing about how inspections are managed, what would it be?

- *Listen for:* Their dream solution - often reveals the highest-value feature

Category 2: Data & Documentation (8-10 questions)

Purpose: Understand how they store, access, and share information

  1. Where do you currently store completed inspection reports?

- *Listen for:* Dropbox folders, email attachments, physical filing cabinets

  1. How do clients receive their inspection reports?

- *Listen for:* Email PDFs manually, clients have to call and request them

  1. Can you pull up a report from 6 months ago in less than 2 minutes right now?

- *Listen for:* "Uh, probably not" = pain point

  1. Do you track inspection history for each building? How?

- *Listen for:* Excel, handwritten notes, "we try to remember"

  1. What information do you need to reference from past inspections when scheduling new ones?

- *Listen for:* Data relationships they need but don't have

  1. How do you handle photos from inspections?

- *Listen for:* Inspector cell phones, lost photos, inconsistent formats

  1. Have you ever had a compliance audit? How hard was it to pull together the required documentation?

- *Listen for:* Panic, scrambling, "took us 3 days"

  1. Do multiple people need access to the same inspection data?

- *Listen for:* Collaboration needs, permission requirements

Category 3: Scheduling & Operations (8-10 questions)

Purpose: Identify bottlenecks in planning and coordination

  1. How far in advance do you typically schedule inspections?

- *Listen for:* Chaos vs. planning, reactive vs. proactive

  1. What happens when an inspector calls in sick and has 5 inspections scheduled?

- *Listen for:* Panic, manual rescheduling nightmare

  1. How do you balance emergency inspections vs. routine scheduled ones?

- *Listen for:* Prioritization chaos

  1. Do you ever have inspectors driving across town multiple times because inspections weren't grouped by location?

- *Listen for:* Wasted drive time, fuel costs

  1. How much time does your office staff spend on the phone scheduling and rescheduling inspections?

- *Listen for:* Quantifiable hours = cost savings justification

  1. Can your inspectors see their schedule from their phone?

- *Listen for:* "No, we text them every morning" = opportunity

  1. How do you know if an inspection is running late or was completed early?

- *Listen for:* Lack of real-time visibility

  1. What's your process for annual re-inspections? How do you remember which buildings need them?

- *Listen for:* Manual tracking, missed revenue opportunities

Category 4: Client Communication (6-8 questions)

Purpose: Discover customer service pain points

  1. How often do clients call asking about inspection status or reports?

- *Listen for:* Frequent interruptions = opportunity for client portal

  1. What do clients complain about most regarding your service?

- *Listen for:* Slow reports, lack of transparency, hard to schedule

  1. How do you notify clients when their inspection is complete?

- *Listen for:* Manual phone calls/emails = automation opportunity

  1. Do clients ever need to reschedule? How does that process work?

- *Listen for:* Back-and-forth phone tag

  1. Have you ever lost a client because of administrative issues (not the quality of inspections)?

- *Listen for:* Revenue lost due to poor process = ROI justification

Category 5: Growth & Scalability (6-8 questions)

Purpose: Understand if current process blocks growth

  1. How many inspections do you currently handle per month?

- *Listen for:* Baseline volume

  1. If you wanted to double your inspection volume, what would break first in your current system?

- *Listen for:* Scalability concerns

  1. Have you turned down work because you couldn't handle the volume?

- *Listen for:* Lost revenue = massive opportunity cost

  1. How many inspectors do you have? Do you plan to hire more?

- *Listen for:* Growth plans = urgent need for better systems

  1. What prevents you from taking on more clients right now?

- *Listen for:* Administrative bottlenecks, not inspection capacity

  1. If you had better systems, how much more revenue could you realistically generate per year?

- *Listen for:* ROI numbers for your pitch

Category 6: Budget & Decision Making (5-7 questions)

Purpose: Qualify if they can afford and approve $15K+ solution

  1. What's your annual revenue, roughly?

- *Listen for:* Size of business = ability to invest

  1. Have you invested in custom software or tools for your business before?

- *Listen for:* Comfort with technology investment

  1. What do you currently spend on software/tools per month?

- *Listen for:* Existing budget for solutions

  1. If I could show you a solution that saves your team 15 hours per week, what would that be worth to you?

- *Listen for:* Value-based thinking vs. cost-based thinking

  1. Who else would need to approve a decision like this?

- *Listen for:* Decision-making authority, multiple stakeholders

  1. What would need to be true for you to invest in a custom solution in the next 30-60 days?

- *Listen for:* Urgency, readiness to buy

  1. If you don't fix this problem, what happens in 6 months?

- *Listen for:* Cost of inaction = urgency

Category 7: Technical Environment (4-6 questions)

Purpose: Understand their current tech stack and constraints

  1. What devices do your inspectors use in the field? (iPhones, Android, tablets?)

- *Listen for:* Technical requirements

  1. Do you have a company website? Who manages it?

- *Listen for:* Technical comfort level

  1. Are there any systems you need this to integrate with? (QuickBooks, Stripe, etc.)

- *Listen for:* Integration requirements

  1. How tech-savvy is your team? Do they pick up new tools easily?

- *Listen for:* User experience priorities

  1. Do you have any compliance requirements for data storage or security?

- *Listen for:* Regulatory constraints

Category 8: Vision & Desired Outcomes (3-5 questions)

Purpose: Understand their ideal future state

  1. If we build this perfectly, what does success look like 6 months from now?

- *Listen for:* Concrete metrics (hours saved, revenue increased)

  1. What would your inspectors say if this worked exactly as you hoped?

- *Listen for:* User satisfaction goals

  1. What's the one metric you'd track to know this was worth the investment?

- *Listen for:* How they'll measure ROI


How to Use These Questions

During the Discovery Call

Don't ask all 50 questions - That's overwhelming. Instead:

  1. Start with Workflow questions (Category 1) to get them talking naturally
  2. Follow the conversation - Let their answers guide which categories to explore
  3. Dig deeper when they mention pain points: "Tell me more about that", "How often does that happen?"
  4. Listen for emotion - Frustration, anger, stress = expensive problems they'll pay to solve
  5. Quantify everything - "How many hours?", "How much does that cost?", "How often?"

Red Flags (Questions that disqualify prospects)

  • Annual revenue under $500K → Likely can't afford $15K
  • "We need this to be under $2K" → Wrong budget expectation
  • "I need to think about it for a few months" → No urgency
  • "We're just exploring options" → Tire-kicker, not ready to buy

Green Flags (Questions that indicate ready buyers)

  • "How soon can you start?" → Urgency
  • "What if we wanted to add [feature]?" → Thinking about expansion
  • "We're currently wasting 20 hours a week on this" → Quantified pain
  • "I can make this decision myself" → Authority

Question Frameworks

The Time Waste Question

"How many hours per week does your team spend on [manual process]?"

  • Reveals cost of problem
  • Creates urgency
  • Builds ROI justification

The Magic Wand Question

"If you could wave a magic wand and fix one thing, what would it be?"

  • Gets to core desire
  • Reveals highest-value feature
  • Opens up dream scenario conversation

The Failure Story Question

"Tell me about the last time [process] went wrong. What happened?"

  • Gets emotional response
  • Reveals real-world consequences
  • Creates fear of inaction

The Growth Blocker Question

"If you wanted to double your business, what would break first?"

  • Reveals scalability needs
  • Creates vision of future growth
  • Justifies investment now

The Cost of Inaction Question

"If you don't solve this problem, what happens in 6 months?"

  • Creates urgency
  • Reveals true cost
  • Motivates decision

Adapting Questions to Different Industries

This skill generates industry-specific questions, but the underlying frameworks apply across all businesses:

Service Businesses (HVAC, Plumbing, Inspections)

  • Focus on: Scheduling, dispatch, route optimization, client communication

Retail/Inventory (Shops, Warehouses)

  • Focus on: Inventory tracking, supplier management, sales reporting

Professional Services (Law, Accounting, Consulting)

  • Focus on: Client management, time tracking, document organization

Healthcare (Clinics, Physical Therapy)

  • Focus on: Patient scheduling, records management, billing

Construction/Trades (Contractors, Builders)

  • Focus on: Job tracking, material management, crew scheduling

Best Practices

DO:

  • ✅ Ask open-ended questions that get them talking
  • ✅ Listen more than you talk (80/20 rule)
  • ✅ Take detailed notes on pain points
  • ✅ Quantify everything in hours and dollars
  • ✅ Ask "Why?" and "Tell me more" to dig deeper
  • ✅ Let silence happen - don't fill every pause

DON'T:

  • ❌ Pitch solutions before understanding the problem
  • ❌ Ask yes/no questions - they shut down conversation
  • ❌ Lead the witness ("Wouldn't it be great if...")
  • ❌ Skip budget qualification questions
  • ❌ Assume you understand without asking

After the Discovery Call

Synthesize Findings

  1. List top 3-5 pain points they mentioned
  2. Calculate cost of problems (hours × hourly rate)
  3. Identify must-have features vs. nice-to-haves
  4. Draft software blueprint using the Business Problem to Blueprint skill
  5. Prepare proposal with ROI calculation

Follow-Up

Send a summary email:

  • Thank them for their time
  • Recap the problems you heard
  • Preview your solution approach
  • Schedule next call to present proposal

Remember

The goal of discovery questions isn't to interrogate - it's to understand their world deeply so you can build software that solves their real problems. The best software tailors ask questions that make prospects say: "Wow, you really get our business."

Good questions lead to great software. Great software gets $15K+ price tags.

平台分布

Codex

37.01%
按下载量换算73

Claude

28.39%
按下载量换算56

Cursor

17.5%
按下载量换算35

Gemini CLI

9.28%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills