llm-wiki-interview

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

An agent-led interview process that turns a person's undocumented project knowledge into draft pages for an LLM-Wiki, a wiki designed to help language models use project information.

In plain words
What is it for?
Finding onboarding gaps and unanswered questions, preparing focused interview questions, and turning answers or transcripts into reviewable draft wiki pages.
Why use it?
It captures decisions, explanations, and answers that are missing from written documentation without presenting personal statements as verified facts.

Skill for Claude CodeCodex

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

Good fit Finding onboarding gaps and unanswered questions, preparing focused interview questions, and turning answers or transcripts into reviewable draft wiki pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/po4yka/llm-wiki-skills/llm-wiki-interview
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-interview
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-interview

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-interview"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 670 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.00058 $0.00670
Opus 5 $0.00029 $0.00335
Sonnet 5 $0.00012 $0.00134
Haiku 4.5 $0.00006 $0.00067

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

Security

Grade A, and why

llm-wiki-interview 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.

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-interview/SKILL.md · 113 lines

How it starts

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

LLM-Wiki Interview

Goal

Use targeted questions to capture a person's tacit knowledge into draft, reviewable wiki pages.

When to use

  • The wiki has open questions, sparse concept pages, or pages marked review_required.
  • Onboarding gaps keep producing the same repeated questions from new contributors.
  • A decision page is missing its rationale, history, or trade-offs.
  • The user hands over a voice-note or transcript that should become draft wiki pages.
  • A lint report or contradiction check surfaces a gap only a person can fill in.

Inputs

  • wiki/index.md, wiki/log.md, open questions and lint reports.
  • Target domain or project.
  • Interview mode: plan questions, conduct interview, or file answers.
  • Optional transcript or voice-note text.

Procedure

1. Find weak areas

Look for:

  • open questions;
  • sparse concept pages;
  • onboarding gaps;
  • contradictions;
  • pages marked review_required;
  • repeated user questions;
  • decision pages missing rationale.

Search wiki/index.md and wiki/log.md for prior interview answers before drafting new questions, so the interview does not re-ask what is already captured.

2. Prepare focused questions

Ask 5-10 questions at a time. Prefer questions that extract:

  • constraints;
  • history;
  • rationale;
  • exceptions;
  • gotchas;
  • examples;
  • terminology;
  • decision trade-offs.

3. Capture answers as draft knowledge

Store interview-derived knowledge as:

  • type: query for Q&A;
  • type: synthesis for human interpretation;
  • type: concept or entity only when the answer clearly belongs there.

Mark:

status: draft
review_required: true
claim_mix:
  extracted: 0.0
  inferred: 0.0
  ambiguous: 0.0

Use interview or human-memory source tags. Do not treat interview answers as external facts.

4. Separate human synthesis

Preserve answers under human-owned sections when they represent the person's interpretation.

5. Update navigation

Add important pages to wiki/index.md and append to wiki/log.md if writing files.

Read the full file on GitHub · 113 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. 12d ago First seen · 113 lines · 58 tokens per session scan A 6d98828ba967

Subscribe to this mod's changes

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

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

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-export

Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…

tboome33/obsidian-mcp-router · 129 tokens

wiki-query

Answer a question using ONLY the existing wiki vault as the knowledge base — no web search, no general LLM knowledge. Reads hot.md first (cheap recent context), then catalog.md to navigate, then drills into specific pages, then optionally semantic-searches the wiki, and synthesizes an answer with citations. Use when…

tboome33/obsidian-mcp-router · 129 tokens

wiki-fold

Roll up the wiki's journal.md entries into structured fold pages — like 2^k log compaction. Reads the last 2, 4, 8, 16... entries and writes a fold page that summarizes them by extractive summarization (no invention), with backlinks to children. Idempotent at the structural level — re-running with the same window…

tboome33/obsidian-mcp-router · 125 tokens

wiki

Bootstrap or check a Karpathy-style "LLM wiki" structure inside an Obsidian vault — a self-maintaining knowledge base where pages reference each other and the LLM keeps it tidy. Sets up catalog.md (curated page catalog), journal.md (append-only operation history), hot.md (recent-context cache), and overview.md…

tboome33/obsidian-mcp-router · 134 tokens