agentleFS
Sign inStart free
VladTheProgrammerVladTheProgrammer/claude-asimov/.claude/skills/wiki-capture/SKILL.md

wiki-capture

Skill0 starsChanged 4 months agoMITView on GitHub

Author a wiki page directly from the current work — a decision (ADR), an experiment result, or a concept — without an external source. Usage: /wiki-capture {decision|experiment|concept} {title}

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use claude-history-ingest, graph-colorize 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.
  • Ivy-Chen1999Skill

    claude-history-ingest

    Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.

    Also in 3 projects that use this

  • Ivy-Chen1999Skill

    graph-colorize

    Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups. Use this skill when the user says "color my graph", "color code obsidian", "colorize the graph", "color the graph by tag", "color by category", "highlight visibility in graph", "make the graph colorful", "distinguish tags in graph", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags/categories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.

    Also in 3 projects that use this

  • nexuschainsSkill

    cross-linker

    Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.

    Also in 3 projects that use this

  • nexuschainsSkill

    tag-taxonomy

    Enforces and normalizes tags across the wiki against the controlled vocabulary in wiki/schema/tag-taxonomy.md. Use this skill when the operator says "fix my tags", "normalize tags", "tag audit", "clean up tags", "tag taxonomy", or "my tags are a mess". Also use when creating or updating wiki pages and the right tags are unclear. Operates in three modes: Audit (report current state), Normalize (apply fixes), and Classify (tag a single new page). Always reads the taxonomy file before assigning any tags.

    Also in 3 projects that use this

  • bozhouDevSkill

    wiki-update

    Use when revising existing wiki pages because knowledge has changed, a new piece of information updates or contradicts existing content, or the user wants to directly edit wiki content with LLM assistance.

    Also in 3 projects that use this

  • +6 more from Ivy-Chen1999
  • +1 more from nexuschains

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Read wiki/SCHEMA.md first.

    line 6
  2. Very specific:

    If this supersedes an earlier decision, set the old one's status: superseded and add a forward [[link]] both ways.

    line 20
  3. Very specific:

    Append-only: never rewrite a past result.

    line 30
  4. Very specific:

    Add/refresh the page in wiki/index.md.

    line 41
  5. Very specific:

    If the fact must be known every session (an invariant), also promote a one-line version to CLAUDE.md / a rule via /add-to-claude / …

    line 43

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

Read wiki/SCHEMA.md first. Use it for frontmatter, naming, and [[wikilink]] conventions. This skill captures internal knowledge (decisions, experiment results, concepts) that did not come from an ingested source.

Parse the input:

  • First argument is the kind: decision, experiment, or concept.
  • The rest is the title.

Decision (ADR)

  1. File: wiki/decisions/NNNN-{slug}.md (next zero-padded sequence). Frontmatter type: decision, status: proposed|accepted.
  2. Body sections: Context · Decision · Rationale · Alternatives rejected · Consequences · Status.
  3. If this supersedes an earlier decision, set the old one's status: superseded and add a forward [[link]] both ways.
  4. Cross-link related concepts/decisions in related: and inline.

Experiment

  1. File: wiki/experiments/YYYY-MM-DD-{slug}.md. Frontmatter type: experiment.
  2. Body sections: Hypothesis · Setup (params, data window, costs/funding/slippage modeled) · Results (metrics — be honest, include drawdowns and failures) · Verdict (keep | reject | inconclusive) · Lessons.
  3. Append-only: never rewrite a past result. A re-run is a new entry that [[links]] to the prior one.
  4. Link the concepts/decisions the experiment tests.

Concept

  1. File: wiki/concepts/{slug}.md (or entities/). Frontmatter type: concept.
  2. Body: Summary · Key facts (each with a sources: trace where possible) · Relationships ([[links]]) · Open questions.

After any capture

  • Add/refresh the page in wiki/index.md.
  • Append one line to wiki/log.md: YYYY-MM-DD | capture | {page} | {note}.
  • If the fact must be known every session (an invariant), also promote a one-line version to CLAUDE.md / a rule via /add-to-claude / /add-to-rules.

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