command-to-subagent

Convert Ruly commands into subagent-driven execution for heavy API logic.

5|Updated Sep 8, 2025
One-click install
npx skills add https://github.com/patrickclery/ruly --skill command-to-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-to-subagent
Source: https://github.com/patrickclery/ruly/tree/main/.claude/ruly/skills/command-to-subagent
Command: npx skills add https://github.com/patrickclery/ruly --skill command-to-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps separate complex execution logic from user-facing workflows by dispatching to dedicated subagents, reducing recipe context and keeping interfaces clean.

Core Features & Use Cases

  • Isolated execution: Move heavy MCP/API logic into a subagent to keep the command lightweight.
  • Improved token efficiency: By isolating execution, you reduce the working set in the main workflow.
  • Use Case: When a command performs multiple external calls, split the execution into a subagent and have the command orchestrate previews and confirmations.

Quick Start

Instantiate a subagent workflow by converting an existing command to dispatch to a dedicated agent.

Frequently Asked Questions about command-to-subagent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate heavy API logic from my main command workflow?

Subagent dispatch separates complex execution logic from user-facing workflows by routing heavy MCP or API calls to a dedicated subagent. This reduces recipe context and keeps the main command interface lightweight.

What is subagent dispatch used for in command orchestration?

Subagent dispatch is used to isolate heavy command execution logic from user-facing workflows. It separates complex external calls into a dedicated agent, reducing the working set and improving token efficiency in the main workflow.

How do I convert an existing command to dispatch to a subagent?

Converting a command to dispatch to a subagent requires creating a command file, a subagent file, and registering them in recipes. This enables the command to orchestrate previews and confirmations while the subagent handles execution.

When should I move MCP logic into a subagent instead of keeping it inline?

Move MCP logic into a subagent when a command performs multiple external calls and needs to isolate heavy execution logic. This separation reduces the working set in the main workflow and improves token efficiency.

Does isolating command logic improve token efficiency in my workflow?

Isolating command logic into a subagent improves token efficiency by moving heavy MCP or API execution out of the main workflow. This reduces the working set and keeps recipe context clean.

What files do I need to set up subagent dispatch for a command?

Setting up subagent dispatch requires a command file, a subagent file, and a registration in recipes. These components enable dispatch-based execution to isolate heavy API logic from the primary user flow.