No Task Output

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

Never Use TaskOutput

Instructions onlyAI & Agents
AI-generated overview

A rule that forbids using the TaskOutput tool and requires synchronous Task calls instead.

What it does
This skill provides a single behavioral rule for an agent: never call the TaskOutput tool, and instead use the Task tool in synchronous mode. It explains that TaskOutput pulls full agent transcripts into the main context window, which can exceed 70k tokens and trigger mid-conversation compaction. It includes a short wrong-versus-right pattern example.
When to use it
Use this when an agent is about to spawn background tasks or read task results and needs guidance on avoiding context flooding. It applies to workflows where agent context isolation matters.
Requirements
No tools, packages, or credentials beyond the agent itself; it is instructions only and ships no scripts.

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 contextTask(run_in_background=true)TaskOutput(task_id="...")  // 70k tokens dumped
# RIGHT - isolated context, returns summaryTask(run_in_background=false)  // Agent runs, returns summary

Source

  • Session where TaskOutput caused context overflow

Source and attribution

Source:parcadei/continuous-claude-v3in.claude/skills/no-task-outputat commitd07ff4b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal