wiki
Skill4 starsChanged todayMITView on GitHub
[oh-my-agy] Persistent markdown project wiki stored in the repository under omagy_wiki/ with keyword/tag search, cross-links, linting, and session-log capture. Use for 'wiki add', 'wiki query', 'wiki read', 'wiki lint', 'wiki delete', or when durable project knowledge (architecture, decisions, debugging notes) should be recorded or looked up.
- Reads credentials
44 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- tboome33/obsidian-mcp-routertheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- skillberry-ai/cap-evolvetheir own version, first seen Nov 8, 2026
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
- SethGammon/Citadeltheir own version, first seen Nov 4, 2026
- zlatko-lakisic/agent-cooptheir own version, first seen Nov 1, 2026
Used with
Projects with it also use deepinit, wiki-lint and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
woosikkimSkilldeepinit
Generate hierarchical AGENTS.md codebase maps for agent context
Also in 3 projects that use this
MicrosoftSkillwiki-lint
Use when an operation issue is a lint or health-check (`operationType: "lint"`) — typically the nightly lint routine or a manual "Run lint" from the UI. Audit the wiki for contradictions, orphans, weak provenance, broken links, and missing concept pages, and return a triage list — do not auto-fix.
Also in 4 projects that use this
MicrosoftSkillwiki-ingest
Use when an operation issue asks you to ingest a captured source from `raw/` into the LLM Wiki, or when the user explicitly says "ingest <slug>". The issue body will name a file under `raw/` (e.g. `raw/karpathy-llm-wiki.md`) and ask for durable wiki pages. Do not invoke this skill for Paperclip activity bundles — those use `paperclip-distill` instead.
Also in 4 projects that use this
AWSSkillmap
Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.
Also in 4 projects that use this
SethGammonSkillexperiment
Automated optimization loop with scalar fitness function. Proposes changes in isolated worktrees, measures with a metric command, keeps improvements, discards failures. Supports convergence detection and diminishing returns.
Also in 3 projects that use this
thoughtbotSkilltrace
Run a scenario and record what actually happened.
Also in 3 projects that use this
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Yeachan-Heo/oh-my-codex★ 34k13% same
Wrote their own version · 43
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- AgriciDaniel/claude-obsidian★ 16ksame name
- SethGammon/Citadel★ 927same name
- saltmd/salt.md★ 178same name
- ekadetov/llm-wiki★ 108same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- skillberry-ai/cap-evolve★ 70same name
- WALKERKILLER/Look-Tongji-Notes★ 53same name
- alirezarezvani/gaios★ 50same name
33 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 repository23 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- ai-slop-cleanerSkill
- analyzeSkill
- askSkill
- autopilotSkill
- cancelSkill
- code-reviewSkill
- deep-interviewSkill
- deep-researchSkill
- doctorSkill
- hudSkill
- loftSkill
- modernizeSkill
- performance-goalSkill
- prSkill
- ralplanSkill
- releaseSkill
- skillSkill
- teamSkill
- threat-modelSkill
- ultragoalSkill
- ultraqaSkill
- visual-ralphSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
Query: run sh <plugin>/hooks/run.sh wiki-query "<query>" [omagy_wiki] --json for deterministic lexical ranking (tags*3 + title*2 + body*1 …
- Distinctive: line 55
No vector embeddings. Query uses keyword + tag matching only.
“Common” is measured: kept by at least 6 in 10 of the 38 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
Wiki
A persistent, self-maintained markdown knowledge base for project and session knowledge. The agent operates it directly with file tools; no CLI or MCP server is needed.
Storage
- Pages:
omagy_wiki/<page-slug>.md - Index:
omagy_wiki/index.md(one line per page:- [[slug]] — title — category — tags) - Working Agreements Ledger:
omagy_wiki/agreements.md(persistent user corrections and repo invariants, e.g.- [v1] [by:human] Never use default exports in packages/core — <date>; auto-injected ahead ofindex.mdonSessionStart/PreInvocationbyomagy-hook.mjs).- Human-Agreement Guard: entries tagged
[by:human](or(by: human)) must never be deleted, reworded, or downgraded by automated wiki refreshes or overwrites (omagy-hook.mjsagreements-guardenforces this inPreToolUse). Do not re-record the same agreement correction twice from the same turn. - Time-Boxed Expiry (
expires: <ISO 8601>): a wiki page may declareexpires: <ISO 8601>in YAML frontmatter, and individual lines inagreements.mdorindex.mdmay carry[expires: YYYY-MM-DD](or(expires: <ISO>)). Once the timestamp passes,omagy-hook.mjsstops projecting that file or line into new sessions without deleting the file on disk. During$wiki refreshor$wiki lint, move expired pages to categoryreferencerather than deleting them.
- Human-Agreement Guard: entries tagged
- Child-Project Discovery: in multi-repo workspaces, touching files inside a child package/repo that has its own
omagy_wiki/automatically surfaces a once-per-session child-wiki summary viaomagy-hook.mjs. - Log:
omagy_wiki/log.md(append-only:<ISO> <op> <slug> — note)
Page format:
---
title: Auth Architecture
category: architecture
tags: [auth, architecture]
created: <ISO>
updated: <ISO>
expires: <optional ISO 8601 date or timestamp>
---
# Auth Architecture
Content. Cross-reference with [[other-page-slug]].Categories
architecture, decision, pattern, debugging, environment, session-log, reference, convention
Operations
- Add / ingest: derive a slug from the title (lowercase, hyphenated). For periodic or recurring pages (
session-log-*,weekly-*), allocate the slug withnextAvailableWikiSlug(which scans active,archive/, anddeleted/pages and appends-2,-3, etc. so archived or deleted slugs are never resurrected with stale inbound links). If a topic page already exists, merge rather than overwrite (ingest), or refuse and suggest editing (quick add). Write the page, updateindex.md, and append tolog.md. - Query: run
sh <plugin>/hooks/run.sh wiki-query "<query>" [omagy_wiki] --jsonfor deterministic lexical ranking (tags*3 + title*2 + body*1with hyphen splitting and CJK bi-gram tokenization, redacting secret snippets), and supplement withgrep -ril "<terms>" omagy_wiki/orread_filewhen full surrounding line context is needed. Rank title/tag matches first and cite page paths. - Read: open
omagy_wiki/<slug>.md. If missing, suggest the closest slugs. - List: render
index.md, or rebuild it if it is stale. - Delete / Move / Archive & Link Repair: confirm destructive deletes with the user, remove or move the page, update
index.md, append tolog.md, and runsh <plugin>/hooks/run.sh wiki-repair omagy_wiki '{"moved":{"<old>":"<new>"},"archived":["<slug>"],"deleted":["<slug>"]}'(or an action array'[{"action":"delete","oldSlug":"<slug>"}]') to automatically rewrite[[old-slug]],[[old-slug|Label]], and[Label](old-slug.md)references across all markdown pages while leaving fenced (```/~~~) and inline (`...`) code spans untouched. - Refresh: rebuild
index.mdfrom page frontmatter. - Lint: run
sh <plugin>/hooks/run.sh wiki-lint [omagy_wiki] [repoRoot] --jsonto deterministically detect dangling[[slug]]wiki links (brokenWikiLinks), dead or out-of-range repositoryfile:linecitations (brokenFileRefs), and non-meta/non-archive zero-inbound-link pages (isolatedPages), alongside checking missing/invalid frontmatter, unknown categories, duplicate titles, andindex.mddrift. Lint never rewrites files unless the user asks for fixes (delegate larger cross-link or docs sync updates todoc-steward). Surface[oh-my-agy HUD](sidecar://oh-my-agy/hud/)once when listing, reading, or linting wiki pages so the user can browse pages and lint status in theWikitab of the Auxiliary Pane.
Session capture & secret-reference rules
At the end of substantial work, if the user opted in (.omagy/config.json -> {"wiki": {"autoCapture": true}}) or asks, write a session-log-<YYYYMMDD>-<topic> page with discoveries, decisions, and gotchas. Never include real secret values or raw private transcripts.
- Secret-reference exclusion & inline/standalone token redaction: never store literal credentials/tokens, and if one entry fails validation, drop only that entry rather than discarding the whole capture.
omagy-hook.mjs(redactSecrets) automatically masks multi-line PEM private-key blocks (-----BEGIN ... PRIVATE KEY-----), standalone secret tokens (sk-...,sk_live_...,rk_live_...,ghp_...,github_pat_...,glpat-...,xox[baprs]-...,AIza...,npm_...,SG....,AKIA...,ASIA...,pypi-..., and 3-part JWTseyJ...), credentialed database URIs, inline CLI flags (--api-key=...,--token=...,--secret=...,--password=...,--client-secret=...),Authorization: Bearer <token>headers, and inlineapi_key/secret/token/passwordassignments wherever they appear before injecting wiki/agreement text. Symbolic references that merely name an env var or placeholder (process.env.X,$VAR,${VAR},{{ slot }},[FILTERED],[REDACTED], the bare wordBearer,null,example,placeholder) are valid documentation and must not be flagged as secrets unless a real secret value is concatenated onto them.
Hard constraints
- No vector embeddings. Query uses keyword + tag matching only.
- Wiki files are repository project knowledge (commit them like docs). They are separate from
.omagy/runtime state.
Does 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.

