agentleFS
YomudoglyYomudogly/oh-my-agy/skills/wiki/SKILL.md

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

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.
  • woosikkimSkill

    deepinit

    Generate hierarchical AGENTS.md codebase maps for agent context

    Also in 3 projects that use this

  • MicrosoftSkill

    wiki-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

  • MicrosoftSkill

    wiki-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

  • AWSSkill

    map

    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

  • SethGammonSkill

    experiment

    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

  • thoughtbotSkill

    trace

    Run a scenario and record what actually happened.

    Also in 3 projects that use this

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
  1. Very specific:

    Query: run sh <plugin>/hooks/run.sh wiki-query "<query>" [omagy_wiki] --json for deterministic lexical ranking (tags*3 + title*2 + body*1 …

    line 42
  2. Distinctive:

    No vector embeddings. Query uses keyword + tag matching only.

    line 55

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 of index.md on SessionStart/PreInvocation by omagy-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.mjs agreements-guard enforces this in PreToolUse). Do not re-record the same agreement correction twice from the same turn.
    • Time-Boxed Expiry (expires: <ISO 8601>): a wiki page may declare expires: <ISO 8601> in YAML frontmatter, and individual lines in agreements.md or index.md may carry [expires: YYYY-MM-DD] (or (expires: <ISO>)). Once the timestamp passes, omagy-hook.mjs stops projecting that file or line into new sessions without deleting the file on disk. During $wiki refresh or $wiki lint, move expired pages to category reference rather than deleting them.
  • 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 via omagy-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 with nextAvailableWikiSlug (which scans active, archive/, and deleted/ 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, update index.md, and append to log.md.
  • Query: run sh <plugin>/hooks/run.sh wiki-query "<query>" [omagy_wiki] --json for deterministic lexical ranking (tags*3 + title*2 + body*1 with hyphen splitting and CJK bi-gram tokenization, redacting secret snippets), and supplement with grep -ril "<terms>" omagy_wiki/ or read_file when 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 to log.md, and run sh <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.md from page frontmatter.
  • Lint: run sh <plugin>/hooks/run.sh wiki-lint [omagy_wiki] [repoRoot] --json to deterministically detect dangling [[slug]] wiki links (brokenWikiLinks), dead or out-of-range repository file:line citations (brokenFileRefs), and non-meta/non-archive zero-inbound-link pages (isolatedPages), alongside checking missing/invalid frontmatter, unknown categories, duplicate titles, and index.md drift. Lint never rewrites files unless the user asks for fixes (delegate larger cross-link or docs sync updates to doc-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 the Wiki tab 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 JWTs eyJ...), credentialed database URIs, inline CLI flags (--api-key=..., --token=..., --secret=..., --password=..., --client-secret=...), Authorization: Bearer <token> headers, and inline api_key/secret/token/password assignments 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 word Bearer, 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.