Delegating to CDN Agent

Delegation to CDN Agent routes Fastly queries—service management, backend inspection, VCL configuration, and cache purging—to a specialized sub-agent, keeping your primary AI focused and reducing token overhead. The sub-agent handles fastly-cli commands and returns clean results without exposing raw API calls.

Yes. The Skill delegates cache purge actions to a sub-agent that executes purge commands by service, key, or URL, with built-in warnings for critical operations. Requests mentioning purge or cache triggers automatic delegation.

The Skill handles listing and describing Fastly services, viewing configured backends, inspecting VCL configurations, and executing cache purge actions. It triggers on mentions of fastly, cdn, vcl, backends, purge, or related domains.

Fastly API details bloat context, increase token costs, and reduce focus on core tasks. Delegation to a specialized sub-agent isolates CDN complexity, preserves main AI efficiency, and delivers formatted results cleanly.

Yes. The Skill depends on fastly-cli. The sub-agent uses it to execute service listing, backend inspection, VCL retrieval, and cache purge operations against your Fastly account.

The Skill routes purge requests to a sub-agent with built-in warnings for critical operations. Results are formatted and returned without exposing internal commands, balancing automation safety with clean output.