by scaccogatto
The OKF toolkit for Claude Code — author, maintain, validate & visualize Open Knowledge Format bundles. Claude Code plugin + skills.sh.
# Add to your Claude Code skills
git clone https://github.com/scaccogatto/okf-skillsokf-skills is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by scaccogatto. The OKF toolkit for Claude Code — author, maintain, validate & visualize Open Knowledge Format bundles. Claude Code plugin + skills.sh. It has 51 GitHub stars.
okf-skills's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/scaccogatto/okf-skills" and add it to your Claude Code skills directory (see the Installation section above).
okf-skills is primarily written in Python. It is open-source under scaccogatto on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh okf-skills against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Teach your coding agent to author, maintain, validate, and visualize portable knowledge bundles — markdown your team and your agents both read.
Click any node → rendered markdown, typed metadata, and "Links to / Cited by" backlinks. No backend, nothing leaves the page.
OKF is an open, vendor-neutral format (announced by Google Cloud, June 2026) that represents knowledge — the context and curated insight around your systems — as a directory of markdown files with YAML frontmatter. No schema registry. No runtime. No SDK. If you can
cata file you can read it; if you cangit clonea repo you can ship it.
This is the Claude Code-native OKF toolchain. It teaches Claude to produce, maintain, consume, validate, and visualize OKF bundles as a normal part of how it already works — driven by the verbatim spec, backed by a deterministic conformance checker, with a self-contained graph renderer. Ships as a Claude Code plugin and as agent skills (Cursor, Codex, and 20+ agents).
Project knowledge lives scattered across wikis, code comments, and people's heads; agents re-discover it from scratch every session. OKF gives it one durable, diffable, portable home — versioned next to the code it describes. It is complementary to the rest of your context stack, not a replacement:
| OKF bundle (this) | CLAUDE.md |
Claude auto-memory | Wiki / Notion | |
|---|---|---|---|---|
| Purpose | curated knowledge | standing instructions | implicit notes | human docs |
| Portable across agents/tools | ✅ plain md + yaml | ⚠️ Claude-specific | ❌ per-agent store | ⚠️ export needed |
| Versioned with code in git | ✅ | ✅ | ❌ | ❌ |
| Typed & queryable | ✅ frontmatter | ❌ prose | ❌ | ⚠️ |
| Graph of linked concepts | ✅ | ❌ | ❌ | ⚠️ |
| Curated & reviewed in PRs | ✅ | ✅ | ❌ implicit | ⚠️ |
| Scales past the context window | ✅ progressive disclosure | ❌ loaded wholesale | ⚠️ | n/a |
Use CLAUDE.md for how to behave, auto-memory for what the agent picked up,
and an OKF bundle for what the team knows — shared, structured, and shippable.
🪞 This repo documents itself in OKF. The architecture, skills, and decisions behind okf-skills live in
.okf/— explore them as a live self-graph. CI validates that bundle on every push (dogfooding the conformance checker).
| Component | What it does |
|---|---|
/okf:okf skill |
Produce / maintain / consume bundles, applying the spec and templates. Auto-triggers when a repo has an OKF bundle. |
/okf:validate skill |
Deterministic §9 conformance check (not an eyeball pass). |
/okf:visualize skill |
Render a bundle to a self-contained interactive HTML graph (viz.html). |
skills/validate/scripts/okf_validate.py |
Standalone, zero-config validator (uv run, PyYAML via PEP 723). |
skills/visualize/scripts/okf_visualize.py |
Standalone bundle→viz.html renderer (Cytoscape + marked via CDN). |
skills/okf/reference/SPEC.md |
The OKF v0.1 spec, vendored verbatim — the source of truth. |
templates/CLAUDE-okf.md |
Snippet that turns on automatic consume/maintain in your project. |
examples/sample-bundle/ |
The conformant bundle behind the live demo — code, data, decisions, runbooks, metrics. |
As a Claude Code plugin (one-plugin marketplace):
/plugin marketplace add scaccogatto/okf-skills
/plugin install okf@scaccogatto
As agent skills via skills.sh (Claude Code, Cursor, Codex, and 20+ agents):
npx skills add scaccogatto/okf-skills # installs the okf, validate & visualize skills
Local development (no marketplace):
claude --plugin-dir /path/to/okf-skills
Both layouts coexist in this single repo: .claude-plugin/ makes it a plugin
marketplace; skills/<name>/SKILL.md makes it skills.sh-discoverable. The scripts
live inside their skills and are referenced via ${CLAUDE_SKILL_DIR}, so they work
identically in either install path.
Requires uv for the scripts (or python3 + pyyaml).
Capture knowledge — ask Claude to "document the auth service in OKF", or run:
/okf:okf produce .okf
Validate before committing:
/okf:validate .okf --strict
# or directly:
uv run skills/validate/scripts/okf_validate.py .okf --strict
Visualize the knowledge graph — a self-contained viz.html that opens in any
browser (live example):
/okf:visualize .okf
# or directly, with a title and a back-link to your repo:
uv run skills/visualize/scripts/okf_visualize.py .okf \
-o viz.html --title "My project" --link "https://github.com/me/project"
Every concept gets a shareable deep link — open viz.html#services/auth-api and the
graph loads with that concept already selected.
Turn on automatic upkeep (soft mode). This plugin ships no hooks by design.
To have Claude consult .okf/ before tasks and write knowledge back after changes,
paste templates/CLAUDE-okf.md into your project's
CLAUDE.md (or ~/.claude/CLAUDE.md for all projects).
.okf/
├── index.md # progressive disclosure (root carries okf_version)
├── log.md # ISO-dated change history, newest first
├── services/
│ ├── index.md
│ └── auth-api.md # one concept = one file; path is its ID
├── datasets/orders-db.md
├── decisions/use-okf.md
├── runbooks/payment-failures.md
└── metrics/checkout-conversion.md
Each concept needs only one thing to be conformant: YAML frontmatter with a
non-empty type. Everything else is optional and tolerated when missing.
---
type: Service
title: Auth API
description: Issues and verifies short-lived access tokens.
resource: https://github.com/acme/auth
tags: [auth, platform]
timestamp: 2026-06-14T10:00:00Z
---
# Endpoints
| Method | Path | Description |
|--------|----------|----------------------------|
| `POST` | `/token` | Exchange creds for a JWT. |
okf-skills/
├── .claude-plugin/{plugin.json, marketplace.json}
├── skills/okf/{SKILL.md, reference/SPEC.md, templates/}
├── skills/validate/{SKILL.md, scripts/okf_validate.py}
├── skills/visualize/{SKILL.md, scripts/okf_visualize.py}
├── examples/sample-bundle/ # the live-demo bundle
├── docs/ # GitHub Pages: the live interactive demo
├── templates/CLAUDE-okf.md
└── .github/workflows/ci.yml
Issues and PRs welcome — new templates, producers for more sources, validator and visualizer improvements. CI validates the plugin manifest and the example bundle on every push.
skills/okf/reference/SPEC.md is vendored
verbatim from the reference repository
with attribution.