Individual skill

orchestration

Decepticon orchestrator patterns — delegation, state management, adaptive re-planning, context handoff protocols.

packages/decepticon/decepticon/skills/standard/decepticon/orchestration/SKILL.md

Read pinned source

Source commit cc6044561ff32188dc0aa899bcc7d3666ffcfd1c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
6,563
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Delegation context and evidence interpretation

A specialist starts with a fresh context. A useful handoff identifies the bounded
question, exact target and permitted actions, acceptance observable, environment,
relevant evidence excerpts and paths, known failed approaches, remaining uncertainty
and budget. Credential references should identify protected artifacts, not repeat
secrets. The live task schema supplies actual field names and available specialists;
examples from another installation do not override it.

## Context quality

Distinguish direct observations, inferred mechanisms and untested assumptions. For a
proof question, include a competing benign explanation and discriminating control.
A code tree, existing reproducer or prior capture may supply enough context without