skill

Name: skill
Author: LiyuanW21

15stars3forks

How to install skill?

liyuanw21/obsidian-wiki-system/skill

$npx -y skills add LiyuanW21/obsidian-wiki-system --skill skill

Installs into the current project.

Summary

Initialize or maintain a reusable Obsidian wiki knowledge iteration system with raw inbox, wiki pages, source/concept/synthesis/project templates, workflows, prompts, indexes, logs, and AGENTS.md rules. Use in Codex, OpenCode, or any agent that can read skill folders when the use

Files · 1

View on GitHub

SKILL.md

1	# Obsidian Wiki System
2
3	Use this skill to scaffold or maintain an Obsidian vault that follows the `raw -> wiki -> index/log` knowledge iteration loop.
4
5	This folder is agent-portable: use the same `SKILL.md`, `references/`, and `assets/` in Codex, OpenCode, or another agent skill system that can access local files.
6
7	## Scaffold Workflow
8
9	1. Inspect the target folder first. Preserve any existing user notes.
10	2. Read `references/language.md` and choose the vault language from the user's request, existing notes, or locale.
11	3. Read `references/structure.md` for the directory model and required files.
12	4. Copy the selected template into the target vault:
13	- Chinese: `assets/vault-template-zh/`.
14	- English: `assets/vault-template-en/`.
15	- Other languages: copy the closest template and localize user-facing prose.
16	5. Replace placeholders:
17	- `{{date}}` with the current local date.
18	- `{{vault_name}}` with the target folder name unless the user provides a name.
19	6. If target files already exist, merge conservatively instead of overwriting. Ask before replacing meaningful content.
20	7. Configure Obsidian templates and daily notes if `.obsidian/` exists or the user wants Obsidian-native setup.
21	8. Tell the user to start from the localized entry page, such as `首页.md` or `Home.md`.
22
23	## Maintenance Workflow
24
25	1. Read the vault `AGENTS.md`, localized entry page such as `首页.md` or `Home.md`, `wiki/index.md`, and `ops/workflows.md`.
26	2. For new materials, put originals in `raw/inbox/` and create processed pages in `wiki/sources/`.
27	3. Extract durable ideas into `wiki/concepts/`, questions into `wiki/questions/`, projects into `wiki/projects/`, and cross-source conclusions into `wiki/syntheses/`.
28	4. Update `wiki/index.md` for important new pages.
29	5. Update `wiki/log.md` after structure changes, major pages, or agent-stack changes.
30	6. Use `ops/prompts/ingest-source.md`, `query-wiki.md`, and `lint-wiki.md` as reusable operating prompts.
31
32	## Boundaries
33
34	- `raw/` may be messy; `wiki/` should become increasingly clear.
35	- Do not turn unsupported excerpts into facts. Mark uncertain points as `待验证`.
36	- Prefer `[[wikilinks]]` for internal vault pages.
37	- Keep source pages traceable: every important claim should link back to a source or be labeled as inference.
38	- Do not install unrelated plugins, MCPs, or external tools unless the user asks.

People who liked this also viewed

6 picks

Type

skill

15stars3forks

View on GitHub

How to install skill?

liyuanw21/obsidian-wiki-system/skill

$npx -y skills add LiyuanW21/obsidian-wiki-system --skill skill

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Obsidian Wiki System
2
3	Use this skill to scaffold or maintain an Obsidian vault that follows the `raw -> wiki -> index/log` knowledge iteration loop.
4
5	This folder is agent-portable: use the same `SKILL.md`, `references/`, and `assets/` in Codex, OpenCode, or another agent skill system that can access local files.
6
7	## Scaffold Workflow
8
9	1. Inspect the target folder first. Preserve any existing user notes.
10	2. Read `references/language.md` and choose the vault language from the user's request, existing notes, or locale.
11	3. Read `references/structure.md` for the directory model and required files.
12	4. Copy the selected template into the target vault:
13	- Chinese: `assets/vault-template-zh/`.
14	- English: `assets/vault-template-en/`.
15	- Other languages: copy the closest template and localize user-facing prose.
16	5. Replace placeholders:
17	- `{{date}}` with the current local date.
18	- `{{vault_name}}` with the target folder name unless the user provides a name.
19	6. If target files already exist, merge conservatively instead of overwriting. Ask before replacing meaningful content.
20	7. Configure Obsidian templates and daily notes if `.obsidian/` exists or the user wants Obsidian-native setup.
21	8. Tell the user to start from the localized entry page, such as `首页.md` or `Home.md`.
22
23	## Maintenance Workflow
24
25	1. Read the vault `AGENTS.md`, localized entry page such as `首页.md` or `Home.md`, `wiki/index.md`, and `ops/workflows.md`.
26	2. For new materials, put originals in `raw/inbox/` and create processed pages in `wiki/sources/`.
27	3. Extract durable ideas into `wiki/concepts/`, questions into `wiki/questions/`, projects into `wiki/projects/`, and cross-source conclusions into `wiki/syntheses/`.
28	4. Update `wiki/index.md` for important new pages.
29	5. Update `wiki/log.md` after structure changes, major pages, or agent-stack changes.
30	6. Use `ops/prompts/ingest-source.md`, `query-wiki.md`, and `lint-wiki.md` as reusable operating prompts.
31
32	## Boundaries
33
34	- `raw/` may be messy; `wiki/` should become increasingly clear.
35	- Do not turn unsupported excerpts into facts. Mark uncertain points as `待验证`.
36	- Prefer `[[wikilinks]]` for internal vault pages.
37	- Keep source pages traceable: every important claim should link back to a source or be labeled as inference.
38	- Do not install unrelated plugins, MCPs, or external tools unless the user asks.

People who liked this also viewed

6 picks

Type