No Task Output
- 461 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
no-task-output is a Continuous-Claude-v3 skill that forbids TaskOutput because it dumps 70k+ agent transcript tokens into the main context, mandating synchronous Task calls instead.
About
no-task-output is a parcadei/continuous-claude-v3 agent skill marked user-invocable false that enforces a strict rule: never use the TaskOutput tool. TaskOutput reads full background agent transcripts into the main context window, often exceeding 70k tokens and triggering mid-conversation compaction that defeats agent context isolation. The correct pattern runs Task with run_in_background=false so the subagent returns only a summary synchronously. Developers and agent configurations reach for no-task-output when wiring Continuous-Claude multi-agent workflows where background TaskOutput polling would flood parent sessions and erase carefully isolated subagent work.
- no-task-output
No Task Output by the numbers
- 461 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #900 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill no-task-outputAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 461 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
Why avoid TaskOutput in Claude agent workflows?
Use no-task-output for development tasks
Who is it for?
Claude Code users running Continuous-Claude multi-agent workflows who need context isolation without TaskOutput transcript floods.
Skip if: Agents that legitimately require full background transcript inspection or environments without the Task and TaskOutput tools.
When should I use this skill?
A workflow would call TaskOutput after run_in_background=true or when agent transcripts are flooding the main context window.
What you get
Synchronous Task delegation patterns that return compact summaries without loading full subagent transcripts into parent context.
By the numbers
- Documents TaskOutput flooding 70k+ tokens into main context
Files
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 summarySource
- Session where TaskOutput caused context overflow
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Apply no-task-output when synchronous Task summaries beat TaskOutput transcript retrieval in Continuous-Claude agent chains.
FAQ
Why does no-task-output forbid TaskOutput?
no-task-output forbids TaskOutput because it reads the full background agent transcript into the main context, often 70k+ tokens, causing compaction and defeating the purpose of isolated subagent execution.
What pattern does no-task-output recommend instead?
no-task-output recommends Task with run_in_background=false so the subagent runs synchronously and returns only a summary. Avoid pairing run_in_background=true with a later TaskOutput call.