agentleFS
mcarmona1064-cellmcarmona1064-cell/clawbridge-codex/.claude/skills/add-karpathy-llm-wiki/SKILL.md

add-karpathy-llm-wiki

Skill1 starsChanged 6 months agoMITView on GitHub

Add a persistent wiki knowledge base to a ClawBridge group. Based on Karpathy's LLM Wiki pattern. Triggers on "add wiki", "wiki", "knowledge base", "llm wiki", "karpathy wiki".

  • Reads credentials

7 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-anydoc, add-clidash 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.
  • TomGranotSkill

    add-anydoc

    Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.

    Also in 5 projects that use this

  • TomGranotSkill

    add-clidash

    Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.

    Also in 5 projects that use this

  • qwibitaiSkill

    add-iron-proxy

    Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.

    Also in 4 projects that use this

  • qwibitaiSkill

    add-mattermost

    Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.

    Also in 4 projects that use this

  • b1rdmaniaSkill

    migrate-memory

    Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.

    Also in 6 projects that use this

  • nanocoaiSkill

    add-cursor

    Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).

    Also in 3 projects that use this

  • +5 more from TomGranot
  • +1 more from qwibitai

The file

We split this skill into the rules it gives an agent

7 rules. 1 is common, 1 is distinctive, and 5 are very specific to this project.

  • 1

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    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 ${CLAUDE_SKILL_DIR}/llm-wiki.md — this is the full LLM Wiki idea as written by Karpathy.

    line 12
  2. Very specific:

    If dedicated: ask which channel and chat, then register with pnpm exec tsx setup/index.ts --step register.

    line 22
  3. Common:

    Do they want the full three-layer architecture or a lighter version?

    line 29
  4. Very specific:

    Create wiki/ and sources/ directories in the group folder.

    line 36
  5. Very specific:

    If the document is a webpage, then claude can use fetch or agent-browser to open the page and extract full text if available.

    line 63
  6. Distinctive:

    If yes, create a ClawBridge scheduled task that runs in the wiki group.

    line 74
  7. Very specific:

    Use the group's folder and chat_jid from the registered groups table.

    line 99

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

Add Karpathy LLM Wiki

Set up a persistent wiki knowledge base on ClawBridge, based on Karpathy's LLM Wiki pattern.

Step 1: Read the pattern

Read ${CLAUDE_SKILL_DIR}/llm-wiki.md — this is the full LLM Wiki idea as written by Karpathy. Understand it thoroughly before proceeding. Summarize the core idea to the user briefly, then discuss what they want to build.

Step 2: Choose a group

AskUserQuestion: "Which group should have the wiki?"

  1. Main group — add to your existing main chat
  2. Dedicated group — create a new group just for the wiki
  3. Other — pick an existing group

If dedicated: ask which channel and chat, then register with pnpm exec tsx setup/index.ts --step register.

Step 3: Design collaboratively

Discuss with the user based on the pattern:

  • What's the wiki's domain or topic?
  • What kinds of sources will they add? (URLs, PDFs, images, voice notes, books, transcripts)
  • Do they want the full three-layer architecture or a lighter version?
  • Any specific conventions they care about? (The pattern intentionally leaves this open.)

Based on this discussion, create three things:

3a. Directory structure

Create wiki/ and sources/ directories in the group folder. Create initial index.md and log.md per the pattern's Indexing and Logging section. Adapt to the user's domain.

3b. Container skill

Create a container/skills/wiki/SKILL.md tailored to this user's wiki. This is the schema layer from the pattern — it tells the agent how to maintain the wiki. Base it on the pattern's Operations section (ingest, query, lint) and the conventions you agreed on with the user. Don't over-prescribe — the pattern says "your LLM figures out the rest."

3c. Group CLAUDE.md

Edit the group's CLAUDE.md to add a wiki section. This is critical — it's what turns the agent into a wiki maintainer. It should:

  • Explain the wiki system concisely: what it is, the three layers (sources, wiki, schema), the three operations (ingest, query, lint)
  • Index the key files and folders (wiki/, sources/, wiki/index.md, wiki/log.md)
  • Point to the container skill for detailed workflow
  • Ingest discipline: Be very explicit that when the user provides multiple files or points at a folder with many files, the agent MUST process them one at a time. For each file: read it, discuss takeaways, create/update all wiki pages (summary, entities, concepts, cross-references, index, log), and completely finish with that file before moving to the next. Never batch-read all files and then process them together — this produces shallow, generic pages instead of the deep integration the pattern requires.

Step 4: Source handling capabilities

Based on the source types the user plans to ingest (discussed in Step 3), check whether the agent can already handle those formats — some are supported natively, others need a skill (e.g. /add-image-vision, /add-pdf-reader, /add-voice-transcription). If a needed capability isn't installed, check if there's an available skill for it and help the user get it set up.

URL handling note

claude has built-in WebFetch, but it returns a summary, not the full document. For wiki ingestion of a URL where the full text matters, the container skill and CLAUDE.md should instruct claude to use bash commands to download full files instead. For example:

curl -sLo sources/filename.pdf "<url>"

If the document is a webpage, then claude can use fetch or agent-browser to open the page and extract full text if available. The container skill and CLAUDE.md should note this so claude gets full content for sources rather than summaries.

Step 5: Optional lint schedule

AskUserQuestion: "Want periodic wiki health checks?"

  1. Weekly
  2. Monthly
  3. Skip — lint manually

If yes, create a ClawBridge scheduled task that runs in the wiki group. This is NOT a Claude Code cron job — it's a ClawBridge group task that runs in the agent container. Insert it into the SQLite database:

pnpm exec tsx -e "
const Database = require('better-sqlite3');
const { CronExpressionParser } = require('cron-parser');
const db = new Database('store/messages.db');
const interval = CronExpressionParser.parse('<cron-expr>', { tz: process.env.TZ || 'UTC' });
const nextRun = interval.next().toISOString();
db.prepare('INSERT INTO scheduled_tasks (id, group_folder, chat_jid, prompt, schedule_type, schedule_value, context_mode, next_run, status, created_at) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)').run(
  'wiki-lint',
  '<group_folder>',
  '<chat_jid>',
  'Run a wiki lint pass per the wiki container skill. Check for contradictions, orphan pages, stale content, missing cross-references, and gaps. Report findings and offer to fix issues.',
  'cron',
  '<cron-expr>',
  'group',
  nextRun,
  'active',
  new Date().toISOString()
);
db.close();
"

Use the group's folder and chat_jid from the registered groups table. Cron expressions: 0 10 * * 0 (weekly Sunday 10am) or 0 10 1 * * (monthly 1st at 10am).

Step 6: Build and restart

pnpm run build
./container/build.sh
launchctl kickstart -k gui/$(id -u)/com.clawbridge  # macOS
# Linux: systemctl --user restart clawbridge

Tell the user to test by sending a source to the wiki group.

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.