技能库智客分类：Agent 工作流 full-output-enforcement

Full Output Enforcement

覆盖默认 LLM 校正行为。执行完整的代码生成,禁止占位符模式,并干净地处理符号限制分出. 适用于任何需要详尽无遗、未压缩的产出的任务.

官方网址：GitHub

技能介绍

先看中文介绍；官方 description 原文单独保留，不改写 SKILL.md。

做什么

覆盖默认 LLM 校正行为。执行完整的代码生成,禁止占位符模式,并干净地处理符号限制分出. 适用于任何需要详尽无遗、未压缩的产出的任务.

何时用

官方 description 未单独写出 Use when。按规范，代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露：启动时只加载 name 与 description（约 100 token）；任务匹配后才读入整份 SKILL.md 正文；scripts/、references/、assets/ 仅在需要时再读。本文件正文结构：Full-Output Enforcement、Baseline、Banned Output Patterns、Execution Process、Handling Long Outputs、Quick Check。

文件分析

文件分析：这是一份仅含 SKILL.md 的指令型技能，代理激活后整份正文进入上下文。

官方 description（原文）

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.

Full-Output EnforcementBaselineBanned Output PatternsExecution ProcessHandling Long OutputsQuick Check

来源分类：GitHub skill

来源与网址

市场来源：GitHub

开源榜 Skill 分类

SKILL.md 与 Agent 调用

官方规范 ↗

name: full-output-enforcement
description: 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.

发现技能客户端向 Agent 提供名称与描述目录。
匹配与调用用户指定或任务匹配后，载入 SKILL.md 指令。
按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围，保留技能包的附属文件，安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理，确认其中的目标目录与客户端匹配。

把 Agent Skill「full-output-enforcement」安装到我的项目：SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-94761d0ca65e325e-Full-Output-Enforcement.html
请存为 .cursor/skills/full-output-enforcement/SKILL.md 或 .claude/skills/full-output-enforcement/SKILL.md，frontmatter 的 name 与 description 保持原样，不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表，确认实际名称。

npx skills add 'https://github.com/nexu-io/open-design/tree/HEAD/skills/output-skill' --list

目标客户端安装范围

npx skills add 'https://github.com/nexu-io/open-design/tree/HEAD/skills/output-skill' --skill 'full-output-enforcement'

CLI 会交互选择目标 Agent，默认安装到项目；用户级安装使用 -g。先通过查看命令核对仓库内容，再用 npx skills list 检查已安装技能。

SKILL.md 原文可复制，不会改动源文件

---
name: full-output-enforcement
description: |
  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.
triggers:
  - "full output"
  - "no placeholders"
  - "complete code"
  - "unabridged implementation"
od:
  mode: prototype
  surface: web
  platform: desktop
  scenario: engineering
  category: agent-workflow
  upstream: "https://github.com/Leonxlnx/taste-skill"
  preview:
    type: html
  design_system:
    requires: false
  example_prompt: |
    Produce the complete implementation for the requested artifact with no placeholder comments, no omitted sections, and clean split instructions only if output length requires it.
---

# Full-Output Enforcement

## Baseline

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.

## Banned Output Patterns

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"

**Structural shortcuts:** Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.

## Execution Process

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.

## Handling Long Outputs

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.

## Quick Check

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

阅读排版

name: full-output-enforcement description: | 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. triggers:

"full output"
"no placeholders"
"complete code"
"unabridged implementation" od: mode: prototype surface: web platform: desktop scenario: engineering category: agent-workflow upstream: "https://github.com/Leonxlnx/taste-skill" preview: type: html design_system: requires: false example_prompt: | Produce the complete implementation for the requested artifact with no placeholder comments, no omitted sections, and clean split instructions only if output length requires it.

Full-Output Enforcement

Baseline

Banned Output Patterns

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"

Structural shortcuts: Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.

Execution Process

Scope — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
Build — Generate every deliverable completely. No partial drafts, no "you can extend this later."
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.

Handling Long Outputs

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.

Quick Check

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