Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
当写、重写或重新设计任何用户可见内容时使用，包括官网、首页、UI 文案、更新提示、release notes、changelog、README 对外说明、用户文档、产品介绍、营销内容、截图说明和社交分享元信息；尤其适用于隔离内部讨论与最终呈现、判断旧内容能否继续作为结构基线、区分能力说明与真实用例场景、校验截图数据源，以及检查中文文案是否自然。
Install User Facing Content Boundary
$ npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Peiiii/nextclaw user-facing-content-boundary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/wiki/skills/content/user-facing-content-boundary .claude/skills/user-facing-content-boundary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "user-facing-content-boundary" agent skill from https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundary into .claude/skills/user-facing-content-boundary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-content-boundary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Peiiii/nextclaw user-facing-content-boundary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/wiki/skills/content/user-facing-content-boundary .agents/skills/user-facing-content-boundary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-facing-content-boundary" agent skill from https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundary into .agents/skills/user-facing-content-boundary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-content-boundary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Peiiii/nextclaw user-facing-content-boundary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/wiki/skills/content/user-facing-content-boundary .cursor/skills/user-facing-content-boundary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "user-facing-content-boundary" agent skill from https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundary into .cursor/skills/user-facing-content-boundary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-content-boundary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Peiiii/nextclaw.git --path .agents/wiki/skills/content/user-facing-content-boundary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Peiiii/nextclaw user-facing-content-boundary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/wiki/skills/content/user-facing-content-boundary .gemini/skills/user-facing-content-boundary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "user-facing-content-boundary" agent skill from https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundary into .gemini/skills/user-facing-content-boundary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-content-boundary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Peiiii/nextclaw user-facing-content-boundaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/wiki/skills/content/user-facing-content-boundary .github/skills/user-facing-content-boundary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "user-facing-content-boundary" agent skill from https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundary into .github/skills/user-facing-content-boundary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-content-boundary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Peiiii/nextclaw user-facing-content-boundary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/wiki/skills/content/user-facing-content-boundary .opencode/skills/user-facing-content-boundary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "user-facing-content-boundary" agent skill from https://github.com/Peiiii/nextclaw/tree/master/.agents/wiki/skills/content/user-facing-content-boundary into .opencode/skills/user-facing-content-boundary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-facing-content-boundary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
user-facing-content-boundary- GitHub stars
- 260
- Token cost
- ~650 tokens
- SKILL.md length
- 96 words
- Files
- 1
- Skills in repo
- 70
- Repo updated
- First seen
- Licence
- MIT
At a glance
当写、重写或重新设计任何用户可见内容时使用，包括官网、首页、UI 文案、更新提示、release notes、changelog、README 对外说明、用户文档、产品介绍、营销内容、截图说明和社交分享元信息；尤其适用于隔离内部讨论与最终呈现、判断旧内容能否继续作为结构基线、区分能力说明与真实用例场景、校验截图数据源，以及检查中文文案是否自然。
- Works in 12 steps: 先判定表面：这是对外页面、UI 文案、更新提示、用户文档或 release… → 先定事实源：重写或重新设计时，按“当前产品愿景与源码/真实运行界面 >… → 审计旧内容：对遗留页面逐项标记保留、重写、取消导航或删除；先按当前产品和用户任务建… → …
- Tasks that involve Changelog and release notes
- SKILL.md covers 目标, 固定流程, 可用句式 and 常见改写, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
User Facing Content Boundary is an agent skill from Peiiii/nextclaw. 当写、重写或重新设计任何用户可见内容时使用，包括官网、首页、UI 文案、更新提示、release notes、changelog、README 对外说明、用户文档、产品介绍、营销内容、截图说明和社交分享元信息；尤其适用于隔离内部讨论与最终呈现、判断旧内容能否继续作为结构基线、区分能力说明与真实用例场景、校验截图数据源，以及检查中文文案是否自然。
Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/user-facing-content-boundary”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- 先判定表面：这是对外页面、UI 文案、更新提示、用户文档或 release note，还是内部 design / plan / log。只有内部文档才可以解释决策过程。
- 先定事实源：重写或重新设计时，按“当前产品愿景与源码/真实运行界面 > 已确认仍有效的对外事实 > 同类产品调研 > 旧页面”的顺序取材。旧页面只是待核实的信息来源，不因已经存在就自动成为信息架构、篇幅或文案基线。
- 审计旧内容：对遗留页面逐项标记保留、重写、取消导航或删除；先按当前产品和用户任务建立完整覆盖矩阵，再决定复用哪些内容。禁止只换主题、导航或首页，却继续沿用已经失效的内容骨架。
- 拆分材料：把内部依据、原则、取舍、分类、实现顺序放到方案文档或协作回复；把用户能感知的能力、结果、步骤和限制放到最终内容。
- 结果化表达：每句话都回答用户关心的一个问题：我能做什么、在哪里做、得到什么、有什么限制、下一步怎么用。
- 截图数据源校准：官网、产品介绍或用户文档中的同一批产品截图必须使用一致的数据源。用户要求真实/本地数据时，所有被引用截图都要来自真实实例和代表性内容，不得混入空态、临时 mock 或只替换局部真实数据。NextClaw 对外产品截图统一使用产品的 default…
- 截图与文案对齐：产品界面截图必须直接截自正在运行的真实界面；合成宣传卡片、重新排版的界面拼图或仅嵌入真实素材的概念图不得冒充产品截图。每张截图必须完整看见文案声称的关键界面、对象或结果；只出现空壳、标签栏、加载态、空白预览区、被裁断的结果或相邻能力时，必须换图或重截，不能靠文字…
- 用例校准：用例必须是用户带着待办来完成的具体任务，标题应包含对象、动作或结果；接入模型、安装技能、统一入口、连接渠道 这类能力入口只能放在能力说明区，不能冒充用例。
- 动作与受众检查：标题、价值主张和用例都必须让读者想到具体对象、界面、动作与结果，并能拍成一段真实操作。声称覆盖多类用户时，要逐类指出读者从哪段文字看到了什么实际选择理由；列举“最典型 / 最容易感受价值”的受众时，不得写成排他的“只适合 /…
- 显式分组守恒：用户已经明确给出受众、主题、优势或场景的数量与分组时，把它当成内容结构合同；不得擅自增删类别，也不得把支撑能力拆成新的并列项。确需重组时，先在讨论中说明理由并获得确认。
- 中文语感检查：中文用户可见内容必须像中文直接写成，而不是英文翻译。优先短句和动词句，少用抽象名词堆叠；如果大声读起来不顺，就改成用户日常会说的话。
- 红旗扫描：最终内容里出现这些信号时必须重写或删除：我们决定、应该展示、官网优先、这个设计、本轮、核心判断、第一现场、不是只展示、不抢权重、方法论、取舍、分类依据、内部、方案、原则。
What it can do on your machine
Read from SKILL.md and the folder at commit 4d9d500. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
User Facing Content Boundary loads about 650 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 96 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Peiiii/nextclaw at commit 4d9d500, republished under its MIT licence (© Peiiii). 96 words, ~650 tokens.
Download SKILL.mdSave it as
.claude/skills/user-facing-content-boundary/SKILL.md (or your agent's skills folder).- name
- user-facing-content-boundary
- description
- 当写、重写或重新设计任何用户可见内容时使用，包括官网、首页、UI 文案、更新提示、release notes、changelog、README 对外说明、用户文档、产品介绍、营销内容、截图说明和社交分享元信息；尤其适用于隔离内部讨论与最终呈现、判断旧内容能否继续作为结构基线、区分能力说明与真实用例场景、校验截图数据源，以及检查中文文案是否自然。
用户可见内容边界
目标
把“内部怎么判断、怎么生产”和“用户最终看到什么”隔离开。用户可见内容只呈现产品结果、用户场景、可观察能力和必要边界，不暴露团队内部的方案讨论、方法论、分类依据或改版理由。
固定流程
- 先判定表面：这是对外页面、UI 文案、更新提示、用户文档或 release note，还是内部 design / plan / log。只有内部文档才可以解释决策过程。
- 先定事实源：重写或重新设计时，按“当前产品愿景与源码/真实运行界面 > 已确认仍有效的对外事实 > 同类产品调研 > 旧页面”的顺序取材。旧页面只是待核实的信息来源，不因已经存在就自动成为信息架构、篇幅或文案基线。
- 审计旧内容：对遗留页面逐项标记保留、重写、取消导航或删除；先按当前产品和用户任务建立完整覆盖矩阵，再决定复用哪些内容。禁止只换主题、导航或首页，却继续沿用已经失效的内容骨架。
- 拆分材料：把内部依据、原则、取舍、分类、实现顺序放到方案文档或协作回复；把用户能感知的能力、结果、步骤和限制放到最终内容。
- 结果化表达：每句话都回答用户关心的一个问题：我能做什么、在哪里做、得到什么、有什么限制、下一步怎么用。
- 截图数据源校准：官网、产品介绍或用户文档中的同一批产品截图必须使用一致的数据源。用户要求真实/本地数据时，所有被引用截图都要来自真实实例和代表性内容，不得混入空态、临时 mock 或只替换局部真实数据。NextClaw 对外产品截图统一使用产品的
default主题；只有用户明确要求展示其他主题时才覆盖。 - 截图与文案对齐：产品界面截图必须直接截自正在运行的真实界面；合成宣传卡片、重新排版的界面拼图或仅嵌入真实素材的概念图不得冒充产品截图。每张截图必须完整看见文案声称的关键界面、对象或结果；只出现空壳、标签栏、加载态、空白预览区、被裁断的结果或相邻能力时，必须换图或重截，不能靠文字解释补足。
- 用例校准：用例必须是用户带着待办来完成的具体任务，标题应包含对象、动作或结果；
接入模型、安装技能、统一入口、连接渠道这类能力入口只能放在能力说明区，不能冒充用例。 - 动作与受众检查：标题、价值主张和用例都必须让读者想到具体对象、界面、动作与结果，并能拍成一段真实操作。声称覆盖多类用户时，要逐类指出读者从哪段文字看到了什么实际选择理由；列举“最典型 / 最容易感受价值”的受众时，不得写成排他的“只适合 / 主要面向”名单，除非产品确实限制其他用户。产品对比优先正面说明自身优势在哪些需求中格外明显，不得靠暗示其他用户不适合、其他能力较弱或其他场景不如竞品来建立可信度。
开源、本地、可扩展等泛标签不能单独算作命中。工具或资源名词的并列清单也不算功能说明，必须改写为读者能完成的动作、对象和结果。融合、留在工作台、长期表面等只有产品作者能解释的结构词，必须改成用户实际会做和看到的事情。 - 显式分组守恒：用户已经明确给出受众、主题、优势或场景的数量与分组时，把它当成内容结构合同；不得擅自增删类别，也不得把支撑能力拆成新的并列项。确需重组时，先在讨论中说明理由并获得确认。
- 中文语感检查：中文用户可见内容必须像中文直接写成，而不是英文翻译。优先短句和动词句，少用抽象名词堆叠；如果大声读起来不顺，就改成用户日常会说的话。
- 红旗扫描：最终内容里出现这些信号时必须重写或删除：
我们决定、应该展示、官网优先、这个设计、本轮、核心判断、第一现场、不是只展示、不抢权重、方法论、取舍、分类依据、内部、方案、原则。 - 翻译腔扫描：中文最终稿里出现这些模式时必须重写：
能力进入流程、能力在背后连接、任务优先的界面、持续看见上下文、工作流里发现能力、连续堆叠能力 / 流程 / 入口 / 上下文 / 场景 / 体系等抽象词。 - 视角转换：把“我们为什么这样做”改成“用户现在可以怎样完成事”。如果一句话只能说明生产过程，移回内部文档。
- 最终自检：发布前至少读一遍成品，不看设计文档也能成立；读者不需要知道团队内部争论，也能理解产品价值。
可用句式
- 用户可以在
<界面/入口>中<动作>，并<结果>。 - 当
<场景>发生时，NextClaw 会<可观察行为>。 - 目前支持
<能力范围>；<限制>仍需用户确认或配置。 - 从
<起点>到<结果>，中间的<上下文/工具/材料>会保留在同一个工作流里。
常见改写
- 内部话：
主界面才是产品的第一现场。对外话：在主界面里开始任务、查看上下文，并继续后续操作。 - 内部话：
官网优先展示真正发生工作的地方。对外话：你可以在一个工作台里使用会话、技能、浏览器和材料。 - 内部话：
Provider 不抢主界面的表达权重。对外话：模型、渠道和工具连接在背后，工作时仍回到同一个界面。
收尾要求
- 对外内容不得混入内部讨论过程。
- 对外截图必须和内容表达互相支撑；如果截图是空态、弱状态或与文案无关，先换真实素材或调整展示位置。
- 内部方案文档可以保留原则和取舍，但必须和最终呈现分开。
- 如果发现当前成品已经混入内部话，先修成品，再判断是否需要更新本 skill 或上游内容 skill。
© Peiiii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/wiki/skills/content/user-facing-content-boundary of Peiiii/nextclaw.
Open the folder on GitHubat commit 4d9d500
Compare with similar skills
User Facing Content Boundary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| User Facing Content Boundary this skillPeiiii/nextclaw | 260 | — | ~650 | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
More from Peiiii/nextclaw
All 70 skills in this repoNextclaw Skin Studio
Peiiii/nextclaw
A skill your agent uses when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM…
Development Task Telemetry
Peiiii/nextclaw
A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…
Nextclaw Product Visual Assets
Peiiii/nextclaw
当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用；也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。
UI UX Pro Max
Peiiii/nextclaw
A skill your agent uses when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset…
Impeccable
Peiiii/nextclaw
A skill your agent uses when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable…
Nextclaw Skill Resource Hub
Peiiii/nextclaw
Curate NextClaw skill resources, including OpenClaw and community sources.
Related
Categories
Questions about User Facing Content Boundary
What does User Facing Content Boundary do?
当写、重写或重新设计任何用户可见内容时使用，包括官网、首页、UI 文案、更新提示、release notes、changelog、README 对外说明、用户文档、产品介绍、营销内容、截图说明和社交分享元信息；尤其适用于隔离内部讨论与最终呈现、判断旧内容能否继续作为结构基线、区分能力说明与真实用例场景、校验截图数据源，以及检查中文文案是否自然。. User Facing Content Boundary is an agent skill from Peiiii/nextclaw.
When should I use User Facing Content Boundary?
User Facing Content Boundary fits situations like: tasks that involve Changelog and release notes.
How do I install User Facing Content Boundary in Claude Code?
Run `npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a claude-code`. Or copy the skill folder (.agents/wiki/skills/content/user-facing-content-boundary in Peiiii/nextclaw) into .claude/skills/user-facing-content-boundary in your project. Claude Code loads it when a task matches its description.
How do I install User Facing Content Boundary in Codex?
Run `npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a codex`. Or copy the skill folder (.agents/wiki/skills/content/user-facing-content-boundary in Peiiii/nextclaw) into .agents/skills/user-facing-content-boundary in your project. Codex loads it when a task matches its description.
Can I use User Facing Content Boundary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Peiiii/nextclaw --skill user-facing-content-boundary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-facing-content-boundary, .gemini/skills/user-facing-content-boundary, .github/skills/user-facing-content-boundary and .opencode/skills/user-facing-content-boundary in your project.
What does User Facing Content Boundary need to run?
SKILL.md names no scripts, command-line tools or credentials: User Facing Content Boundary is instructions for the agent only.
Does User Facing Content Boundary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is User Facing Content Boundary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does User Facing Content Boundary use?
User Facing Content Boundary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does User Facing Content Boundary use?
About 650 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to User Facing Content Boundary?
Skills that share tags, products or a category with User Facing Content Boundary: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Facing Content Boundary?
Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 9, 2026.
Source: Peiiii/nextclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.