Skip to content
skillsafebeta
← Report library
Purpose / Development

Full Output Enforcement Skill Security Audit

What the author says it does (original text)

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

Independent security check

Security risks found

Files checked
1
Risks found
2
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.Risks found: 2
Medium risk

The “every task” rule exceeds the stated scope and may override a user’s brevity request

Source references: 3
What we found

The metadata says the Skill applies to tasks requiring exhaustive, unabridged output, but the body then treats “every task” as production-critical and forbids optimizing for brevity. This expands specialized behavior to every request where the Skill remains active.

Why this matters

If enabled persistently, it may produce unnecessary material and require multiple continuation turns even when the user wants a summary, diff, or short answer. This can increase time and usage cost while obscuring the most important information.

The metadata targets tasks needing exhaustive, unabridged output, but the active baseline treats “every task” as production-critical and explicitly rejects optimizing for brevity. If enabled for a summary or short-answer request, it could produce unnecessarily long responses and override the user's brevity preference. Users can ask the author to limit this rule to requests that explicitly require complete files or lists.

SKILL.md:3In the instructionsOpen original file
name: full-output-enforcementdescription: Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.---
Show 2 other places
SKILL.md:10In the instructionsOpen original file
Treat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.
SKILL.md:32In the instructionsOpen original file
- Do not compress remaining sections to squeeze them in.- Do not skip ahead to a conclusion.- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).- End with:
Medium risk

A global ban on specific text can corrupt faithful quotations or legitimate code

Source references: 2
What we found

The Skill goes beyond banning placeholder-based omissions and requires listed patterns never to appear anywhere in the output. The list includes `// TODO`, `/* ... */`, and a bare ellipsis, which can also be legitimate source text, test fixtures, documentation, or content the user needs preserved.

Why this matters

The model may remove, rewrite, or refuse to reproduce source material, changing patch semantics, making audit evidence inaccurate, or producing incorrect tests and documentation.

The apparent purpose is to prevent placeholders from replacing real implementation, but the rule says text such as `// TODO` and `/* ... */` must never be produced, then requires that no banned pattern appear “anywhere in the output.” When a user asks for verbatim quotation, review, or preservation of source containing those strings, the Skill could alter evidence or prevent faithful output. Users can restrict the ban to omission placeholders newly authored by the model, excluding quotations, fixtures, and source that must be preserved.

SKILL.md:14In the instructionsOpen original file
The following patterns are hard failures. Never produce them:**In code blocks:** `// ...`, `// rest of code`, `// implement here`, `// TODO`, `/* ... */`, `// similar to above`, `// continue pattern`, `// add more as needed`, bare `...` standing in for omitted code**In prose:** "Let me know if you want me to continue", "I can provide more details if needed", "for brevity", "the rest follows the same pattern", "similarly for the remaining", "and so on" (when replacing actual content), "I'll leave that as an exercise"
Show 1 other places
SKILL.md:45In the instructionsOpen original file
Before finalizing any response, verify:- No banned patterns from the list above appear anywhere in the output- Every item the user requested is present and finished- Code blocks contain actual runnable code, not descriptions of what code would do- Nothing was shortened to save space
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

5 instruction sections

This Skill contains only instructions governing model output; the supplied source includes no scripts, installation steps, network access, or file-changing implementation. It requires every deliverable to be generated and counted before responding.

View source
SKILL.md:24In the instructionsOpen original file
1. **Scope** — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.2. **Build** — Generate every deliverable completely. No partial drafts, no "you can extend this later."3. **Cross-check** — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.

When output approaches the length limit, the Skill instructs the model to pause at a complete section boundary, report progress, and wait for the user to send “continue.”

View source
SKILL.md:30In the instructionsOpen original file
When a response approaches the token limit:- Do not compress remaining sections to squeeze them in.- Do not skip ahead to a conclusion.- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).- End with:```[PAUSED — X of Y complete. Send "continue" to resume from: next section name]```On "continue", pick up exactly where you stopped. No recap, no repetition.
Start here · InstructionsSKILL.md
full-output-enforcement
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
Lines read
50
File checksum (to compare versions)
8d4d05fef9b924fa63822485b1e7586d976dfc6efe32165f18de76c7d2d7e640