Token导航 LogoToken导航TokenDH.com
前端设计需要联网github未标认证来源可访问许可证需确认审计通过

llm-wikiLLM Wiki

Agent Skill

llm-wiki 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

192

周安装

8

GitHub Stars

1

下载量

64
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:llm-wiki(LLM Wiki)
来源仓库:https://github.com/godstale/llm-wiki
仓库路径:skills/llm-wiki
安装命令:
npx skills add https://github.com/godstale/llm-wiki --skill llm-wiki
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/godstale/llm-wiki --skill llm-wiki

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,支持项目状态跟踪。

  • 适用于围绕仓库变更、代码审查或团队协作事项进行信息整理。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态及是否触发联网或文件操作。
  • llm-wiki 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

LLM Wiki

Agent-maintained personal knowledge base: ingest → query → lint → graph.

Ontology is opt-in. If wiki/ontology.yaml does not exist, all commands work exactly as described below. Ontology features are additive — see references/ontology-commands.md.

Project Layout

raw/          # Drop zone for unprocessed docs (originals stay after ingest)
wiki/
  index.md          # Catalog of all pages — update on every ingest
  log.md            # Append-only chronological record
  overview.md       # Living synthesis
  history.json      # Registry of all ingested sources
  ontology.yaml     # (OPTIONAL) project ontology schema
  synthesis-map.md  # Lightweight index of all saved query syntheses (append-only)
  originals/        # Read-only archive of source docs
  sources/          # One summary page per source (kebab-case.md)
  entities/         # People, companies, projects, products (TitleCase.md)
  concepts/         # Ideas, frameworks, methods, theories (TitleCase.md)
  syntheses/        # Saved query answers (kebab-case.md)
graph/              # graph.json + graph.html

Page templates and frontmatter schema → see references/templates.md. Wikilinks are case-sensitive: [[PageName]].


/wiki-ingest

Arguments (all optional):

  • *(none)* → batch-ingest all files in raw/
  • <file> → single file (e.g. raw/my-article.md)
  • --from <folder> → use custom source folder instead of raw/
  • --to <folder> → copy originals to PARA-structured subfolder (not wiki/originals/)
  • --no-copy → skip copying originals; incompatible with --to
  • --force-new → always create new entry (date-suffix slug if duplicate); mutually exclusive with --force-update
  • --force-update → always overwrite existing entry; mutually exclusive with --force-new
  • --no-interview → skip ontology Context Interview
  • --batch-defaults → reuse first file's interview answers as defaults for the rest
  • --summary-only → extract summary + metadata only; skip full-text conversion

For batch mode, --to PARA rules, file pre-processing (pdf/docx/pptx/xlsx), summary-only strategy, Context Interview → read references/ingest-advanced.md

Ingest Strategy (quick reference)

ConditionStrategy
--summary-only flagsummary-only
.xlsx / .xlssummary-only
.pptx / .pptsummary-only
.pdf > 30 pagessummary-only
Everything elsefull

Duplicate Detection

Check wiki/history.json for the candidate slug before ingesting:

  • --force-new: append today's date (e.g. my-article-20260421); proceed
  • --force-update: overwrite existing entry; proceed
  • Active slug, no flag: pause and ask — Update / New entry (<slug-YYYYMMDD>) / Cancel
  • Deleted slug: treat as fresh ingest (reuse slug, set status: "active")

Agent-Based Ingest (full strategy)

  1. Read the source file in full
  2. Read wiki/index.md and wiki/overview.md. If wiki/ontology.yaml exists, run Context Interview (see references/ingest-advanced.md) unless --no-interview
  3. Derive title and slug: a. Timestamp filename / empty title — if the filename matches YYYY-MM-DDTHH_MM_SS… or bare YYYY-MM-DD, or the source's title field is empty/whitespace:

- Read the first meaningful content lines (skip blank lines, lone URLs, timestamps) - Generate a concise descriptive title in the source's language (3–7 words) - Slug = kebab-case(title) + -YYYYMMDD date suffix (from file metadata or today) to guarantee uniqueness - If content is < 10 meaningful words or context is unclassifiable, use title 임시메모-YYYYMMDD and assign category 임시메모 b. Named filename — slug = kebab-case(filename, no extension); title = source's title field or first heading

  1. Select template → see references/templates.md
  2. Write wiki/sources/<slug>.md with source_file: wiki/originals/<slug>.md
  3. Copy original to wiki/originals/<slug>.md (skip if --no-copy; apply PARA rules if --to)
  4. Update wiki/index.md:

- Place the entry under the matching category ## section (create section if absent); maintain sections in this order: ## 기술/개발 · ## 업무/프로젝트 · ## 개인/생활 · ## 여행 · ## 임시메모 - Format: - [Title](sources/slug.md) — one-line summary (summary is mandatory — never omit or leave blank) - Classify by dominant content signal: - 기술/개발: code, tools, APIs, programming, software, hardware, dev workflows - 업무/프로젝트: work meetings, job-related memos, company projects, career - 개인/생활: accounts, IDs, passwords, addresses, family, finance, household - 여행: travel plans, trekking, transportation, accommodation, places - 임시메모: < 10 meaningful words, single snippet, or ambiguous context

  1. Update wiki/overview.md — revise living synthesis if warranted
  2. Create/update entity pages in wiki/entities/EntityName.md — when wiki/ontology.yaml exists, derive class: + properties: frontmatter from the matching class definition in the ontology; do not invent fields not declared there
  3. Create/update concept pages in wiki/concepts/ConceptName.md — same ontology-derived frontmatter applies
  4. Flag any contradictions with existing wiki content
  5. Update wiki/history.jsonalways use Write tool (read existing → merge entry → overwrite). Schema → see references/ingest-advanced.md
  6. Append to wiki/log.md: ## [YYYY-MM-DD] ingest | <Title>
  7. Post-ingest: check broken [[wikilinks]], verify all new pages in index, print change summary. If wiki/ontology.yaml exists: print any schema warnings from this ingest as a ⚠ Schema warnings block (unknown class, missing required properties, unknown predicates) — these do not block ingest but should be resolved

/wiki-query

$ARGUMENTS = the question to answer

For structural filters (class:, type:, AND/OR/NOT, dotted field paths like context.phase) → read references/query-advanced.md

  1. Synthesis-map lookup — if wiki/synthesis-map.md exists, read it in full; scan all entries and select the top 2–3 most semantically relevant past syntheses; read those wiki/syntheses/<slug>.md files in full
  2. Read wiki/index.md to identify the most relevant pages
  3. Read up to ~10 most relevant pages
  4. If summaries lack sufficient detail, read the original from the page's source_file field
  5. Present the answer with [[PageName]] wikilink citations; reference matched past syntheses with [[syntheses/slug]] links if they informed the answer
  6. Include ## Sources listing every page and synthesis drawn from
  7. End with: 💾 이 답변을 저장하려면: \/wiki-synthesize``

Empty wiki: *"The wiki is empty. Run /wiki-ingest <file> to add your first source."*


/wiki-synthesize

$ARGUMENTS (optional) = custom slug override (e.g. /wiki-synthesize my-custom-slug)

Saves the most recent /wiki-query answer from this session as a reusable synthesis.

  1. Retrieve the query question and composed answer from the current session context
  2. Generate a kebab-case slug from the query question (or use the provided override)
  3. Extract entities, concepts, and relations from the answer
  4. Write wiki/syntheses/<slug>.md (template: references/templates.md)
  5. Append to wiki/synthesis-map.md (append-only — never edit past entries): ## YYYY-MM-DD | <slug> Query: <one-line question> Entities: Entity1, Entity2,... Concepts: Concept1, Concept2,... Relations: Subject→predicate→Object,... Preview: <one-sentence answer summary>
  6. Append to wiki/log.md: ## [YYYY-MM-DD] query | <question summary>
  7. Output: ✅ Saved synthesis: [[syntheses/<slug>]] — use /wiki-delete <slug> to remove if not needed

No recent query in session: *"No query found in this session. Run /wiki-query <question> first."*


/wiki-lint

python tools/lint.py
python tools/lint.py --save   # save to wiki/lint-report.md

Agent-based checks:

  1. Orphan pages — pages with no inbound [[PageName]] links
  2. Broken links[[WikiLinks]] pointing to non-existent pages
  3. Missing entity pages — names mentioned in 3+ pages but no wiki/entities/ page
  4. Contradictions — read ## Contradictions sections; cross-check flagged claims
  5. Stale summaries — source pages where last_updated < related concept/entity pages
  6. Data gaps — questions the wiki can't answer; suggest source type to fill

Ontology checks (7–12), when wiki/ontology.yaml exists → read references/ontology-commands.md

After report, ask: "Save to wiki/lint-report.md?" Append to wiki/log.md: ## [YYYY-MM-DD] lint | Wiki health check


/wiki-graph

python tools/build_graph.py --open
python tools/build_graph.py --report --save

Agent-based fallback:

  1. Glob every .md in wiki/. Build one node per page: {"id": "wiki/...", "label": "Title", "type": "source|entity|concept|synthesis", "color": "<hex>"} Colors: source #4CAF50 · entity #2196F3 · concept #FF9800 · synthesis #9C27B0
  2. Grep [[wikilinks]]; resolve each to a node id and create an edge
  3. Write graph/graph.json; inline its contents into graph/graph.html (template: references/graph-html.md)

Ontology-aware coloring, typed edges, and phase lanes → read references/ontology-commands.md

Append to wiki/log.md: ## [YYYY-MM-DD] graph | Knowledge graph rebuilt


/wiki-sources

  1. Read wiki/history.json (if missing → *"No sources ingested yet. Run /wiki-ingest <file>."*)
  2. Print table sorted by last_updated desc: Slug Title Ingested Last Updated Status
  3. For each active source, list pages_created, entities_created, concepts_created

/wiki-update <slug>

  1. Read wiki/history.json; error if slug absent or status: "deleted"
  2. Find original at source_file; error if missing
  3. Re-run Agent-Based Ingest steps 1–14 (update mode: do not re-archive original; overwrite source page; merge entity/concept pages)
  4. Update wiki/history.json: set last_updated, refresh entity/concept lists
  5. Append to wiki/log.md: ## [YYYY-MM-DD] wiki-update | <slug>
  6. Output: ✅ Updated source: <slug>. Run /wiki-graph to regenerate the knowledge graph.

/wiki-delete <slug>

  1. Read wiki/history.json; error if absent or already "deleted"
  2. Show what will be deleted and ask for confirmation:

- wiki/sources/<slug>.md, source_file archive, orphaned entity/concept pages

  1. After confirmation: delete source page, archive, and entity/concept pages not referenced by any other source. Update wiki/index.md and wiki/overview.md.
  2. Set "status": "deleted" in wiki/history.json (preserve entry for audit trail)
  3. Append to wiki/log.md: ## [YYYY-MM-DD] wiki-delete | <slug>
  4. Output: ✅ Deleted source: <slug>. Run /wiki-lint to check for remaining broken links.

/wiki-ontology-* commands

Full flow for /wiki-ontology-init, /wiki-ontology-show, /wiki-ontology-validateread references/ontology-commands.md


Key Gotchas

  • wiki/originals/ is read-only — never modify archived files
  • wiki/index.md must be updated every ingest — stale index breaks /wiki-query
  • wiki/log.md is append-only — never edit past entries
  • wiki/history.json: always use Write tool — read existing first, merge, then overwrite
  • wiki/synthesis-map.md is append-only — never edit past entries; keep each entry under ~200 chars per line
  • /wiki-delete never removes shared pages — cross-check references before deleting entity/concept pages
  • Source slugs in sources: frontmatter must exactly match the source filename without extension
  • All scripts run from the wiki project root (python tools/..., not from the scripts directory)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.64%
按下载量换算22

Claude

29.05%
按下载量换算19

Cursor

17.53%
按下载量换算11

Gemini CLI

9.72%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills