A setup procedure for a Logseq wiki, including its folders, indexes, tracking files, and theme directories. It first examines existing pages to find themes and possible naming conflicts.

Use it to initialize a wiki from existing Logseq pages, detect project themes, and prepare the wiki structure after reviewing a dry-run report.

It removes the manual work of organizing a new wiki and reveals conflicts before writing files. It also supports vault paths containing spaces or special characters.

How ystreibel/logseq-wiki configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to ystreibel/logseq-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ystreibel/logseq-wiki/main/.skills/wiki-setup/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ystreibel/logseq-wiki

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-setup/github.svg)](https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-setup)

Your own site

<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-setup"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-setup"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,418 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00066	$0.01418
Opus 5.5	$0.00026	$0.00567
Sonnet 5.5	$0.00013	$0.00284
Haiku 4.5	$0.00007	$0.00142

Measured 2mo ago against content hash 5bf571c9f5a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wiki-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.skills/wiki-setup/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Logseq Setup — Initialisation du wiki

REQUIRED: Invoke llm-wiki skill first for Logseq syntax and file format rules.

Règle paths : Tous les chemins lus depuis LOGSEQ_VAULT_PATH doivent être quotés dans les commandes shell (ex: "$LOGSEQ_VAULT_PATH/pages/") pour supporter les espaces et caractères spéciaux (OneDrive, chemins Windows via WSL).

Étape 0 : Analyse préliminaire (dry-run)

Avant toute écriture, effectuer une analyse complète et demander confirmation.

Lister les fichiers pages/*.md (exclure contents.md, excalidraw-*.md, hls__*.md)
Détecter les thèmes candidats : identifier les sections ## dans les pages pour extraire les thèmes/projets principaux
Détecter les collisions : vérifier si un nom de thème candidat correspond déjà à un fichier existant dans pages/ (ex : thème "capsule" ET pages/capsule.md → conflit). Lister toutes les collisions détectées.
Lire wiki/_meta/exclusions.yml si présent — appliquer les exclusions (thèmes listés dans themes: sont à exclure de la détection)

Afficher le rapport dry-run :

Thèmes détectés     : [liste]
Collisions          : [liste ou "aucune"]
Exclusions actives  : [liste ou "aucune"]
Fichiers à créer    : wiki/_master-index.md, wiki/_log.md, wiki/_manifest.json,
                      wiki/_meta/taxonomy.md, wiki/_meta/exclusions.yml,
                      wiki/[thème]/_index.md (×N)

Demander confirmation : "Confirmes-tu la création de ces fichiers ?" — ne pas continuer sans réponse affirmative.

Étape 1 : Vérifier l'état actuel

Lire wiki/_manifest.json si il existe
Si le manifest existe et contient des sources ingérées : avertir l'utilisateur que le wiki existe déjà et demander confirmation avant de continuer
Si wiki/ existe mais est vide : procéder sans confirmation

Étape 2 : Détecter les thèmes

Lire tous les fichiers pages/*.md (sauf contents.md, excalidraw-*.md, hls__*.md). Pour chaque fichier, identifier les thèmes/projets principaux en lisant les titres de niveau 2 (## ). Ce sont les candidats pour les sous-dossiers wiki.

Read the full file on GitHub · 186 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 186 lines · 66 tokens per session scan A 5bf571c9f5a8

Subscribe to this mod's changes

wiki-setup is a skill published in the GitHub repository ystreibel/logseq-wiki (5 stars, last pushed 11d ago), licensed MIT. It adds 66 tokens to every session and 1,418 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Documents

wiki-setup next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wiki-setupystreibel/logseq-wiki	Skill	5	11d ago	MIT	A	66	Claude Code, Codex
orbit-notionnexu-io/open-design	Skill	106k	today	Apache-2.0	A	117	Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	2d ago	Apache-2.0	A	123	Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	48	Claude Code
legal-holdanthropics/claude-for-legal	Skill	9.9k	3d ago	Apache-2.0	A	68	Claude Code
ppt-reviewOrkas-AI/Orkas	Skill	9.0k	today	MIT	A	2	Claude Code, Codex
feishuHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	33	Claude Code, Codex

logseq-wiki: Skill for Claude Code