Skill

orchestration-context

Compaction and handoff rules for multi-agent orchestration. Use when a lead orchestrator or teammate needs to manage context pressure, compact their context window, or write a handoff note before compacting.

From agent-orchestrator
Install
1
Run in your terminal
$
npx claudepluginhub l3digitalnet/claude-code-plugins --plugin agent-orchestrator
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Orchestration — Context Budget Management

Lead Orchestrator

  • Compact after every wave; always after 2+ waves
  • Write handoff to .claude/state/lead-handoff.md BEFORE compacting
  • Compact instruction: Preserve: orchestration plan, team roster, current wave, file ownership map, all ledger entries, blocker status
  • After compaction, immediately read your handoff note

Teammates

  • Compact every 3 tasks, or after 10+ file reads (the read-counter hook will warn you)
  • Write handoff to .claude/state/<your-name>-handoff.md BEFORE compacting
  • Compact instruction: Preserve: my tasks, file ownership, decisions from my handoff note
  • After compaction, immediately read your handoff note

Subagents

  • Disposable — no compaction needed
  • Return structured results only (use the scan/integration templates in orchestration-state)
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars3
Parent Repo Forks0
Last CommitFeb 19, 2026