subask_skill

Overview

This skill forwards a focused question to a sub-agent so you can get an answer without polluting the main session. It preserves the main conversation context, reduces token usage, and keeps your primary task flow uninterrupted. The sub-agent runs independently and returns its reply directly to the main session.

How this skill works

You invoke the skill with "/subask <question>". The skill validates input, launches a sub-agent task with parameters (model, type, and a prompt that includes the current working directory), and returns the sub-agent's output unchanged. By default it uses a low-cost, fast model and a general-purpose sub-agent; flags change model and behavior.

When to use it

• Ask brief diversion questions during a longer session without losing context
• Get quick technical clarifications or conceptual summaries
• Request filesystem or git actions localized to the current working directory
• Avoid increasing token consumption in the main conversation
• Run small experimental queries that should not affect session memory

Best practices

• Keep questions concise to get focused responses from the sub-agent
• Use --detailed for deeper explanations or when you need thorough guidance
• Use --explore when the answer must inspect the repository or files
• Avoid relying on sub-agent replies for critical state changes unless you verify them
• Include explicit scope if you expect file or git operations (e.g., mention the target directory)

Example use cases

• Quickly compare two technologies: "/subask REST and GraphQL differences"
• Ask for coding patterns: "/subask Go error handling patterns"
• Request a repository-aware action: "/subask --explore list files in this directory"
• Get a short conceptual explanation: "/subask Explain asyncio vs threading"
• Commit changes in current directory: "/subask Commit changes"