Menu
Clarify requirements before implementing. Use when requests have multiple interpretations or key details are unclear. Prevents wasted work on wrong assumptions.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Create a content calendar for the month
Master storytelling frameworks, video scripts (15s/30s/60s), social media captions, segment-specific messaging, and persuasive CTAs. Turn product features into emotional stories that convert across different audience segments.
Create a compelling job description
Marketing multi-agent orchestration system for complex, parallelizable campaigns. Coordinates specialized AI agents for: (1) Research + synthesis + content creation pipelines, (2) Platform-specific content generation at scale (Reddit, LinkedIn, Twitter, Email), (3) Lead generation and outbound campaigns, (4) Human-in-the-loop review before any external execution, (5) Automated posting with natural timing patterns. Triggers: "build me a marketing team", "orchestrate agents", "outbound campaign", "multi-platform content", "lead generation system", "social media blitz", or any request implying coordinated marketing specialist work.
Define and align organization around a single North Star Metric (NSM) that captures product value, drives growth, and focuses team efforts. Framework for choosing NSM by product type (social, marketplace, SaaS, content) with input metrics breakdown.
Set up, optimize, and scale paid social campaigns on Meta (Facebook/Instagram), Google Ads, and TikTok. Master test budgets, creative testing, audience targeting, funnel metrics, and budget scaling strategies for maximum ROAS.
| name | ask-questions |
| description | Clarify requirements before implementing. Use when requests have multiple interpretations or key details are unclear. Prevents wasted work on wrong assumptions. |
Use this skill when a request has multiple plausible interpretations or key details (objective, scope, constraints, environment, or safety) are unclear.
Do not use this skill when the request is already clear, or when a quick, low-risk discovery read can answer the missing details.
Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions).
Treat a request as underspecified if after exploring how to perform the work, some or all of the following are not clear:
If multiple plausible interpretations exist, assume it is underspecified.
Ask 1-5 questions in the first pass. Prefer questions that eliminate whole branches of work.
Make questions easy to answer:
defaults to accept all recommended/default choices)1b 2a 3c); restate the chosen options in plain language to confirmUntil must-have answers arrive:
If the user explicitly asks you to proceed without answers:
Once you have answers, restate the requirements in 1-3 sentences (including key constraints and what success looks like), then start work.
1) Scope?
a) Minimal change (default)
b) Refactor while touching the area
c) Not sure - use default
2) Compatibility target?
a) Current project defaults (default)
b) Also support older versions: <specify>
c) Not sure - use default
Reply with: defaults (or 1a 2a)
Request: "Add authentication to the app"
Underspecified: Yes - many interpretations possible
Questions:
Before I add authentication, I need to clarify:
1) Authentication method?
a) Email + password (default)
b) OAuth (Google/GitHub)
c) Both
d) Not sure - use default
2) User management?
a) Local database (default)
b) Third-party service (Auth0, Firebase, etc.)
c) Not sure - use default
3) Protected routes?
a) Just /dashboard and /profile
b) Everything except homepage
c) I'll tell you which ones
d) Not sure - protect /dashboard and /profile
Reply with: defaults (or 1b 2a 3c)
Request: "Fix the slow API endpoint"
Underspecified: Yes - need to know which endpoint, what "slow" means, constraints
Questions:
To fix the slow API, I need:
1) Which endpoint is slow? (e.g., /api/users, /api/products)
2) What's "slow" mean?
a) Taking > 1 second (default)
b) Taking > 5 seconds
c) Timing out
d) User complaint without specific metric
3) Any constraints?
a) Can change database queries (default)
b) Database schema is locked
c) Must maintain backward compatibility
d) Not sure - use default
Reply with endpoint name and: defaults (or 2c 3b)
Request: "Refactor the user service"
Underspecified: Yes - scope and goals unclear
Questions:
Before refactoring, I need to understand:
1) Goal?
a) Improve testability (default)
b) Improve performance
c) Add new features
d) Simplify code
e) Multiple goals (specify)
2) Scope?
a) User service only (default)
b) User service + dependent services
c) Entire auth system
d) Not sure - user service only
3) Can I change interfaces?
a) Yes, internal refactoring only (default)
b) Yes, but maintain backward compatibility
c) No, interfaces must stay exactly the same
d) Not sure - use default
Reply with: defaults (or 1d 2b 3b)
This skill works well before:
Attribution: Based on "ask-questions-if-underspecified" from Trail of Bits Skills License: CC-BY-SA-4.0 Adapted for: Claude Starter Kit by Sunny Patneedi and Contributors