agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/wiki-ingest/SKILL.md

wiki-ingest

Skill9 starsChanged 7 months agoMITView on GitHub

Integrate a new source from wiki/raw/ into the curated wiki. Reads the source, identifies affected pages, delegates updates to domain specialists, and applies a coherent changeset. Use whenever raw sources have been added (e.g., after research agents complete, or after Obsidian Web Clipper drops a new article into wiki/raw/community/articles/).

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-status, wiki-capture and 9 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.
  • nexuschainsSkill

    wiki-status

    Reports the current state of the wiki vault — page counts, category breakdown, hub pages, orphans, stale entries, and a delta showing what has changed since the last ingest. Use this skill when the operator asks "what's the status", "wiki dashboard", "how many pages", "what's stale", "what's been ingested", "show me the delta", or "wiki health overview". Also surfaces structural insights (top hubs, fragmented clusters, bridge pages) when the operator asks "wiki insights", "what's central", or "show me the hubs". Read-only: this skill reports and recommends; it does not modify any files.

    Also in 5 projects that use this

  • jehrhardtSkill

    wiki-capture

    Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.

    Also in 6 projects that use this

  • Ivy-Chen1999Skill

    wiki-research

    Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.

    Also in 5 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 4 projects that use this

  • Ivy-Chen1999Skill

    wiki-setup

    Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.

    Also in 5 projects that use this

  • bozhouDevSkill

    wiki-init

    Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.

    Also in 7 projects that use this

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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    If no argument: scan wiki/raw/ for new files (files not yet cited in any wiki page's sources: frontmatter)

    line 13
  2. Distinctive:

    Read the file(s) fully. Every word.

    line 27
  3. Very specific:

    Use grep/glob against wiki/ to check which of these pages already exist.

    line 43
  4. Distinctive:

    Read its full current content

    line 48
  5. Distinctive:

    Wait for each owner's draft.

    line 70
  6. Very specific:

    If you are the owner (wiki-curator owns index.md, log.md, SCHEMA.md, README.md), draft the update yourself.

    line 72
  7. Very specific:

    Update sources: in every touched page's frontmatter to include the new raw source path

    line 141
  8. Very specific:

    Update updated: timestamp in every touched page's frontmatter to today's date

    line 142
  9. Very specific:

    If any new pages were created, add them to wiki/index.md under the right category

    line 143
  10. Very specific:

    Verify [[wikilinks]] — if a new link points to a page that doesn't exist, create the stub

    line 144
  11. Very specific:

    If the user runs /wiki-ingest <directory>, iterate over all files in that directory:

    line 165
  12. Distinctive:

    Write one log entry per file ingested

    line 171

“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-ingest — Integrate a Raw Source

Delegate to: wiki-curator

Arguments

  • <source> — path to a raw source file or directory to ingest
  • If no argument: scan wiki/raw/ for new files (files not yet cited in any wiki page's sources: frontmatter)

Prerequisites

  • wiki/SCHEMA.md exists (wiki has been seeded via /wiki-seed)
  • wiki/index.md exists
  • The source path exists under wiki/raw/

Workflow

1. Read the Schema

Load wiki/SCHEMA.md first. Every output must comply with it.

2. Read the Source

Read the file(s) fully. Every word. Note:

  • Source type (check frontmatter source_type): official-roblox-docs, luau-spec, devforum, reddit, article, github-readme
  • Subject (what it's about): service, concept, pattern, exploit, etc.
  • Key claims: specific facts, numbers, APIs, patterns mentioned

3. Scan for Wiki Targets

Identify every entity the source touches. For each:

  • Roblox class name → candidate page in wiki/services/<ClassName>.md
  • Luau feature → candidate page in wiki/luau/*.md
  • Pattern name → candidate page in wiki/concepts/*.md or wiki/patterns/*.md
  • Exploit → candidate page in wiki/exploits/*.md
  • Performance topic → candidate page in wiki/performance/*.md
  • Monetization concept → candidate page in wiki/monetization/*.md
  • Studio/tooling → candidate page in wiki/studio/*.md

Use grep/glob against wiki/ to check which of these pages already exist.

4. Load Each Affected Page

For every existing page that's a candidate:

  • Read its full current content
  • Note its owner:, status:, sources: frontmatter
  • Note its current Related section links

5. Determine Required Changes

For each page, decide:

No change needed — source adds nothing new beyond what's already there. Skip.

Minor update — add a detail, fix a small inaccuracy, update a number. Draft the specific edit.

Significant update — substantial new content, new code examples, new edge cases. Draft the section additions.

New page — source introduces a topic that has no existing page. Plan to create a stub (if minor) or complete page (if source has enough content).

Contradiction — source directly contradicts an existing claim. Add a ⚠️ Contradiction flagged block to the page; do NOT silently overwrite.

6. Delegate Updates to Owners

For each page requiring changes, identify the owner: from its frontmatter. Delegate the draft to that agent by invoking them with the source content + the current page content + the proposed change description.

Wait for each owner's draft. If multiple pages share an owner, batch them.

If you are the owner (wiki-curator owns index.md, log.md, SCHEMA.md, README.md), draft the update yourself.

7. Assemble the Full Changeset

Collect all drafts into one package:

# Ingest Proposal: <source filename>

**Source:** wiki/raw/<path>
**Source type:** <type>
**Captured:** <captured_at>
**Captured by:** <captured_by>

## Summary
<1-2 sentences on what the source is about>

## Pages to Update (N)

### [[Page Name]]
**Owner:** <agent>
**Change type:** minor | significant | contradiction
**Diff summary:**
<brief description of changes>

<If diff is small, include it inline. If large, summarize and show on request.>

---

### [[Another Page]]
...

## Pages to Create (N)

### [[New Page Name]]
**Type:** stub | complete
**Owner:** <agent>
**Reason:** <why this page is needed>

## Contradictions Flagged (N)

### [[Page with contradiction]]
**Current claim:** ...
**New source claims:** ...
**Resolution:** Defer to <owner> agent for review.

## Raw Source Update

The following pages will have their `sources:` frontmatter extended to cite:
- `wiki/raw/<path>`

## Estimated Scope
- Files touched: N
- Lines changed: ~N
- New pages: N
- Time to apply: <few seconds | several seconds>

8. Present to User

Show the full changeset. Wait for one of:

  • "go" or equivalent → apply all changes
  • "skip X" → remove X from the changeset and apply the rest
  • "cancel" → discard and report

9. Apply Changes

On approval:

  1. Apply all page updates in one pass (use Edit for in-place edits, Write for new files)
  2. Update sources: in every touched page's frontmatter to include the new raw source path
  3. Update updated: timestamp in every touched page's frontmatter to today's date
  4. If any new pages were created, add them to wiki/index.md under the right category
  5. Verify [[wikilinks]] — if a new link points to a page that doesn't exist, create the stub

10. Append to wiki/log.md

## [YYYY-MM-DD] ingest | <source title>
- Source: wiki/raw/<path>
- Source type: <type>
- Updated: [[page1]], [[page2]], [[page3]]
- Created: [[new-page1]], [[new-page2]]
- Contradictions flagged: [[page4]]
- Delegated to: <list of agent names>
- Notable additions: <1-3 bullets on what the wiki now knows that it didn't before>

11. Final Check

Offer to run /wiki-lint as a sanity check. If the user says yes, run it and report any new issues introduced.

Bulk Ingest Mode

If the user runs /wiki-ingest <directory>, iterate over all files in that directory:

  1. Sort files by type (more authoritative sources first: official-docs > spec > article > devforum > reddit)
  2. For each file, run the single-file workflow above
  3. Batch the changesets into a single user-approval step (show all proposals together, let the user approve/skip per-file)
  4. Apply approved changes
  5. Write one log entry per file ingested

Safety: For bulk ingest with > 10 files, warn the user first: "This will touch an estimated N pages. Proceed?"

Output to User

After completion:

  • Files ingested
  • Pages updated (count + list)
  • Pages created (count + list)
  • Contradictions flagged (count + list — these need follow-up)
  • Recommendation for next step (e.g., "Run /wiki-lint to verify" or "Run /wiki-ingest on the next batch")

Anti-Patterns

  • ❌ Do not silently overwrite — always present the diff to the user first
  • ❌ Do not invent content not in the source
  • ❌ Do not skip frontmatter updates (sources: and updated:)
  • ❌ Do not leave [[wikilinks]] dangling — if you link to a non-existent page, create it as a stub in the same changeset
  • ❌ Do not batch > 15 page updates without breaking into smaller chunks
  • ❌ Do not forget to update wiki/index.md when adding new pages
  • ❌ Do not forget to log the ingest in wiki/log.md

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.