Overview (confidence: high)

TrueHOOHA/LLM-Wiki-Skilled is an OKF-spec-guided skill set with a formal SPEC.md for wiki conformance. Its AGENTS.md (the authoritative schema) defines 4 page types, .agents/skills/ workflow enforcement, and a “schema evolution” pattern where the document co-evolves with the operator.

Key Facts (confidence: high)

  • Form: OKF-spec-guided agent schema + .agents/skills/ enforcement
  • Page types: entity, concept, source, synthesis (4 types; our vault uses 5: entity, concept, comparison, query, summary)
  • Workflow enforcement: skills under .agents/skills/ (ingest, query, lint) — no helper scripts
  • Frontmatter: uses resource field to point at raw sources (instead of our sources array), aliases for wikilink resolution, timestamp instead of updated
  • Index rebuild: canonical procedure rewrites wiki/index.md wholesale from all page frontmatters
  • SPEC.md: formal OKF v0.1 conformance anchor
  • Schema evolution: AGENTS.md co-evolves with operator — if workflow isn’t working, change schema before changing behavior

Features

Core Architecture

  • Skill-based enforcement.agents/skills/ directory with ingest, query, lint skills
  • OKF v0.1 conformance — formal SPEC.md as the conformance anchor
  • Schema evolution — AGENTS.md co-evolves with the operator
  • 4 page types — entity, concept, source, synthesis (OKF-aligned)

Quality & Governance

  • Formal spec — SPEC.md defines conformance requirements
  • Skill-enforced workflows — no helper scripts, skills teach the agent
  • Index rebuild — canonical procedure rewrites wiki/index.md from all frontmatters
  • Aliases — wikilink resolution via frontmatter aliases field

Integration

  • agentskills.io compatible — portable skill package
  • Claude Code native — designed for skill-based operation
  • OKF ecosystem — interoperable with other OKF implementations

Data & Storage

  • Markdown + OKF frontmatter — standardized format
  • Resource field — points at raw sources for traceability

Key Differences from Our Vault (confidence: medium)

DimensionTrueHOOHAThis vault
Page typesentity, concept, source, synthesisentity, concept, comparison, query, summary
Source pageswiki/sources/frontmatter sources: field only
Workflow location.agents/skills/ (skills enforce schema)inline in AGENTS.md
Frontmatterresource, timestamp, aliasessources: [], updated, lifecycle, confidence
Index rebuildWholesale rewrite from frontmatterManual add per ingest
SPEC.mdFormal OKF conformance anchorExists (governance)

Relationships (confidence: high)

  • open-knowledge-format — (type: implements) TrueHOOHA’s entire purpose is OKF conformance; uses resource field and aliases per OKF §4.1 extensions
  • llm-wiki — (type: belongs-to) skill-packaged implementation with .agents/skills/ enforcement
  • claude-skills — (type: sibling-of) same “skills teach the agent how to operate” form factor
  • atomicstrata-llm-wiki-compiler — (type: sibling-of) both aim at standards compliance; atomicstrata is the CLI compiler, TrueHOOHA is skill-based

Implications (confidence: high)

TrueHOOHA shows the “skills-as-conformance” path. Its schema evolution pattern (co-evolve with operator) is a principle we could adopt. The aliases field for wikilink resolution is a more elegant solution than our current filename-matching approach.

Sources

^[raw/articles/llm-wiki-okf-comprehensive-report-2026.md]