Full Output Enforcement
Override default LLM truncation behavior to enforce complete code generation. Use when the user asks for complete files, all components, or full implementations and you're likely to truncate. Treat partial output as broken output.
Install
$ agentstack add skill-ariadoss-superskills-full-output-enforcement ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ariadoss-superskills-full-output-enforcement) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Full-Output Enforcement Policy
A partial output is a broken output.
Treat all tasks as mission-critical. Brevity is not a virtue when completeness is required.
Core Principle
When the user asks for a complete file, all components, or a full implementation — deliver everything requested. Don't prioritize response length over task completion.
Prohibited Shortcuts
Never use these in code:
// ... rest of component/* ... */// existing code here// TODO: implement// similar pattern as above
Never use these in prose:
- "for brevity..."
- "the rest follows the same pattern"
- "I'll skip the remaining components"
- "similar to the above"
Also prohibited:
- Skeleton implementations when full code was requested
- Replacing actual content with descriptions of what it would do
- Showing one example and saying "repeat for the others"
Implementation Approach
- Count deliverables — identify exactly how many files, components, or sections the user expects
- Generate each completely — no skipping, no abbreviating
- Verify before responding — check nothing was omitted
Managing Token Constraints
When approaching output limits:
- Stop at a clean logical breakpoint (end of a function, end of a component)
- Never compress or abbreviate to fit
- End with a clear status: "Completed: [X, Y, Z]. Remaining: [A, B]. Reply 'continue' for the next batch."
- On continuation, resume from exactly where you stopped — no recap
When This Applies
Activate this policy when:
- User says "complete", "full", "entire", "all", or "don't skip anything"
- Task involves multiple files or components
- User has previously complained about truncation
- The request clearly requires more output than a typical response
What "Complete" Means
- Every function has a body (not a stub)
- Every import is present and used
- Every component handles its props
- Every CSS class is defined
- Every case in a switch is handled
- Error states are included, not just happy path
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ariadoss
- Source: ariadoss/superskills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.