Wiki

This is an OMH wiki workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

wiki exists to keep knowledge work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.

Do Not Use When

• The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
• The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.

Examples

Good example:

• Prompt: wiki: six of us keep re-answering the same questions in chat; help me stand up a wiki in Notion.
• Expected behavior: Ask who reads and maintains it and what knowledge repeats, then propose one model with its breaking conditions, a skeleton, and seed pages, without claiming the store was created.
• Why: The request is wiki construction for a shared audience, not a single note capture or connector execution.

Bad example:

• Prompt: wiki: treat casual chat or unaccepted work as if this workflow already produced verified results.
• Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing wiki.
• Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.

Completion Checklist

• Audience scale, destination, knowledge types, and maintenance owner are recorded or named as missing.
• The proposed model carries its rationale, breaking conditions, and one alternative.
• Skeleton, entry points, conventions, maintenance, and seed pages are concrete enough to start today.
• Destination-specific guidance is prepared for the named store or the unknown destination gap is explicit.
• No output claims an external write, store creation, connector run, or memory mutation without evidence.
• Separate coding or connector tasks are extracted instead of buried in notes.

Recovery Notes

• If the audience scale is unknown, ask for it before proposing structure; it changes the model.
• If nobody owns maintenance, record 'unmaintained' and choose a model that survives it.
• If source evidence conflicts, route to memory or knowledge review before writing durable guidance.
• If the destination is unknown, record the missing facts and keep the guidance vendor-neutral.
• If the fact may be stale, record the staleness warning and next refresh action.

Use When

Use to design a wiki someone can start today - model, skeleton, conventions, seed pages, and maintenance sized to a personal, small-group, team, or organization audience - and to capture durable knowledge into markdown vaults, Obsidian, Notion, Google Drive/Docs, databases, or local folders.

Strong routing signals: `wiki`, `project wiki`, `build a wiki`, `start a wiki`, `organize my notes`, `external knowledge store`, `knowledge base`, `Obsidian`, `markdown vault`, `Notion knowledge base`, `Google Drive wiki`, `옵시디언`, `마크다운 볼트`, `노션 지식베이스`, `위키`, `위키 만들`, `지식베이스`, `지식 정리 체계`

Catalog Metadata

Category: knowledge Phase: design-and-capture Quality tier: knowledge-gated Reasoning demand: light

Quality bar:

• Size the structure to the audience: personal and shared wikis fail differently and get different models.
• Propose a model with its rationale, breaking conditions, and one alternative; cap seed pages at ten.
• Check existing ecosystem wiki skills before designing a bespoke structure.
• Capture durable facts with source evidence and destination-aware retrieval hints.
• Treat Obsidian as one vendor hint under a broader external knowledge connection model.
• Never present prepared wiki guidance as an observed external write, store creation, or memory mutation.
• Mark stale or uncertain knowledge instead of presenting it as permanent truth.
• Extract separate coding tasks instead of burying them in notes.

Required inputs:

• audience scale (personal, small group, team, or organization)
• whether an agent is one of the readers
• destination or existing store
• knowledge types the wiki must hold
• maintenance owner and cadence

Expected outputs:

• wiki_blueprint/v1 with organization model, rationale, breaking conditions, and one alternative
• skeleton, entry points, conventions, maintenance routine, seed pages, and ecosystem candidates
• destination-aware note guidance with retrieval hint and staleness warning
• prepared-versus-observed external write boundary

Artifact expectations:

• wiki skeleton proposal covering sections, entry points, conventions, and maintenance
• repo-local markdown knowledge artifact or metadata-only destination guidance

Safety rules:

• Do not imply hidden Hermes runtime behavior.
• Use the smallest verification that can prove the claim.

Runtime Evidence

Use the current host's own tools and subagent/task mechanism when available; otherwise run the same lanes sequentially or name the unavailable capability. A prepared plan, handoff, checklist, or skill installation is not execution, review, CI, merge-readiness, or merge evidence. Record actual tool results, or not_observed / not_available, in the record; never invent dispatch or host accounting. Treat supplied context as advisory, not proof of hidden memory reads or writes. State scope, constraints, verification, and the stop condition before work. Reply in the user's own words and the host's own voice: OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done. Supporting paths are relative to this skill directory; sibling skill paths are relative to its parent. Resolve them from the host-provided skill base directory ({baseDir} on hosts that provide it), never a hardcoded install location. A named workflow not installed here is unavailable, not permission to emulate its host-specific capabilities. Verify through the real surface before done.