socratic
A questioning protocol for gathering information before taking action. Use this when you need to understand requirements, validate assumptions, or clarify intent before proceeding.
What this skill does
# Socratic Questioning Protocol ## When to Use Apply this protocol BEFORE taking any significant action: - Before creating plans - Before removing/simplifying - Before making design decisions - Whenever you're unsure about user intent ## The Process ### Step 1: Identify What You Need to Know Before asking, think: - What assumptions am I making? - What's ambiguous about this request? - What could go wrong if I misunderstand? ### Step 2: Ask Questions in Batches Use the AskUserQuestion tool. Ask 2-3 related questions per round. **Question Types:** - **Clarifying** - "What do you mean by X?" - **Probing assumptions** - "You mentioned X, are you assuming Y?" - **Exploring rationale** - "Why is this important? What problem does it solve?" - **Testing boundaries** - "What's out of scope? What should this NOT do?" - **Validating understanding** - "So if I understand correctly, you want X?" ### Step 3: Adapt Based on Answers - Vague answer -> Probe deeper - New information revealed -> Explore that thread - Contradiction detected -> Point it out, ask for clarification - Clear answer -> Move to next question area ### Step 4: Confirm Before Proceeding Before moving to your core work, summarize: - "Here's what I understand: [summary]" - "Is there anything else I should know before I proceed?" If user says "yes, also..." -> Ask more questions about that If user confirms -> Proceed to your core work ## Rules 1. **Never assume** - If something is unclear, ask 2. **Never stop prematurely** - Let the user decide when there's enough context 3. **Always confirm** - Summarize understanding before acting 4. **Batch questions** - 2-3 per round, not one-by-one 5. **Adapt** - Follow interesting threads, don't stick rigidly to a script 6. **Hand back control** - If you run out of questions, ask "anything else?" rather than just stopping
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.