sub-agent
Delegate a self-contained task to a sub-Agent (Codex, Claude Code, or Pi via background process). The original use case was coding tasks — building features, reviewing PRs, refactoring — but the skill is the generic "spawn a sub-Agent with full tool surface" slot used by meta-skill DAG steps for any LLM-driven sub-task (policy review, trace parsing, report synthesis, document generation). Renamed from ``coding-agent`` to reflect actual usage; the wrapped CLIs (codex / claude / pi) still bias toward coding workloads. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn
npx skills add opensquilla/opensquilla --skill sub-agent --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sub-Agent (opensquilla process tools) Generic "spawn a sub-Agent" entry point for delegating self-contained tasks to Codex / Claude Code / OpenCode / Pi via background process. Wrapping CLIs are coding-oriented, but the skill itself is used as the generic sub-Agent slot by meta-skill DAGs for any LLM-driven sub-task (file edits, document generation, policy review, etc.). Use opensquilla's `exec_command`, `background_process`, and `process` tools for coding agent work. OpenSquilla does not expose a `bash` tool; do not use the legacy bash tool-call DSL. ## Non-Interactive CLI Mode OpenSquilla's process tools do not expose a `pty` parameter. Prefer non-interactive command modes that run and exit cleanly: ```bash # ✅ Correct for Codex/Pi/OpenCode exec_command(command="codex exec 'Your prompt'") ``` For **Claude Code** (`claude` CLI), use `--print --permission-mode bypassPermissions` instead. `--dangerously-skip-permissions` with PTY can exit after the confirmation dialog. `--print` mode keeps full tool access and avoids interactive confirmation: ```bash # ✅ Correct for Claude Code (no PTY needed) cd /path/to/project && claude --permission-mode bypassPermissions --print 'Your task' #
- Non-Interactive CLI Mode
- OpenSquilla Tool Parameters
- Process Tool Actions (for background sessions)
- Quick Start: One-Shot Tasks
- The Pattern: workdir + backgroundprocess
- Codex CLI
- Flags
- Building/Creating
- Reviewing PRs
- Batch PR Reviews (parallel army!)
- Claude Code
- OpenCode
- Pi Coding Agent
- Parallel Issue Fixing with git worktrees
cd /path/to/project && claude --permission-mode bypassPermissions --print 'Your task' For background execution: use background_process Quick chat (Codex needs a git repo!) Or in a real project Start agent in target directory. Returns session_id for tracking Wait for it to finish — blocks until the process exits (or the timeout Peek at output without blocking (optional, for progress) Send input (if agent asks a question) Submit with Enter (like typing "yes" and pressing Enter)
What does the sub-agent skill do?
Delegate a self-contained task to a sub-Agent (Codex, Claude Code, or Pi via background process). The original use case was coding tasks — building features, reviewing PRs, refactoring — but the skill is the generic "spawn a sub-Agent with full tool surface" slot used by meta-skill DAG steps for any LLM-driven sub-task (policy review, trace parsing, report synthesis, document generation). Renamed from ``coding-agent`` to reflect actual usage; the wrapped CLIs (codex / claude / pi) still bias toward coding workloads. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill sub-agent --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.