sub-agent-call

Creates a nested pi sub-agent in a persistent thread for delegated tasks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/junkijin/my-pi --skill sub-agent-call
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sub-agent-call
Source: https://github.com/junkijin/my-pi/tree/main/skills/sub-agent-call
Command: npx skills add https://github.com/junkijin/my-pi --skill sub-agent-call

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Invokes a nested pi CLI session as a persistent sub-agent thread to obtain second opinions, provider/model comparison, repository inspection, or continued follow-up. Use when the user wants to consult another agent/model, compare providers, or continue a focused sub-agent conversation from pi. By default, reuse the current session's provider and model unless the user explicitly asks for a different one.

Core Features & Use Cases

  • Delegate a narrowly scoped task to a nested pi session within a persistent thread.
  • Compare providers/models or perform repository inspection via a sub-agent.
  • Maintain continuity by reusing the current provider/model unless the user requests explicit override.

Quick Start

Start a first sub-agent call with a prompt and optionally attach a small context file.

Frequently Asked Questions about sub-agent-call

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

FAQPage Schema
How do I delegate a sub-agent task to compare AI providers within the same session?

You can delegate a sub-agent task by invoking a nested pi session in a persistent thread. This allows you to compare providers or models while reusing your current session configuration unless you explicitly request an override.

Can I consult another model for a second opinion without losing my current workflow context?

Yes, you can consult another model for a second opinion by spawning a sub-agent in a persistent thread. It integrates your current context and maintains continuity without disrupting your primary workflow.

How do I start a focused sub-agent conversation from an existing pi thread?

Start a focused sub-agent conversation by running the wrapper script with a specific prompt and optional context file. This initiates a nested pi session that runs parallel to your main thread.

Does a sub-agent automatically use the same provider and model as my main session?

Yes, the sub-agent defaults to reusing the current provider and model from your active session. You can override this behavior by explicitly specifying a different provider or model for the sub-agent.

What are the limitations of using a persistent sub-agent thread for repository inspection?

The persistent sub-agent thread is designed for narrowly scoped tasks like repository inspection. Complex or overly broad tasks may exceed the focused context integration limits of the nested pi session.

Do I need any external dependencies to run a nested pi sub-agent?

No external dependencies are required to run a nested pi sub-agent. The Skill implements a self-contained wrapper script with built-in thread management and prompt handling.