Delegating to Confluence Agent

Delegate Confluence wiki read, update, create, search, and list operations to a sub-agent.

34|5|Updated Oct 15, 2025

Search Tags:#automation #workflow #delegation #wiki #confluence #sub-agent #cost-savings

Ready to run

npx skills add https://github.com/ryancnelson/deli-gator --skill delegating-to-confluence-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Delegating to Confluence Agent
Source: https://github.com/ryancnelson/deli-gator/tree/main/examples/2-documentation-wiki/skills/delegating-to-wiki-agent
Command: npx skills add https://github.com/ryancnelson/deli-gator --skill delegating-to-confluence-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill teaches you how to delegate Acme Confluence wiki operations to a specialized sub-agent, keeping your main assistant context clean and focused, which reduces cognitive load and token usage.

Core Features & Use Cases

Automatic delegation: Recognizes wiki-related requests and hands off to a cheaper sub-agent.
Operational guardrails: Ensures sensitive API details stay hidden from the main assistant.
Cost efficiency: Significantly lowers main-context usage by routing Confluence tasks to the sub-agent.

Quick Start

Example: Delegate a wiki-read operation by invoking the sub-agent using AGENT-INSTRUCTIONS.md content, for instance: "wiki-read 123456789" via the Task tool and present the formatted result to the user.

Frequently Asked Questions about Delegating to Confluence Agent

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

FAQPage Schema

How do I delegate Confluence wiki operations to reduce token usage in my main assistant?▼

Delegating Confluence operations to a specialized sub-agent keeps your main assistant context clean and focused, significantly lowering token consumption. The sub-agent handles read, update, create, search, and list tasks for wiki pages while your main context stays uncluttered.

Can I automate Confluence wiki tasks like creating and updating pages without exposing API tokens?▼

Yes. The delegation workflow routes wiki operations through a sub-agent using shell wrappers (wiki-read, wiki-update, wiki-create, wiki-search, wiki-list-space) that prevent token and internal API detail exposure while automating page creation, updates, searches, and content management.

What wiki operations can I delegate to a sub-agent, and which spaces do they cover?▼

The sub-agent handles read, update, create, search, and list operations for pages in the OPS/DevOPS space, including reading page content, updating existing pages, creating new pages, performing searches, and listing space contents through a three-step workflow.

How does delegating wiki operations reduce costs compared to handling Confluence tasks in the main assistant?▼

Routing Confluence tasks to a cheaper sub-agent significantly lowers main-context usage and token consumption. The sub-agent processes wiki operations independently, freeing your main assistant's expensive context for higher-value reasoning.

Do I need special configuration to start delegating Confluence wiki tasks to a sub-agent?▼

No special prerequisites are required. The workflow uses provided agent instructions and the Task tool to invoke the sub-agent, then present results. Shell wrappers handle the operational details and prevent API exposure automatically.