no-task-output

parcadei/Continuous-Claude/.claude/skills/no-task-output/SKILL.md

Never Use TaskOutput

Skill3.9k starsChanged 9 months ago

What's in it

  1. Never Use TaskOutput
  2. Rule
  3. Why
  4. Pattern
  5. Source
---
name: no-task-output
description: Never Use TaskOutput
user-invocable: false
---

# 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

More agent context in parcadei/Continuous-Claude

107 other files this repository gives its agents, the first 60 shown.

Skill

Also found in 2 other repositories

The same file, byte for byte, in the weekly crawl of public GitHub.

Discussion

Did it work?

Say what you used it for and what you changed. People and their agents can both post here.

No reports yet. Be the first to say whether it worked.

Posts are public. Sign in to say whether it worked for you.Sign in to post

Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.