skills/consiliency/spawn/agent/SKILL.md
Spawn an AI coding agent in a new terminal (Claude, Codex, Gemini, Cursor, OpenCode, Copilot). Defaults to Claude Code if unspecified.
npx skillsauth add aiskillstore/marketplace spawn-agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Spawn an AI coding agent in a new terminal window. Follow the 'Instructions', execute the 'Workflow', based on the 'Cookbook'.
| Variable | Default | Description | |----------|---------|-------------| | DEFAULT_AGENT | claude-code | Agent to use when not explicitly specified | | ENABLED_CLAUDE_CLI | true | Enable Claude Code agent | | ENABLED_CODEX_CLI | true | Enable OpenAI Codex agent | | ENABLED_GEMINI_CLI | true | Enable Google Gemini agent | | ENABLED_CURSOR_CLI | true | Enable Cursor agent | | ENABLED_OPEN_CODE_CLI | true | Enable OpenCode agent | | ENABLED_COPILOT_CLI | true | Enable GitHub Copilot agent | | LOG_TO_FILE | false | Write full terminal output to debug file | | LOG_AGENT_OUTPUT | true | Write clean agent JSON response to file | | READ_CAPTURED_OUTPUT | false | Read and display agent output after spawn | | AGENTIC_CODING_TOOLS | claude-code, codex-cli, gemini-cli, cursor-cli, opencode-cli, copilot-cli | Available agentic tools |
MANDATORY - You MUST follow the Workflow steps below in order. Do not skip steps.
If you're about to:
STOP -> Read the appropriate cookbook file -> Follow its instructions -> Then proceed
Common Mistake: When spawning agentic CLIs (Claude, Codex, Gemini) with a prompt, most require command chaining (e.g.,
&& claude --continue) to stay in interactive mode after the prompt completes. Always check the cookbook for the correct pattern.
Next User Request field.MANDATORY CHECKPOINTS - Verify each before proceeding:
The fork_terminal() function supports three output controls:
| Parameter | Default | Output File | Description |
|-----------|---------|-------------|-------------|
| log_agent_output | True | /tmp/fork-agent-*.json | Clean agent JSON response |
| log_to_file | False | /tmp/fork-debug-*.txt | Full terminal output (debug) |
| capture | False | N/A | Block and return content directly |
| capture | log_agent_output | log_to_file | Behavior |
|-----------|-------------------|---------------|----------|
| False | True (default) | False | Returns agent JSON file path |
| False | False | True | Returns debug file path |
| False | False | False | Returns empty string |
| True | True | * | Blocks, returns agent JSON content |
| True | False | True | Blocks, returns debug content |
When log_agent_output=True (default), clean agent output is logged. Use read_fork_output(file_path) to retrieve it:
# Spawn without blocking (returns path to JSON output)
file_path = fork_terminal(cmd, log_agent_output=True)
print(f"Agent output will be at: {file_path}")
# Later, read the output when needed
output = read_fork_output(file_path, timeout=60)
For debugging, enable log_to_file=True to capture full terminal output (including stderr):
# Debug mode: capture everything
file_path = fork_terminal(cmd, log_to_file=True, log_agent_output=False)
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.