no-task-output
Restricts agent context usage by forcing the use of synchronous Task operations instead of TaskOutput.
Install
mkdir -p .claude/skills/no-task-output && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2713" && unzip -o skill.zip -d .claude/skills/no-task-output && rm skill.zipInstalls to .claude/skills/no-task-output
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Never Use TaskOutputKey capabilities
- →Enforce synchronous Task tool usage
- →Prevent context window flooding
- →Maintain isolated agent context
How it works
The skill mandates the use of the Task tool in synchronous mode, preventing the use of TaskOutput which dumps large transcripts into the context.
Inputs & outputs
When to use no-task-output
- →Maintain context window integrity
- →Prevent agent transcript flooding
About this skill
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
When not to use it
- →When explicit transcript retrieval is required for debugging
Limitations
- →Prohibits TaskOutput tool usage entirely
How it compares
It forces a specific execution pattern to preserve context window integrity compared to default asynchronous task handling.
Compared to similar skills
no-task-output side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| no-task-output (this skill) | 2 | 7mo | No flags | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
dev-browser
SawyerHood
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools