wiki-config

Name: wiki-config
Author: vanillaflava

56stars7forks

How to install wiki-config?

vanillaflava/llm-wiki-skills/wiki-config

$npx -y skills add vanillaflava/llm-wiki-skills --skill wiki-config

Installs into the current project.

Summary

Set up, validate, and reconfigure the llm-wiki skill suite. Always use this skill when the user says /wiki-config, asks to 'set up my wiki', 'configure wiki', 'initialize wiki config', mentions 'page structure problems', 'schema issues', 'missing templates', 'wiki help', 'how doe

Files · 1

View on GitHub

SKILL.md

1	# Wiki Config
2
3	Interactive setup, validation, and maintenance for `wiki-config.md`. Pairs with the five operational wiki skills (wiki-ingest, wiki-lint, wiki-integrate, wiki-crystallize, wiki-query) which all read the same config.
4
5	---
6
7	## Capability Requirements
8
9	Filesystem read, write, search, and directory creation. If running on a surface without filesystem tools, inform the user and stop.
10
11	---
12
13	## Workflow
14
15	### Step 0 - Welcome & Initialization
16
17	Every time wiki-config is invoked, start here.
18
19	#### Show the wiki skill ecosystem
20
21	Check which wiki skills are available in this session. Scan the `<available_skills>` section in your context for skills matching the `wiki-*` pattern (wiki-config, wiki-ingest, wiki-query, wiki-lint, wiki-integrate, wiki-crystallize). Skills found in `<available_skills>` are enabled and usable - mark as ✓. Skills not found are either not installed or toggled off in the user's settings - mark as ✗.
22
23	Present this table with actual status for each skill:
24
25	```
26	## Wiki Skill Ecosystem
27
28	\| Skill \| Status \| What it does \|
29	\|---\|---\|---\|
30	\| wiki-config \| ✓ \| Interactive setup and validation \|
31	\| wiki-ingest \| [✓/✗] \| Process raw/ → wiki pages → ingested/ \|
32	\| wiki-query \| [✓/✗] \| Search wiki, cite sources, file good answers \|
33	\| wiki-lint \| [✓/✗] \| Health checks: broken links, orphans \|
34	\| wiki-integrate \| [✓/✗] \| Add backlinks when pages change \|
35	\| wiki-crystallize \| [✓/✗] \| Distil conversations into wiki pages \|
36	```
37
38	If any are missing: "Install from https://github.com/vanillaflava/llm-wiki-skills for the full ecosystem."
39
40	The bundled `references/setup-help.md` is available throughout this session. Read it if you need more orientation context, if a user asks detailed questions about the wiki system, or if you get stuck.
41
42	#### Present the welcome message
43
44	"Let me read the setup guide to orient us both..."
45
46	Then present:
47
48	---
49
50	> Welcome to your LLM-Wiki
51	>
52	> Before we start, a quick orientation:
53
54	> Filesystem access scope - The directory your filesystem tool can reach. This is the outer boundary. Scope your tool tightly; broad access is a privacy risk.
55	>
56	> Wiki root - The folder inside that scope containing your Markdown notes and wiki system files (`wiki-config.md`, `wiki-help.md`, `Home.md`, `Overview.md`, `index.md`, `log.md`, `raw\`, `ingested\`, `templates\`). This is where you keep your `.md` files - a subset of your Obsidian vault, your Logseq graph, or wherever you maintain notes. Skills find wiki root by looking for `wiki-config.md`.
57
58	> Important: Wiki root should not be your machine root (`C:\`, `/`) or user home - those are privacy risks. It also doesn't need to be your entire vault or graph.
59	>
60	> We recommend setting wiki root as a subdirectory of your knowledge base - only the folders you're comfortable sharing with an agent.
61	>
62	> The wiki works with your existing notes and helps you synthesize sources (PDFs, articles, documents) into interlinked wiki pages. Each source you add and each question you ask makes the knowledge base richer - it compounds over time.
63
64	---
65
66	If the user seems uncertain or asks for more context, offer: "Want me to show you the full setup guide?" Then read and present `references/setup-help.md`.
67
68	Otherwise proceed to assess state.
69
70	#### Assess state and branch
71
72	Check filesystem scope:
73
74	Identify your filesystem scope root - the top-level directory your filesystem tool can access.
75
76	If scope is insensible (bare drive root, OS root, or user home):
77
78	"Your filesystem access is set to `[scope]` - this is very broad and a privacy risk. I recommend scoping to just your wiki folder after setup.
79
80	I need an absolute path to your wiki root. Examples:
81	- Windows: `C:\Users\YourName\Documents\wiki`
82	- Mac: `/Users/YourName/Documents/wiki`
83
84	What's the path?"
85
86	Privacy discipline: Never list users or enumerate system folders. Ask for path directly.
87
88	If scope is sensible: Search for `wiki-config.md` recursively (max 5 levels deep).
89
90	Branch based on findings:
91
92	→ Config not found - "You don't have a wiki yet. I'll walk you through setup." → Step 2 (Init)
93
94	→ Config found - Read it, then run a full environment c

People who liked this also viewed

6 picks

Type

wiki-config

56stars7forks

View on GitHub

How to install wiki-config?

vanillaflava/llm-wiki-skills/wiki-config

$npx -y skills add vanillaflava/llm-wiki-skills --skill wiki-config

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Wiki Config
2
3	Interactive setup, validation, and maintenance for `wiki-config.md`. Pairs with the five operational wiki skills (wiki-ingest, wiki-lint, wiki-integrate, wiki-crystallize, wiki-query) which all read the same config.
4
5	---
6
7	## Capability Requirements
8
9	Filesystem read, write, search, and directory creation. If running on a surface without filesystem tools, inform the user and stop.
10
11	---
12
13	## Workflow
14
15	### Step 0 - Welcome & Initialization
16
17	Every time wiki-config is invoked, start here.
18
19	#### Show the wiki skill ecosystem
20
21	Check which wiki skills are available in this session. Scan the `<available_skills>` section in your context for skills matching the `wiki-*` pattern (wiki-config, wiki-ingest, wiki-query, wiki-lint, wiki-integrate, wiki-crystallize). Skills found in `<available_skills>` are enabled and usable - mark as ✓. Skills not found are either not installed or toggled off in the user's settings - mark as ✗.
22
23	Present this table with actual status for each skill:
24
25	```
26	## Wiki Skill Ecosystem
27
28	\| Skill \| Status \| What it does \|
29	\|---\|---\|---\|
30	\| wiki-config \| ✓ \| Interactive setup and validation \|
31	\| wiki-ingest \| [✓/✗] \| Process raw/ → wiki pages → ingested/ \|
32	\| wiki-query \| [✓/✗] \| Search wiki, cite sources, file good answers \|
33	\| wiki-lint \| [✓/✗] \| Health checks: broken links, orphans \|
34	\| wiki-integrate \| [✓/✗] \| Add backlinks when pages change \|
35	\| wiki-crystallize \| [✓/✗] \| Distil conversations into wiki pages \|
36	```
37
38	If any are missing: "Install from https://github.com/vanillaflava/llm-wiki-skills for the full ecosystem."
39
40	The bundled `references/setup-help.md` is available throughout this session. Read it if you need more orientation context, if a user asks detailed questions about the wiki system, or if you get stuck.
41
42	#### Present the welcome message
43
44	"Let me read the setup guide to orient us both..."
45
46	Then present:
47
48	---
49
50	> Welcome to your LLM-Wiki
51	>
52	> Before we start, a quick orientation:
53
54	> Filesystem access scope - The directory your filesystem tool can reach. This is the outer boundary. Scope your tool tightly; broad access is a privacy risk.
55	>
56	> Wiki root - The folder inside that scope containing your Markdown notes and wiki system files (`wiki-config.md`, `wiki-help.md`, `Home.md`, `Overview.md`, `index.md`, `log.md`, `raw\`, `ingested\`, `templates\`). This is where you keep your `.md` files - a subset of your Obsidian vault, your Logseq graph, or wherever you maintain notes. Skills find wiki root by looking for `wiki-config.md`.
57
58	> Important: Wiki root should not be your machine root (`C:\`, `/`) or user home - those are privacy risks. It also doesn't need to be your entire vault or graph.
59	>
60	> We recommend setting wiki root as a subdirectory of your knowledge base - only the folders you're comfortable sharing with an agent.
61	>
62	> The wiki works with your existing notes and helps you synthesize sources (PDFs, articles, documents) into interlinked wiki pages. Each source you add and each question you ask makes the knowledge base richer - it compounds over time.
63
64	---
65
66	If the user seems uncertain or asks for more context, offer: "Want me to show you the full setup guide?" Then read and present `references/setup-help.md`.
67
68	Otherwise proceed to assess state.
69
70	#### Assess state and branch
71
72	Check filesystem scope:
73
74	Identify your filesystem scope root - the top-level directory your filesystem tool can access.
75
76	If scope is insensible (bare drive root, OS root, or user home):
77
78	"Your filesystem access is set to `[scope]` - this is very broad and a privacy risk. I recommend scoping to just your wiki folder after setup.
79
80	I need an absolute path to your wiki root. Examples:
81	- Windows: `C:\Users\YourName\Documents\wiki`
82	- Mac: `/Users/YourName/Documents/wiki`
83
84	What's the path?"
85
86	Privacy discipline: Never list users or enumerate system folders. Ask for path directly.
87
88	If scope is sensible: Search for `wiki-config.md` recursively (max 5 levels deep).
89
90	Branch based on findings:
91
92	→ Config not found - "You don't have a wiki yet. I'll walk you through setup." → Step 2 (Init)
93
94	→ Config found - Read it, then run a full environment c

People who liked this also viewed

6 picks

Type