ask-clarifying-questions
Ask Clarifying Questions
Drive a structured interview to surface load-bearing assumptions before any code is written. Use the agent's interactive question tool when available. The "output" is shared understanding in the current session — no file artifact is produced.
When to Use
- The user invokes
/ask-clarifying-questionsexplicitly. - The user names
ask-clarifying-questionsin a Codex session. - The user asks to build a feature, refactor, or design something and the brief is short or leaves room for meaningfully different implementations.
- Skip when: the request is mechanical (typo fix, obvious rename, a one-line bug fix the user has already diagnosed). Cheap requests don't earn an interview — clarification has its own cost.
Process
1. Anchor
Restate in one sentence what you understand the user wants. This anchors the interview and gives the user a chance to redirect cheaply.
2. Ask up to 4 questions per round, ranked by load-bearing-ness
More from usetemi/skills
google-drive
Manage Google Drive files with manifest-tracked push/pull workflows via rclone. Use when the user needs to download, upload, list, or manage files on Google Drive shared drives.
22google-search-console
Query Google Search Console analytics, inspect URL indexing status, manage sitemaps, and run PageSpeed Insights audits. Use when the user needs SEO data, search performance reports, indexing diagnostics, or Core Web Vitals analysis.
15google-analytics
Query GA4 reports (users, sessions, conversions, funnels, realtime), manage properties / data streams / key events / custom dimensions / audiences / access bindings, and send Measurement Protocol events via the `ga4` CLI. Use this skill whenever the user mentions GA4, Google Analytics, property IDs starting with `properties/`, tracking events, engagement or traffic metrics, attribution, conversions, key events, audiences, BigQuery links, access roles, or realtime users — even if they don't explicitly say "GA4". Do not use for Google Search Console (see google-search-console skill) or generic web analytics where the source isn't GA4 (ask first).
14template-skill
Replace with a clear description of what this skill does and when Claude should use it. Be specific about trigger words and use cases.
14humanize
Remove signs of AI-generated writing from text. Use when editing, reviewing, or rewriting prose to make it sound natural and human-written, or when the user says "humanize this", "make this sound human", "remove AI-isms", "this sounds AI-generated", or invokes /humanize. Based on Wikipedia's "Signs of AI writing" guide. Detects and fixes 29 patterns including inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, copula avoidance, passive voice, negative parallelisms, sycophantic tone, and filler phrases.
2pdf
Fill, redline, and generate PDFs with the right tool for the source. Detects AcroForm vs flat PDFs, handles AES-encrypted government forms, navigates appearance-stream gotchas, and verifies every output by rendering. Use when the user asks to fill a PDF form, redline a PDF, generate a PDF from markdown, or reproduce a packet of forms. PDF-only — DOCX, XLSX, and other formats are out of scope.
2