karlorz/llm-wiki · Archived

wiki-init

Bootstrap a CodeWiki vault — domain-aware SCHEMA.md, index.md, log.md, and ~/.skillwiki/.env binding. Use when starting a fresh vault.

First seen Jul 27, 2026

Installation

$ npx skills add karlorz/llm-wiki --skill wiki-init

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from karlorz/llm-wiki · top by installs.

npx skills add karlorz/llm-wiki

Browse all from karlorz/llm-wiki

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,766 B
  • docs SUMMARY.md 153 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

wiki-init

When This Skill Activates

  • User asks to create, build, or start a vault, wiki, or knowledge base.
  • The resolved vault path (see step 0) does not yet contain SCHEMA.md.

Pre-orientation reads

None for the first run.

Steps

  1. Resolve target. Run skillwiki path --init-time to see what target the CLI will pick. Confirm with the user, or override with --target <dir>.
  2. Verify target is empty or has no SCHEMA.md.
  3. Ask the domain question: "What knowledge domain will this vault cover? Be specific."
  4. Propose a 10–15 tag taxonomy tailored to the domain. Confirm or accept the user's revision.
  5. Ask the language question: "What language should generated page prose use? Default is en. Aliases like chinese-traditional or zh-Hant are accepted."
  6. Run skillwiki init --target <dir> --domain "<answer>" --taxonomy "<comma list>" --lang "<lang>".

Init always writes or merges a vault .gitignore for GitHub-sync hygiene (work-complete journals, last-op, locks, memory/graph caches). It does not ignore session-brief.* or agent-memory-trends/. Pass --no-gitignore only when the user explicitly does not want that file. For an existing vault: skillwiki init --target <dir> --domain existing --write-gitignore.

  1. Report the installed Web Clipper assets at

Templates/web-clipper/llm-wiki-clippings.json and Templates/web-clipper/readme.txt. Tell the user to open Obsidian Web Clipper Settings, import the JSON, and repeat the import for every browser profile that should capture into the vault. Re-init preserves existing customized copies, including short files.

  1. Explain that the generic template preserves {{content}}; remote HTTP(S)

images remain external dependencies. An attended local-asset capture may choose any URL-friendly path under raw/assets/, but it must write the asset, emit an explicit vault-qualified ![[raw/assets/...]] embed, verify resolution/preview, and only then finalize the immutable raw note.

  1. Suggest first sources. Propose 3–5 initial sources (URLs, papers, articles) appropriate to the domain. Prompt the user to provide the first one to ingest, then hand off to wiki-ingest.

Stop conditions

  • Target non-empty and --force not consented.
  • ~/.skillwiki/.env already binds a different vault or language and --force not consented.

Forbidden

  • Modifying anything outside the target directory or ~/.skillwiki/.env.
  • Writing to ~/.hermes/.env (read-only fallback).
  • Running any LLM-driven content generation in this skill.