agentleFS
Sign inStart free
baobachbaobach/llm-wiki-vault/skills/wiki/SKILL.md

wiki

Skill0 starsChanged 18 days agoMITView on GitHub

Rebuild Index.md and propose fleeting notes ready for promotion into Literature or Permanent notes. Use when the user asks to update the index, refresh the wiki, or review notes for promotion.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-slop-cleaner, ralplan and 10 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.
  • Jurel89Skill

    ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

    Also in 4 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 4 projects that use this

  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

  • woosikkimSkill

    deepinit

    Generate hierarchical AGENTS.md codebase maps for agent context

    Also in 3 projects that use this

  • ibahgatSkill

    hud

    Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.

    Also in 3 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前，通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run python3 wiki_index.py .

    line 17
  2. Very specific:

    Read its report. Add each unmapped topic:/project: target to the match list of the section it fits.

    line 19
  3. Very specific:

    Put a short fixed annotation for a note (e.g.

    line 23
  4. Very specific:

    If you changed index_sections.json, run the script again.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 36 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

Hermes Agent: do not run this skill. Tell the user it belongs to Claude Code or Codex (see the roles in AGENTS.md).

Rebuild the index

Index.md is generated by wiki_index.py from note frontmatter and index_sections.json. Never edit Index.md by hand. Your judgment goes into index_sections.json.

  1. Take the write lock.
  2. Run python3 wiki_index.py . in the vault root. It writes Index.md only when the content changed.
  3. Read its report. Add each unmapped topic:/project: target to the match list of the section it fits. Make a new section only when about 3 notes share a theme no section covers. A #tag in a match list places notes by tag. Leave a note with no usable topic or tag uncategorized.
  4. Put a short fixed annotation for a note (e.g. "published, 2026") in the notes map of index_sections.json.
  5. If you changed index_sections.json, run the script again.
  6. Log one line, then release the lock.

Propose promotions

  1. Find fleeting notes with real substance, alone or in groups on one theme.
  2. Show a shortlist, each with one line on why it is ready. Create nothing yet.
  3. Take the write lock. For each item the user approves, write a synthesized note in Literature Notes/ with sources: listing the fleeting notes, and append Promoted to [[New Note]] to each source note.
  4. Log one line per promotion, then release the lock.

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.

Check your setup, free