メニュー
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 に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dceoy/hokf --skill okf-authorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Run local QA including formatting, linting, type-checking, static site build, and workflow checks for the repository. Use whenever any file has been updated.
Curate the canonical HOKF bundle and improve deterministic knowledge quality. Use when maintaining index.md or log.md, validating OKF v0.2, fixing broken links, stale or orphaned concepts, tag inconsistencies, or obvious duplicates under okf/.
Build, preview, troubleshoot, search, and publish HOKF's static Hugo presentation. Use when changing the OKF-to-Hugo adapter, site layouts or assets, Pagefind integration, GitHub Pages workflow, or diagnosing generated-content and deployment failures.
| 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.