Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Lightweight session execution skill. Resumes existing team-coordinate sessions for pure execution via team-worker agents. No analysis, no role generation -- only loads and executes. Session path required. Triggers on "Team Executor".
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 357% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 97% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 195% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 13% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 15% | 0% |
Lightweight session execution skill: load session -> reconcile state -> spawn team-worker agents -> execute -> deliver. No analysis, no role generation -- only executes existing team-coordinate sessions.
+---------------------------------------------------+
| Skill(skill="team-executor") |
| args="--session=<path>" [REQUIRED] |
+-------------------+-------------------------------+
| Session Validation
+---- --session valid? ----+
| NO | YES
v v
Error immediately Orchestration Mode
(no session) -> executor
|
+-------+-------+-------+
v v v v
[team-worker agents loaded from session role-specs]CRITICAL: Session validation MUST occur before any execution.
Extract from $ARGUMENTS:
--session=<path>: Path to team-coordinate session folder (REQUIRED)--session provided:team-session.json exists and valid JSONtask-analysis.json exists and valid JSONrole-specs/ directory has at least one .md fileteam-session.json#roles has corresponding .md file in role-specs/This skill is executor-only. Workers do NOT invoke this skill -- they are spawned as team-worker agents directly.
| Scenario | Action | |----------|--------| | No --session | ERROR immediately | | --session invalid | ERROR with specific reason | | Valid session | Orchestration Mode -> executor |
Invocation: Skill(skill="team-executor", args="--session=<session-folder>")
Lifecycle:
Validate session
-> executor Phase 0: Reconcile state (reset interrupted, detect orphans)
-> executor Phase 1: Spawn first batch team-worker agents (background) -> STOP
-> Worker executes -> callback -> executor advances next step
-> Loop until pipeline complete -> Phase 2 report + completion actionUser Commands (wake paused executor):
| Command | Action | |---------|--------| | check / status | Output execution status graph, no advancement | | resume / continue | Check worker states, advance next step |
| Role | File | Type | |------|------|------| | executor | roles/executor/role.md | built-in orchestrator | | (dynamic) | <session>/role-specs/<role-name>.md | loaded from session |
When executor spawns workers, use team-worker agent with role-spec path:
spawn_agent({
agent_type: "team_worker",
task_name: "<task-id>",
fork_turns: "none",
message: `## Role Assignment
role: <role>
role_spec: <session-folder>/role-specs/<role>.md
session: <session-folder>
session_id: <session-id>
requirement: <task-description>
inner_loop: <true|false>
Read role_spec file to load Phase 2-4 domain instructions.
## Task Context
task_id: <task-id>
title: <task-title>
description: <task-description>
pipeline_phase: <pipeline-phase>
## Upstream Context
<prev_context>`
})After spawning, use wait_agent({ timeout_ms: 1800000 }) to collect results. If result.timed_out, send STATUS_CHECK via followup_task (wait 3 min), then FINALIZE with interrupt (wait 3 min), then mark timed_out and close agents. Use close_agent({ target: <name> }) each worker.
team-executor loads roles dynamically from session role-specs. Use reasoning_effort based on the role type defined in the session:
reasoning_effort: "high"reasoning_effort: "medium"reasoning_effort: "high"On resume, executor reconciles session state with actual running agents:
const running = list_agents({})
// Compare with session's task-analysis.json active tasks
// Reset orphaned tasks (in_progress but agent gone) to pendingsend_message({ target: "<task-id>", message: "..." }) -- queue supplementary contextfollowup_task({ target: "<task-id>", message: "..." }) -- assign new work to inner_loop workerclose_agent({ target: "<task-id>" }) -- cleanup completed workerWhen pipeline completes (all tasks done), executor presents an interactive choice:
functions.request_user_input({
questions: [{
question: "Team pipeline complete. What would you like to do?",
header: "Completion",
multiSelect: false,
options: [
{ label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
{ label: "Keep Active", description: "Keep session for follow-up work" },
{ label: "Export Results", description: "Export deliverables to target directory, then clean" }
]
}]
})| Choice | Steps | |--------|-------| | Archive & Clean | Update session status="completed" -> output final summary with artifact paths | | Keep Active | Update session status="paused" -> output: "Resume with: Skill(skill='team-executor', args='--session=<path>')" | | Export Results | functions.request_user_input(target path) -> copy artifacts to target -> Archive & Clean |
| Scenario | Skill | |----------|-------| | New task, no session | team-coordinate | | Existing session, resume execution | team-executor | | Session needs new roles | team-coordinate (with resume) | | Pure execution, no analysis | team-executor |
| Scenario | Resolution | |----------|------------| | No --session provided | ERROR immediately with usage message | | Session directory not found | ERROR with path, suggest checking path | | team-session.json missing | ERROR, session incomplete, suggest re-run team-coordinate | | task-analysis.json missing | ERROR, session incomplete, suggest re-run team-coordinate | | No role-specs in session | ERROR, session incomplete, suggest re-run team-coordinate | | Role-spec file not found | ERROR with expected path | | capability_gap reported | Warn only, cannot generate new role-specs | | Fast-advance spawns wrong task | Executor reconciles on next callback | | Completion action fails | Default to Keep Active, log warning |
Other measured skills in the registry, with their headline benchmark lift.