Standard change process for the LLM Wiki engine. Every feature change follows 5 phases: Concept → Verify → Implement → Document → Visualize. Use for any new feature, pipeline change, or script modification.
EnglishSync docs/PROCESS.md with the actual implementation. Reads all scripts, hooks, prompts, and config files, then updates docs/PROCESS.md to reflect reality. Use when scripts have changed, new features were added, or to verify documentation accuracy.
EnglishDiscover and use a locally-available LLM-wiki through its wiki CLI — from any project, not just inside the vault. Read the knowledge base to ground answers in the operator's own compiled knowledge; diagnose pipeline health; contribute back (capture context, record a hard fact, ingest a source); run maintenance (compile, lint, review); or report engine bugs upstream. Step 1 locates the wiki (env var, walk-up, or registry) — if none is found, the skill does not apply and exits cleanly. Use when: an agent in any project should consult, feed, diagnose, or report on the operator's knowledge base — "check the wiki", "what does my wiki say about X", "add this to the wiki", "ingest this", "compile the wiki", "wiki health", "vault status", "is the pipeline healthy", "file a bug against the engine", "report this to lx-0/llm-wiki".
English
AGENT SKILLS ATLASIncludes LLM Wiki Change, Sync Process Docs, and Use LLM Wiki.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
LLM Wiki Change
Standard change process for the LLM Wiki engine. Every feature change follows 5 phases: Concept → Verify → Implement → Document → Visualize. Use for any new feature, pipeline change, or script modification. Trigger: "llm-wiki change", "wiki change", "engine change", "neues feature", "pipeline ändern"
Sync Process Docs
Sync docs/PROCESS.md with the actual implementation. Reads all scripts, hooks, prompts, and config files, then updates docs/PROCESS.md to reflect reality. Use when scripts have changed, new features were added, or to verify documentation accuracy. Trigger: "sync process docs", "update process", "process docs aktualisieren"
Use LLM Wiki
Discover and use a locally-available LLM-wiki through its wiki CLI — from any project, not just inside the vault. Read the knowledge base to ground answers in the operator's own compiled knowledge; diagnose pipeline health; contribute back (capture context, record a hard fact, ingest a source); run maintenance (compile, lint, review); or report engine bugs upstream. Step 1 locates the wiki (env var, walk-up, or registry) — if none is found, the skill does not apply and exits cleanly. Use when: an agent in any project should consult, feed, diagnose, or report on the operator's knowledge base — "check the wiki", "what does my wiki say about X", "add this to the wiki", "ingest this", "compile the wiki", "wiki health", "vault status", "is the pipeline healthy", "file a bug against the engine", "report this to lx-0/llm-wiki".
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the LLM Wiki Change skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.