logseq-wiki: Skill for Claude Code

.skills/wiki-setup/SKILL.md

wiki-setup is a skill for Claude Code, Codex from ystreibel/logseq-wiki. It costs 66 tokens per session (1,418 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it to initialize a wiki from existing Logseq pages, detect project themes, and prepare the wiki structure after reviewing a dry-run report.
Why use it?
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.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is ystreibel/logseq-wiki's own configuration. It tells Claude Code and Codex how to work on logseq-wiki itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything logseq-wiki configures →

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.

agentmods badge for wiki-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-setup.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.svg" alt="Measured on agentmods" 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.01418
Opus 5 $0.00033 $0.00709
Sonnet 5 $0.00013 $0.00284
Haiku 4.5 $0.00007 $0.00142

Measured 7d ago against content hash 5bf571c9f5a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 7d 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.

  1. Lister les fichiers pages/*.md (exclure contents.md, excalidraw-*.md, hls__*.md)
  2. Détecter les thèmes candidats : identifier les sections ## dans les pages pour extraire les thèmes/projets principaux
  3. 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.
  4. Lire wiki/_meta/exclusions.yml si présent — appliquer les exclusions (thèmes listés dans themes: sont à exclure de la détection)
  5. 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)
    
  6. 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.

  1. 7d 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 (4 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. 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.

Related

Other skills, from other repositories

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

read

Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…

tw93/Waza · 78 tokens

overleaf-sync

A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.

wanshuiyin/Auto-claude-code-research-in-sleep · 97 tokens