Best use case
no-task-output is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Never Use TaskOutput
Teams using no-task-output should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/no-task-output/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How no-task-output Compares
| Feature / Agent | no-task-output | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Never Use TaskOutput
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
implement_task
Implementation agent that executes a single task and creates handoff on completion
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity