Never Use TaskOutput
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill no-task-output-carmandale-agent-config --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of No Task Output Carmandale Agent Config?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-no-task-output-carmandale-agent-config)More formats (shields.io, HTML) on the badges page.
---
name: no-task-output
description: Never Use TaskOutput
---
# Never Use TaskOutput
TaskOutput floods the main context window with agent transcripts (70k+ tokens).
## Rule
NEVER use `TaskOutput` tool. Use `Task` tool with synchronous mode instead.
## Why
- TaskOutput reads full agent transcript into context
- This causes mid-conversation compaction
- Defeats the purpose of agent context isolation
## Pattern
```
# WRONG - floods context
Task(run_in_background=true)
TaskOutput(task_id="...") // 70k tokens dumped
# RIGHT - isolated context, returns summary
Task(run_in_background=false) // Agent runs, returns summary
```
## Source
- Session where TaskOutput caused context overflow
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...