ccf-skill-forger

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

CCF Skill Forger

Invocation Controls

调用控制

CCFA Handoff Mode: PARTIAL (Recommended). Follow

metadata.ccf_skill_controls.handoff_question_mode

and

../ccf-common/references/handoff-modes.md

when maintaining the CCFA skill family.

When maintaining the CCFA skill family, preserve

metadata.ccf_skill_controls

in each

SKILL.md

. Do not add sibling-skill transitions without checking

../ccf-common/references/routing.md

../ccf-common/references/task-modes.md

../ccf-common/references/handoff-modes.md

, and the denylist-respecting fallback.

If the user disables a skill or asks for writing-only behavior, encode that boundary directly in the edited skill instructions. Do not weaken idea-scope protection in writing skills unless the user explicitly requests that policy change.

When adding sources, update

../ccf-common/references/source-registry.yaml

instead of duplicating URL lists in sibling skills. When adding browsing or evidence rules, keep them aligned with

../ccf-common/references/privacy-and-evidence.md

Never commit machine-specific absolute paths, usernames, expanded home directories, or private local directory names into skills, README files, source registries, diagrams, examples, scripts, or command snippets. Use

$CODEX_HOME

$HOME

, repo-relative paths, or placeholders that do not identify the user or machine.

CCFA交接模式：PARTIAL（推荐）。维护CCFA技能家族时，请遵循

metadata.ccf_skill_controls.handoff_question_mode

以及

../ccf-common/references/handoff-modes.md

中的要求。

维护CCFA技能家族时，请保留每个

SKILL.md

中的

metadata.ccf_skill_controls

配置。在未检查

../ccf-common/references/routing.md

、

../ccf-common/references/task-modes.md

、

../ccf-common/references/handoff-modes.md

以及尊重拒绝列表的回退机制前，请勿添加兄弟技能跳转。

如果用户禁用某项技能或要求仅执行写作操作，请直接在编辑后的技能说明中明确该边界。除非用户明确要求更改策略，否则请勿削弱写作技能中的范围保护机制。

添加来源时，请更新

../ccf-common/references/source-registry.yaml

，而非在兄弟技能中重复URL列表。添加浏览或证据规则时，请确保与

../ccf-common/references/privacy-and-evidence.md

保持一致。

切勿将机器特定的绝对路径、用户名、展开的主目录或私有本地目录名称提交到技能、README文件、源注册表、图表、示例、脚本或命令片段中。请使用

$CODEX_HOME

、

$HOME

、仓库相对路径或不会识别用户或机器的占位符。

Core Rule

核心规则

Build skills as compact operational guidance for another Codex session. Keep

SKILL.md

focused on trigger-relevant workflow, decisions, and resource navigation. Put detailed examples, checklists, schemas, policy text, or long instructions in

references/

and load them only when needed. This skill also owns CCFA documentation SVG diagrams; do not create a separate runtime drawing skill for repository architecture or workflow diagrams.

将技能构建为供另一个Codex会话使用的简洁操作指南。保持

SKILL.md

聚焦于与触发相关的工作流、决策和资源导航。将详细示例、检查清单、模式、政策文本或冗长说明放在

references/

目录中，仅在需要时加载。本技能同时负责CCFA文档SVG图的维护；请勿为仓库架构或工作流图创建单独的运行时绘图技能。

Workflow

工作流

Clarify the goal with concrete examples. If the user's intent is clear, proceed with reasonable assumptions. Ask only for missing information that changes the skill's scope, location, or required assets.
Choose a skill name and destination. Use lowercase letters, digits, and hyphens only; keep names under 64 characters; check for conflicts in the target skills directory. Default to
```
$CODEX_HOME/skills
```
; if unset, use
```
~/.codex/skills
```
.
Decide the resource shape:
- Use only
```
SKILL.md
```
  for short, stable procedural guidance.
- Add
```
references/
```
  for detailed documentation that Codex should read selectively.
- Add
```
scripts/
```
  only for repeatable deterministic operations or fragile command sequences.
- Add
```
assets/
```
  only for templates, images, boilerplate, or other files used in final outputs.
Initialize the skill when creating from scratch. Prefer the local
```
skill-creator
```
initializer if available:

powershell

python '<skill-creator-dir>/scripts/init_skill.py' <skill-name> --path '<skills-dir>' --resources references,scripts

