OpenSkillIndex← back to search
claude-codeautomation

Vibecosystem no-task-output

Never Use TaskOutput

install
source · Clone the upstream repo
git clone https://github.com/vibeeval/vibecosystem
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/vibeeval/vibecosystem "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/no-task-output" ~/.claude/skills/vibeeval-vibecosystem-no-task-output && rm -rf "$T"
manifest: skills/no-task-output/SKILL.md
tags
#context-management#tool-restriction#agent-optimization#debugging#performance
source content

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