llm-wiki-skill-compiler

llm-wiki-skill-compiler is a skill for Claude Code, Codex from po4yka/llm-wiki-skills. It costs 56 tokens per session (847 once invoked), scanned A, original, MIT.

A workflow that turns reusable step-by-step knowledge from an LLM-Wiki into installable Agent Skills. Agent Skills are instruction files that coding agents can trigger for recurring tasks.

In plain words
What is it for?
Use it to identify useful runbooks, checklists, troubleshooting guides, or repeated query answers and propose or write SKILL.md files from them.
Why use it?
It prevents teams from repeatedly rediscovering the same procedure or hiding important domain knowledge in prompts. The resulting skills retain evidence links and include validation.

Skill for Claude CodeCodex

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

Good fit Use it to identify useful runbooks, checklists, troubleshooting guides, or repeated query answers and propose or write SKILL.md files from them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add po4yka/llm-wiki-skills --skill llm-wiki-skill-compiler
Clone the repo
git clone --depth 1 https://github.com/po4yka/llm-wiki-skills

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 llm-wiki-skill-compiler

README.md
[![agentmods](https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler/github.svg)](https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler)
Your own site
<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler/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.

agentmods 80×15 button for llm-wiki-skill-compiler

Your own site · 80×15
<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-skill-compiler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 847 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.00056 $0.00847
Opus 5 $0.00028 $0.00424
Sonnet 5 $0.00011 $0.00169
Haiku 4.5 $0.00006 $0.00085

Measured 12d ago against content hash 8132bf4415e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

llm-wiki-skill-compiler 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 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/audit-skills.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/llm-wiki-skill-compiler/SKILL.md · 130 lines

How it starts

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

LLM-Wiki Skill Compiler

Goal

Turn reusable procedural knowledge from the wiki into small, triggerable Agent Skills without moving domain knowledge into hidden prompts.

When to use

  • A wiki page or folder captures a repeated step-by-step workflow, runbook, checklist, or troubleshooting routine worth reusing across sessions or agents.
  • A saved query answer keeps getting re-asked and should become a triggerable skill instead of a synthesis note.
  • An existing skills/ directory needs a new candidate evaluated against skills.sh.json before writing anything.
  • Someone wants to compile a batch of wiki pages into SKILL.md files and needs the propose-only vs. write-mode boundary made explicit first.
  • Do not use this skill to answer a one-off question or to publish domain facts as-is; use it only when the target output is a procedural, triggerable skill.

Inputs

  • Candidate wiki pages or folders.
  • Existing skills/ directory.
  • skills.sh.json if present.
  • Target agent(s).
  • Desired mode: propose-only or write skill files.

Procedure

1. Find procedural candidates

Search for pages containing:

  • step-by-step workflows;
  • repeated troubleshooting routines;
  • runbooks;
  • checklists;
  • project conventions;
  • saved query answers that are reused;
  • scripts or command sequences.

2. Separate procedure from knowledge

Keep in the skill:

  • trigger conditions;
  • required inputs;
  • deterministic procedure;
  • output contract;
  • safety gates.

Keep in the wiki or references:

  • domain facts;
  • long examples;
  • historical background;
  • volatile current-state claims;
  • source excerpts.

3. Design skill boundary

For each candidate, propose:

| Candidate | Skill name | Trigger | Inputs | Risks | Evidence pages |
|---|---|---|---|---|---|

Use one skill per coherent user intent. Do not create one giant skill.

4. Generate SKILL.md

Create valid frontmatter:

---
name: example-skill
description: Trigger-rich description.
license: MIT
compatibility: Designed for Agent Skills-compatible coding agents.
metadata:
  author: po4yka
  version: "0.1.0"
  install_scope: self-contained
---

Read the full file on GitHub · 130 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 130 lines · 56 tokens per session scan A 8132bf4415e3

Subscribe to this mod's changes

llm-wiki-skill-compiler is a skill published in the GitHub repository po4yka/llm-wiki-skills (3 stars, last pushed 19d ago), licensed MIT. It adds 56 tokens to every session and 847 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

okf-harness-bootstrap

This unified entrypoint routes setup and workspace maintenance without making the user choose a mode.

pumblus/okf-harness · 0 tokens

okf-harness

One Door routes OKF Harness workspace requests to exactly one internal workflow at a time.

pumblus/okf-harness · 0 tokens

wiki-lint

Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…

tboome33/obsidian-mcp-router · 119 tokens

meta-sync-template

Interactive flow to propagate the reference (.template) vault's plugins, snippets, and root docs to one or more configured vaults. Reads the active router config, lists every vault with online status, flags vaults missing obsidian-local-rest-api upfront, lets the user pick all or a subset, and optionally re-clones…

tboome33/obsidian-mcp-router · 159 tokens

save

File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…

tboome33/obsidian-mcp-router · 112 tokens

wiki-boundary

Rank the "frontier" pages of a wiki — the crossroads many pages link to that stay thin inside — so you can decide where research would pay off most. Use when the user says "what should I write about next", "where are the gaps", "which pages need work", "find the thin hub pages", "boundary pages", "/wiki-boundary"…

tboome33/obsidian-mcp-router · 141 tokens