Write
```
SKILL.md
```
before filling optional resources. Put all "when to use" trigger wording in the YAML
```
description
```
; the body is loaded only after trigger selection. Use imperative instructions and avoid user-facing tutorial prose.
Add resources that directly support the skill. Remove placeholder files and unused directories. Test any script by running it on a small representative example.
Validate and iterate. Run the available validator, then inspect manually for trigger quality, resource links, naming, and excessive context. Use realistic future prompts to decide whether the skill actually helps.
Run
```
ccf-common/scripts/check_path_privacy.py
```
before finishing CCFA-family maintenance. Replace any committed local absolute path or username with
```
$CODEX_HOME
```
,
```
$HOME
```
, a repo-relative path, or a non-identifying placeholder.
For CCFA documentation diagrams, update
```
../tools/build_ccfa_diagrams.py
```
, regenerate all language variants, and screenshot-check rendered SVG output. Use
```
references/svg-style-guide.md
```
; do not hand-edit generated SVGs unless the same change is backported to the generator.

用具体示例明确目标。如果用户意图清晰，可基于合理假设推进。仅询问会改变技能范围、位置或所需资源的缺失信息。
选择技能名称和目标路径。仅使用小写字母、数字和连字符；名称长度不超过64个字符；检查目标技能目录中是否存在冲突。默认路径为
```
$CODEX_HOME/skills
```
；若未设置，则使用
```
~/.codex/skills
```
。
确定资源结构：
- 简短、稳定的流程指南仅使用
```
SKILL.md
```
  。
- 若需Codex选择性读取的详细文档，添加
```
references/
```
  目录。
- 仅为可重复的确定性操作或易出错的命令序列添加
```
scripts/
```
  目录。
- 仅为模板、图片、样板代码或最终输出中使用的其他文件添加
```
assets/
```
  目录。
从零创建技能时进行初始化。如果可用，优先使用本地
```
skill-creator
```
初始化工具：

powershell

python '<skill-creator-dir>/scripts/init_skill.py' <skill-name> --path '<skills-dir>' --resources references,scripts

在填充可选资源前编写
```
SKILL.md
```
。将所有“何时使用”的触发语放在YAML格式的
```
description
```
中；仅在触发选择后才加载正文内容。使用祈使句指令，避免面向用户的教程式文字。
添加直接支持技能的资源。移除占位文件和未使用的目录。通过在小型代表性示例上运行来测试任何脚本。
验证并迭代。运行可用的验证工具，然后手动检查触发语质量、资源链接、命名和冗余上下文。使用真实的未来提示来判断该技能是否真正有用。
完成CCFA家族维护前，运行
```
ccf-common/scripts/check_path_privacy.py
```
。将任何已提交的本地绝对路径或用户名替换为
```
$CODEX_HOME
```
、
```
$HOME
```
、仓库相对路径或非识别性占位符。
对于CCFA文档图，更新
```
../tools/build_ccfa_diagrams.py
```
，重新生成所有语言变体，并截图检查渲染后的SVG输出。遵循
```
references/svg-style-guide.md
```
；除非将相同更改回写到生成器中，否则请勿手动编辑生成的SVG。

Reference Files

参考文件

Load these files only when the task calls for them:

```
references/design-checklist.md
```
: Use when planning a new skill, reviewing structure, or deciding whether content belongs in
```
SKILL.md
```
,
```
references/
```
,
```
scripts/
```
, or
```
assets/
```
.
```
references/patterns.md
```
: Use when drafting a concrete
```
SKILL.md
```
shape, frontmatter description, or example-driven workflow.
```
references/local-commands.md
```
: Use when scaffolding or validating skills on this machine, especially in PowerShell or Windows paths.
```
references/svg-style-guide.md
```
: Use when maintaining CCFA architecture, workflow, routing, installation, artifact, catalog, or demo SVG diagrams.

仅在任务需要时加载以下文件：

```
references/design-checklist.md
```
：规划新技能、审查结构或决定内容应放在
```
SKILL.md
```
、
```
references/
```
、
```
scripts/
```
还是
```
assets/
```
时使用。
```
references/patterns.md
```
：起草具体的
```
SKILL.md
```
结构、前置描述或基于示例的工作流时使用。
```
references/local-commands.md
```
：在本机搭建或验证技能时使用，尤其是PowerShell或Windows路径场景。
```
references/svg-style-guide.md
```
：维护CCFA架构、工作流、路由、安装、工件、目录或演示SVG图时使用。

Output Style

输出风格

When creating a skill, give the user a concise scheme before editing, then create the files. After creation, report the skill name, location, key files, and validation result. If validation cannot run because a local dependency is missing, say exactly what failed and perform the manual checks from

references/design-checklist.md

创建技能时，请在编辑前向用户提供简洁方案，然后创建文件。创建完成后，报告技能名称、位置、关键文件和验证结果。如果因缺少本地依赖而无法运行验证，请明确说明失败原因，并执行

references/design-checklist.md

中的手动检查。