okf
Skill1 starsChanged 51 days agoMITView on GitHub
Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert to OKF', 'enrich knowledge docs', 'agent-readable knowledge', 'LLM wiki', 'knowledge catalog', 'kcmd', or wants to structure knowledge as markdown files for AI agent consumption. Also use when the user has a directory of markdown files and wants to make them interoperable or conformant with the OKF standard. Even for simple requests like 'make this folder OKF conformant' — the skill has critical structural rules the agent needs.
- Installs packages
17 other projects use a version of this.
Adopted by
Most recently taken up by
- cofin/flowtheir own version, first seen Nov 15, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- saschb2b/okf-bundlestheir own version, first seen Oct 20, 2026
- gradigit/claude-skillstheir own version, first seen Oct 15, 2026
- scaccogatto/okf-skillstheir own version, first seen Oct 13, 2026
- superwebpros/claude-skillstheir own version, first seen Oct 13, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- scaccogatto/okf-skills★ 444same name
- gannonh/kata★ 67same name
- sniperunder123/okf-knowledge★ 65same name
- gannonh/kata-symphony★ 63same name
- saschb2b/skills★ 22same name
- cofin/flow★ 20same name
- k3ybladewielder/skills★ 7same name
- eloybar/okf-skills★ 5same name
- EwenSellitto/skills★ 4same name
- 18studio/simple_okf★ 3same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- anti-kakuSkill
- artikelgenSkill
- obscura-windowsSkill
- pdf-inspector-windowsSkill
- tgrep-skillSkill
- translate-id-enSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 15 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 162
When the user wants to create an OKF bundle from scratch:
- Distinctive: line 166
Ask: What knowledge are we capturing?
- Distinctive: line 226
Use standard markdown links.
- Very specific: line 235
When claims reference external sources, use sources in frontmatter and footnotes in body:
- Distinctive: line 252
Place in any directory for progressive disclosure.
- Very specific: line 304
Every non-reserved .md file has parseable YAML frontmatter
- Very specific: line 305
Every frontmatter has a non-empty type field
- Very specific: line 388
Agent behavior: Before validating, check if okflint is installed (command -v okflint).
- Distinctive: line 395
If the user agrees to install:
- Distinctive: line 408
After installation (or if already available):
- Very specific: line 429
When okflint is not installed, use scripts/validate.sh which checks the 3 core conformance rules plus v0.2 fields.
- Distinctive: line 431
When asked to validate, check the 3 conformance rules.
- Distinctive: line 469
When the user has existing OKF concepts that need enrichment:
- Very specific: line 490
Add sources to frontmatter and footnotes to body for per-claim attribution:
- Very specific: line 516
If title, description, tags are missing, add them.
- Distinctive: line 521
Start with metadata-only docs (just frontmatter + minimal body)
- Distinctive: line 522
Add schema/structure from source system
- Very specific: line 523
Add sources from authoritative documentation
- Very specific: line 526
Add generated and optionally verified for trust tracking
- Very specific: line 591
NEVER invent data: If you don't know the correct type, ask.
- Distinctive: line 596
Ask before assuming: If the domain is unclear, ask what types and structure make sense.
- Very specific: line 597
Respect trust hierarchy: Only mark as verified by human: if actually human-reviewed.
- Distinctive: line 598
Computation integrity: Never edit the computation in an Attested Computation concept — only fill parameters.
- Distinctive: line 661
Search and type filtering
- Distinctive: line 663
When to mention this to users: If they're enriching BigQuery datasets, point them to the reference agent.
- Distinctive: line 736
When creating a bundle, present results as:
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Open Knowledge Format (OKF)
OKF is a vendor-neutral, open spec (v0.2, released by Google Cloud) for representing knowledge as a directory of markdown files with YAML frontmatter. No SDK required — if you can cat a file, you can read OKF.
It formalizes the "LLM Wiki" pattern (Karpathy's gist) into an interoperable format: wikis written by different producers can be consumed by different agents without translation.
v0.2 adds: provenance tracking (sources), trust signals (generated, verified), lifecycle management (status, stale_after), and Attested Computations — a new concept type for sanctioned, verifiable calculations.
For the full spec, see:
- references/spec-v02.md — Current version (v0.2)
- references/spec-v01.md — Legacy version (v0.1)
- references/okflint.md — Linter & Validation Guide (
okflint) - examples/majalengka-design-system/ — Real-world example bundle with
okf-base.yamland GitHub Actions CI workflow
Design Principles
- Minimally opinionated — Only
typeis required. The spec defines interoperability surface, not content model. - Producer/consumer independence — Who writes and who reads are decoupled. Human-authored bundles feed agents; LLM-generated bundles are browsed by humans.
- Format, not platform — No cloud, SDK, or vendor dependency. Value comes from how many parties speak it.
- Trust is first-class — v0.2 makes provenance, verification, and freshness queryable from frontmatter.
Key Terminology
| Term | Definition |
| Bundle | A directory tree of .md files. The unit of distribution (git repo, tarball, or subdirectory). |
| Concept | One markdown file = one unit of knowledge (table, metric, playbook, API, etc.) |
| Concept ID | File path within the bundle, minus .md suffix. Example: tables/users.md → ID tables/users |
| Frontmatter | YAML block between --- delimiters at file top. |
| Body | Everything after the frontmatter. Standard markdown. |
| Link | Standard markdown link expressing a relationship between concepts. |
| Source | A material a concept derives from, recorded in the sources frontmatter field. |
| Provenance | The set of sources a concept derives from. |
| Actor | Identity string: <producer>/<version> for agents, human:<id> for people, process:<id> for automation. |
| Trust tier | Level derived from verified: unverified, machine-confirmed, or human-reviewed. |
| Attested Computation | A concept (type: Attested Computation) carrying a sanctioned way to compute a value. |
Quick Reference — Frontmatter Fields
Core Fields (all concepts)
| Field | Required? | Description |
type | YES | Kind of concept (free-form string, e.g. BigQuery Table, Metric, Playbook, Attested Computation) |
title | Recommended | Human-readable display name |
description | Recommended | One-sentence summary |
resource | Recommended | URI identifying the underlying asset (omit for abstract concepts) |
tags | Optional | YAML list for cross-cutting categorization |
Trust & Lifecycle Fields (v0.2)
| Field | Description |
generated | { by: <actor>, at: <ISO8601> } — Who/what created this content and when |
verified | List of { by: <actor>, at: <ISO8601> } — Who confirmed correctness |
status | draft | stable | deprecated — Default: stable |
stale_after | ISO 8601 datetime — Content is stale on/after this instant |
Provenance Fields (v0.2)
| Field | Description |
sources | List of source entries (see below) |
usage_window | { from, to } — Time range for usage_count signals |
Each sources entry:
resource(REQUIRED): URL, bundle-relative path, or scope descriptorid: Stable key for footnote attributiontitle: Human-readable labelauthor: Actor who produced the sourceusage_count: How often exercised (liveness signal)last_modified: When the source last changed
Attested Computation Fields (v0.2)
For concepts with type: Attested Computation:
| Field | Description |
runtime | REQUIRED. How to run it: bigquery, postgres, dbt, python, Looker |
parameters | List of { name, type, required } — Typed holes the agent fills |
computation | Path to computation file (if not inline in body) |
executor | { resource, receipt: [...] } — How to run and what evidence to capture |
attester | { resource } — Deterministic code that verifies the receipt |
Reserved Filenames
| File | Purpose | Has frontmatter? |
index.md | Directory listing for progressive disclosure | NO* |
log.md | Change history, newest first | NO |
*Exception: bundle-root index.md MAY have frontmatter with okf_version: "0.2".
Conventional Body Headings
| Heading | When to use |
# Schema | Data assets — describe columns/fields |
# Examples | Show concrete usage (code blocks, queries) |
# Computation | Attested Computation — the sanctioned code/query |
Actor Convention
Fields that record identity (generated.by, verified[].by, sources[].author) use:
<producer>/<version>for agents:reference_agent/gemini-2.5-prohuman:<id>for people:human:ahormatiprocess:<id>for automation:process:finance-nightly
Trust tiers are derived from the human: prefix — human-verified > machine-confirmed > unverified.
Trust Tiers
Consumers derive trust from the verified field:
| Condition | Trust Tier |
No verified key | Unverified |
verified by non-human: actors only | Machine-confirmed |
verified by a human:<id> actor | Human-reviewed |
Trust tiers are advisory signals, not access control.
Create a Bundle
When the user wants to create an OKF bundle from scratch:
1. Determine scope and structure
Ask: What knowledge are we capturing? (tables, metrics, APIs, playbooks, etc.) Organize into a directory tree that makes sense for the domain.
2. Create concept documents
Each concept = one .md file. Minimal conformant example:
---
type: Metric
---
# Monthly Recurring Revenue (MRR)
Sum of all active subscriptions normalized to a monthly amount.Full v0.2 example with provenance and trust:
---
type: Metric
title: Monthly Recurring Revenue
description: Sum of all active subscription revenue normalized to monthly.
tags: [revenue, saas, kpi]
status: stable
generated: { by: human:ftelles, at: 2026-08-25T10:00:00Z }
verified: { by: human:finance-lead, at: 2026-08-25T14:00:00Z }
stale_after: 2026-12-31T00:00:00Z
sources:
- id: stripe-docs
resource: https://stripe.com/docs/billing/subscriptions
title: Stripe Subscription Billing
author: team:stripe-docs
last_modified: 2026-06-01T00:00:00Z
---
# Monthly Recurring Revenue (MRR)
## Definition
Sum of all active subscriptions normalized to a monthly amount.[^stripe-docs]
Excludes one-time fees and overages.
## Formula
`MRR = Σ(active_subscription_monthly_value)`
## Related
- [Churn Rate](./churn.md) uses MRR as denominator
- [ARR](./arr.md) = MRR × 12
[^stripe-docs]: Stripe Subscription BillingFor more examples across domains, see references/examples.md.
3. Cross-link concepts
Use standard markdown links. Two forms:
- Absolute (bundle-relative, starts with
/):[customers](/tables/customers.md)— preferred (stable when files move) - Relative:
[churn](./churn.md)
Links assert relationships. The kind of relationship is conveyed by surrounding prose, not by the link syntax. Broken links are explicitly permitted — they represent knowledge not yet written.
4. Add provenance with footnotes (v0.2)
When claims reference external sources, use sources in frontmatter and footnotes in body:
sources:
- id: ga4-schema
resource: https://developers.google.com/analytics/bigquery/export-schema
title: GA4 BigQuery Export schemaThe `events_` table is sharded daily as `events_YYYYMMDD`.[^ga4-schema]
[^ga4-schema]: GA4 BigQuery Export schema5. Generate index.md
Place in any directory for progressive disclosure. No frontmatter. Format:
# Metrics
- [MRR](./mrr.md) - Monthly recurring revenue
- [Churn](./churn.md) - Monthly churn rate
- [NPS](./nps.md) - Net Promoter ScoreEntries should include the description from the linked concept's frontmatter.
6. Generate log.md (optional)
Chronological change history, newest first, ISO 8601 date headings:
# Update Log
## 2026-08-25
- **Creation**: Added MRR, Churn, and NPS metrics.
- **Creation**: Established directory structure.
## 2026-08-20
- **Initialization**: Bundle created.7. Declare version (optional)
Bundle-root index.md may include frontmatter declaring the spec version:
---
okf_version: "0.2"
---
# My Knowledge Bundle
- [Tables](./tables/) - Database tables
- [Metrics](./metrics/) - Business KPIs8. Distribution
A bundle can be distributed as:
- A git repository (recommended — history, attribution, diffs)
- A tarball or zip archive
- A subdirectory within a larger repository
9. Verify conformance
Three rules — all must pass:
- Every non-reserved
.mdfile has parseable YAML frontmatter - Every frontmatter has a non-empty
typefield - Reserved files (
index.md,log.md) follow their defined structure when present
Create an Attested Computation (v0.2)
Attested Computations are concepts that carry not just what a value means but a sanctioned way to compute it. Use them when you need verifiable, reproducible calculations.
When to use
- Financial metrics where compliance requires audit trails
- KPIs that must be computed consistently across reports
- Any calculation where "did the sanctioned thing run" matters
Structure
---
type: Attested Computation
title: Revenue for fiscal year
description: Recognized revenue for a fiscal year, per Finance's definition.
status: stable
runtime: bigquery
parameters:
- { name: year, type: integer, required: true }
executor:
resource: references/skills/run-on-bq.md
receipt: [job_id, executed_sql, result]
attester:
resource: references/attesters/revenue.py
generated: { by: reference_agent/gemini-2.5-pro, at: 2026-06-20T22:53:05Z }
verified: { by: human:ahormati, at: 2026-06-25T09:00:00Z }
stale_after: 2026-09-23T00:00:00Z
sources:
- id: rev-policy
resource: https://wiki.acme/finance/revenue-recognition
title: Revenue recognition policy
---
# Computation
SELECT SUM(amount) AS revenue
FROM finance.recognized_revenue
WHERE fiscal_year = @year
The computation binds only the declared `parameters`, per the recognition
policy.[^rev-policy]
[^rev-policy]: Revenue recognition policyKey rules
- Agent fills parameters only — The agent supplies values for declared
parameters, never edits the computation itself - Computation can be inline or external — Use
# Computationheading for inline, orcomputation:field for external file - Executor produces receipt — Evidence the attester inspects
- Attester is deterministic — No LLM, just code that verifies the receipt
Linking to computations
Other concepts link to Attested Computations:
---
type: Metric
title: Revenue
---
# Definition
Recognized revenue for a fiscal year, computed by
[the revenue computation](../computations/revenue.md).Validate a Bundle
Preferred: okflint (when available)
okflint is a dedicated Python linter for OKF bundles with 18 rules across 3 tiers (OKF core, profile, hygiene). If installed, always prefer it over the built-in bash script.
Agent behavior: Before validating, check if okflint is installed (command -v okflint). If NOT installed, ask the user:
"okflint (linter dedicado para OKF com 18 regras, profiles via manifesto e suporte a wikilinks) não está instalado. Quer que eu instale? Opções:
uv tool install okflint(recomendado, isolado)pip install okflint- Seguir sem ele (validação básica com o script bash embutido)"
If the user agrees to install:
# Option 1: uv (recommended — installs isolated, no venv needed)
uv tool install okflint
# Option 2: pip (installs in current environment)
pip install okflint
# Verify installation
okflint --versionAfter installation (or if already available):
# Full validation with manifest (if okf-base.yaml exists)
if [ -f okf-base.yaml ]; then
okflint validate --manifest okf-base.yaml ./bundle/
else
# Core OKF validation only (no manifest needed)
okflint validate ./bundle/
fiokflint advantages over the built-in script:
- Manifest-driven profiles (enforce custom required fields, status vocabularies, per-type constraints)
- Wikilink resolution against full Obsidian vault
- JSON output (
--json) for CI pipeline parsing - Detects broken markdown links and ambiguous wikilinks
- Exit codes:
0= pass,1= conformance failure,2= bad manifest
Fallback: built-in bash script
When okflint is not installed, use scripts/validate.sh which checks the 3 core conformance rules plus v0.2 fields.
When asked to validate, check the 3 conformance rules. Report:
✅ PASS: 12/12 concept files have valid frontmatter with type field
✅ PASS: index.md follows list structure (no frontmatter)
✅ PASS: log.md uses ISO 8601 date headings, newest first
⚠ WARNING: 3 files missing 'description' field (recommended)
⚠ WARNING: 2 broken cross-links (permitted but worth noting)
ℹ INFO: 5 files with trust fields (generated/verified)
ℹ INFO: 2 Attested Computation concepts foundFor a script-based check, see scripts/validate.sh.
Errors (conformance failures)
E1: File{path}has no YAML frontmatterE2: File{path}has frontmatter but notypefield (or empty)E3: Reserved file{path}has unexpected structureE4: Attested Computation missing requiredruntimefield
Warnings (non-blocking, spec allows these)
W1: Missing recommended fieldtitleordescriptionW2: Broken cross-link{link}in{file}W3: Nogeneratedfield (v0.2 recommended)W4: Noindex.mdin directory{dir}W5:log.mddates not in ISO 8601 formatW6:sourcesentry missingresourcefieldW7:stale_afterdate has passed — content is stale
Consumers MUST NOT reject a bundle because of: missing optional fields, unknown type values, unknown frontmatter keys, broken links, or missing index files.
Enrich Concepts
When the user has existing OKF concepts that need enrichment:
Add schema section
For data assets, add # Schema with a columns table:
# Schema
| Column | Type | Description |
|--------|------|-------------|
| `order_id` | STRING | Unique identifier |
| `customer_id` | STRING | FK to [customers](/tables/customers.md) |Add examples section
For APIs, queries, or tools, add # Examples with fenced code blocks showing usage.
Add provenance (v0.2)
Add sources to frontmatter and footnotes to body for per-claim attribution:
sources:
- id: official-docs
resource: https://example.com/docs
title: Official Documentation
author: team:product-docs
last_modified: 2026-07-15T00:00:00ZAdd trust signals (v0.2)
generated: { by: reference_agent/gemini-2.5-pro, at: 2026-08-25T10:00:00Z }
verified: { by: human:domain-expert, at: 2026-08-25T14:00:00Z }
status: stable
stale_after: 2026-12-31T00:00:00ZAdd cross-links
Weave links into natural prose. Don't create a standalone "links" section — express relationships in context where they're meaningful.
Fill recommended fields
If title, description, tags are missing, add them. Derive values from body content when possible.
Enrichment workflow reference
The official enrichment agent follows this pattern — apply the same logic manually:
- Start with metadata-only docs (just frontmatter + minimal body)
- Add schema/structure from source system
- Add
sourcesfrom authoritative documentation - Weave cross-links based on discovered relationships (FKs, shared tags, join paths)
- Generate
index.mdfiles for progressive disclosure - Add
generatedand optionallyverifiedfor trust tracking
Migrate v0.1 to v0.2
Breaking changes to address
timestamp→generated.at# v0.1 timestamp: 2026-05-28T22:53:05Z # v0.2 generated: { by: human:author, at: 2026-05-28T22:53:05Z }# Citations→sources# v0.1 body # Citations [1] https://example.com/docs # v0.2 frontmatter sources: - id: docs resource: https://example.com/docs title: Example Documentation
Migration script pattern
# For each .md file:
# 1. Extract timestamp, convert to generated
# 2. Parse # Citations, convert to sources
# 3. Add footnotes in body for citations
# Consumers MAY fall back to legacy fields when v0.2 fields absentBackward compatibility
v0.2 consumers SHOULD:
- Fall back to
timestampwhengeneratedis absent - Parse legacy
# Citationswhensourcesis absent
Convert Sources to OKF
For detailed conversion guides, see references/conversion.md.
Quick rules
Notion export: Properties → frontmatter. Remove UUID suffixes from filenames. Convert Notion links → relative markdown links.
Obsidian vault: Convert [[wikilinks]] → [title](./file.md). Ensure type field exists. Move inline #tags to frontmatter.
CSV/spreadsheet: Each row = one concept. Map columns to frontmatter fields. First column = filename.
Guardrails
- NEVER invent data. If you don't know the correct
type, ask. If you don't have schema info, leave it out. No fabricated URLs or column names. - Preserve unknown fields. OKF explicitly allows extension. Don't delete fields you don't recognize.
- Don't impose taxonomy. Type values are free-form strings. Suggest descriptive values but never reject a bundle for having unexpected types.
- Broken links are OK. The spec explicitly permits them — they represent not-yet-written knowledge.
- Minimal by default. Generate only
type(required) + recommended fields that are warranted. Don't pad with empty values. - Ask before assuming. If the domain is unclear, ask what types and structure make sense.
- Respect trust hierarchy. Only mark as
verifiedbyhuman:if actually human-reviewed. Don't fabricate verification. - Computation integrity. Never edit the computation in an Attested Computation concept — only fill parameters.
Serve via Google Cloud Knowledge Catalog
Google Cloud's Knowledge Catalog natively ingests OKF bundles and serves them to agents. This is the enterprise path — optional but powerful.
kcmd CLI (Metadata as Code)
kcmd is a bidirectional sync tool between OKF-like local metadata and Knowledge Catalog. Think "git for metadata."
# Initialize from BigQuery dataset
kcmd init --bigquery-dataset <project>.<dataset>
# Pull current state from catalog
kcmd pull
# Push local changes
kcmd push --dry-run
kcmd pushAlso ships as an MCP server for agent integration:
{
"mcpServers": {
"kc-mac": {
"command": "kcmd",
"args": ["mcp", "--path", "/path/to/root"]
}
}
}MCP tools: pull, push, list-entries, lookup-entry, modify-entry.
Reference Enrichment Agent
The official enrichment agent (Python, ADK, Gemini) auto-generates OKF bundles from BigQuery metadata. Two-pass architecture:
- BQ pass — one OKF doc per table/view from metadata
- Web pass — LLM crawls seed URLs and for each page decides to:
- (a) Enrich existing concepts with citations/schemas
- (b) Mint a new
references/<slug>doc - (c) Skip irrelevant content
Controls: --web-seed-file, --web-max-pages, --web-allowed-host, --no-web.
Visualizer
The reference agent includes a visualize subcommand that renders any OKF bundle as a self-contained interactive HTML file:
python -m reference_agent visualize --bundle ./bundles/<name>Features:
- Force-directed graph of concepts with colored nodes by type
- Detail panel with frontmatter and rendered markdown
- "Cited by" backlinks
- Search and type filtering
When to mention this to users: If they're enriching BigQuery datasets, point them to the reference agent. If they want enterprise catalog integration, point to kcmd.
Manifest & Automated Lint Validation (okflint)
Setiap kali Anda membuat atau menstandardisasi bundle OKF, selalu sertakan konfigurasi linter okflint agar kepatuhan dan kebersihan bundle dapat diverifikasi secara otomatis:
1. File Manifest okf-base.yaml di Root Bundle
Manifest ini mendefinisikan aturan profil tipe konsep, field wajib/opsional, batasan status, dan aturan kebersihan (hygiene):
- Tentukan
okf_version: "0.2" - Konfigurasi
base.name,roots,reserved_files(index.md,log.md), danlink_resolution - Definisikan
profile.typessesuai domain bundle (contoh: PRD, Architecture Decision, Standard, Design Token, Component Spec, Metric, Attested Computation) - Tentukan aturan
hygiene:hygiene: broken_links: error reserved_files: error okf_v02_shapes: error legacy_forms: error unknown_fields: warn stale_content: warn split_candidates: warn split: min_lines: 220
2. GitHub Actions CI Workflow (.github/workflows/okflint.yml)
Otomatisasi pengujian bundle di GitHub Actions:
name: OKF lint
on:
push:
branches: [main]
pull_request:
jobs:
okflint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.12"
- name: Pasang okflint
run: pip install okflint
- name: Periksa manifest
run: okflint validate-manifest okf-base.yaml
- name: Validasi bundle
run: okflint validate --manifest okf-base.yaml --json > okflint-report.json
- name: Audit bundle
if: always()
run: okflint audit --manifest okf-base.yaml
- name: Simpan laporan
if: always()
uses: actions/upload-artifact@v4
with:
name: okflint-report
path: okflint-report.json3. Perintah Eksekusi Mandiri
- Validasi Manifest:
okflint validate-manifest okf-base.yaml - Validasi Kepatuhan:
okflint validate --manifest okf-base.yaml - Audit Komprehensif:
okflint audit --manifest okf-base.yaml
Lihat contoh bundle produksi lengkap di examples/majalengka-design-system/ dan panduan detail di references/okflint.md.
Output Format
When creating a bundle, present results as:
- Directory tree showing the full structure (including
okf-base.yamland.github/workflows/okflint.yml) - Each file's content in fenced code blocks
- Conformance check confirming the bundle passes the 3 rules + okflint manifest
- Trust summary (v0.2) showing verified/unverified counts
saas-metrics/
├── .github/
│ └── workflows/
│ └── okflint.yml
├── okf-base.yaml
├── index.md
├── log.md
├── metrics/
│ ├── index.md
│ ├── mrr.md
│ ├── churn.md
│ └── nps.md
└── computations/
└── mrr-calculation.mdThen show each file, then confirm:
Bundle is OKF v0.2 conformant & lint-ready ✅
- 4 concept files
- 1 Attested Computation
- 3 human-verified, 1 unverified
- 0 stale concepts
- okf-base.yaml manifest & .github/workflows/okflint.yml configuredDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

