mcpbeat

No Task Output

vibeeval/no-task-output

Never Use TaskOutput

188 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
521
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vibeeval/vibecosystem --skill no-task-output

The instruction itself

5 sections, as written by the author

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

How to use it

Copy the folder

Take vibeeval/no-task-output from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.