菜单
Create or update canonical Open Knowledge Format v0.2 concepts in HOKF. Use when authoring Markdown under okf/, adding concept metadata or cross-links, or recording a knowledge change in the reserved index.md and log.md files.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dceoy/hokf --skill okf-author命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | okf-author |
| description | Create or update canonical Open Knowledge Format v0.2 concepts in HOKF. Use when authoring Markdown under okf/, adding concept metadata or cross-links, or recording a knowledge change in the reserved index.md and log.md files. |
Edit knowledge only under okf/. Treat site/content/ as disposable generated
output. Derive a concept ID from its bundle-relative path without .md; for
example, okf/concepts/architecture.md has ID concepts/architecture.
Search existing paths, titles, and descriptions before creating a concept.
Prefer updating or linking an existing concept over introducing a duplicate.
Never use reserved index.md or log.md filenames for concepts.
Begin each concept with YAML front matter. Require only a non-empty, descriptive
type; tolerate unknown types and producer-defined fields.
Recommend title, description, resource, and a lowercase kebab-case tags
list where useful. Add optional metadata only when known:
generated: { by, at } for authorship and the last meaningful change.verified as one { by, at } mapping or a list of verification events.sources as mappings that each contain resource.status as draft, stable, or deprecated.stale_after as an absolute YYYY-MM-DD date.Use human:<id>, process:<id>, or <producer>/<version> actors. Use an ISO
8601 datetime for event at fields. Never add legacy timestamp; preserve it
when encountered unless the task includes migrating it to generated.
Preserve every unknown type, key, and nested value when editing. Use standard
relative or bundle-root-relative Markdown links ending in .md.
Add a concise link and description to the nearest index.md. Index files use
headings and Markdown link lists without front matter, except the bundle-root
okf/index.md, whose only front matter key is okf_version: "0.2".
Record meaningful bundle changes in okf/log.md beneath a ## YYYY-MM-DD
heading. Keep date groups newest first.
Run:
python3 tools/okf_validate.py --src okf
python3 -m unittest discover -s tests -v
Fix conformance errors. Review advisory warnings and resolve those introduced by the change; warnings describe quality, not OKF validity.