ワンクリックでManusで任意のスキルを実行

kb-init

スター3

フォーク0

更新日2026年7月9日 02:37

Initialize, migrate, or repair a review-gated Obsidian knowledge base. Use this skill whenever the user says "kb init", "initialize knowledge base", "repair vault", "migrate an old layout", "add draft/live review gate", "set up briefings", "LLM Wiki", "Karpathy wiki", "Obsidian IDE", "knowledge compiler", "personal knowledge base", "second brain", "初始化知识库", "迁移知识库", "修复知识库结构", "中文优先 wiki", "raw/wiki/output 脚手架", "把这个 vault 搭成中文优先 wiki", or wants a fresh vault or legacy-layout vault brought onto the review-gated contract. Do not use it for normal compile, review, query, or maintenance work once the support layer is already healthy.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

bahayonghang

bahayonghang/obsidian-notes-karpathy

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア開発者コンピュータ・数学職·SOC 15-1252

ファイルエクスプローラー

20 ファイル

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

kb-compile

bahayonghang/obsidian-notes-karpathy

Incrementally compile tracked raw captures into reviewable draft knowledge. Use this skill whenever the user says "compile wiki", "compile kb", "sync drafts", "digest these captures", "turn my clips into drafts", "编译wiki", "更新草稿层", "同步草稿", or wants tracked material under `raw/human/**`, `raw/agents/{role}/**`, bootstrap `raw/*.md`, `raw/**/assets/*`, or `raw/**/data/*` turned into reviewable summaries, topics, concepts, entities, and draft indices. This is also the right skill when Chinese-LLM-Wiki wording such as `来源页`, `主题页`, `实体页`, `综合页草稿`, `整理成来源页`, `补主题页`, or `补实体页草稿` clearly means “build draft pages from raw evidence first.” Do not treat `raw/**/papers/*.pdf` as a normal compile trigger: those paper ingests still belong to `paper-workbench`, and `kb-compile` should only surface or defer them.

2026-07-093

kb-ingest

bahayonghang/obsidian-notes-karpathy

Register and normalize raw source intake for an Obsidian knowledge base. Use this skill whenever the user says "kb ingest", "ingest sources", "refresh manifest", "register new raw files", "scan raw library", "同步素材清单", "登记新来源", "更新 manifest", or wants `raw/**` captures recorded into `raw/_manifest.yaml` before compile runs. Treat browser-side collection as an upstream companion lane: if the source is still on the web and not in `raw/` yet, use `web-access` or Web Clipper first, then come here. Do not use it for draft generation, review, query, or maintenance once the source registry is already current.

2026-07-093

kb-query

bahayonghang/obsidian-notes-karpathy

Query, search, and generate grounded outputs from the approved live layer of an Obsidian vault. Use this skill whenever the user asks what approved notes already say, wants grounded answers, ranked local candidates, archived Q&A reuse, publishable artifacts, or static web exports from `wiki/live/`; says "query kb", "kb-search", "archive this answer", "归档这个回答", "复用旧 Q&A", "写成公众号/thread", "对外内容", "一鱼多吃", "问知识库", or "搜索批准层并回答"; or uses Chinese-LLM-Wiki terms such as `综合页`, `output/analyses`, `中文优先分析`, `原文证据摘录`, or `先读 wiki/index.md 再回答`. This is the canonical read-side skill for approved retrieval, candidate ranking, answer archiving/reuse, creator-facing publishing, and static export. Do not use for generic writing, open web research, deterministic rendering, or governance/maintenance work handled by `kb-render` or `kb-review`.

2026-07-093

kb-render

bahayonghang/obsidian-notes-karpathy

Render deterministic outward-facing artifacts from approved knowledge. Use this skill whenever the user says "kb render", "render slides", "render report", "make a canvas", "generate chart brief", "生成幻灯片", "生成报告", "输出 canvas", `把已批准主题做成报告`, or clearly wants a deterministic derivative from approved live pages or already-grounded archived answers. This is the separate shipped skill for slides, reports, charts, and canvas outputs. Do not use it for retrieval, grounded Q&A, static web export, governance reports, or maintenance work.

2026-07-093

kb-review

bahayonghang/obsidian-notes-karpathy

Run the canonical governance lane for an Obsidian knowledge base. Use this skill whenever the user says "kb review", "kb health", "review gate", "health check", "approve drafts", "reject draft knowledge", "promote to live", "rebuild briefings", "lint live wiki", "clear archive backlog", "audit archived outputs", "检查归档内容", "检查风格约束是否冲突", "检查账号 briefing", "审校草稿", "批准草稿", "知识库体检", or uses Chinese-LLM-Wiki maintenance wording such as `lint`, `孤儿页`, `断链`, `旧结论被覆盖`, `output/reports`, `治理报告`, `先做 lint`, and `原文证据摘录是否充分`. This skill owns both the immediate gate and the longer-horizon maintenance lane through internal `gate` and `maintenance` modes. Do not use it for normal approved-layer retrieval or deterministic derivative rendering.

2026-07-093

obsidian-notes-karpathy

bahayonghang/obsidian-notes-karpathy

Diagnose and route ambiguous, workflow-level review-gated Obsidian vault requests. Use this skill when the user is talking about an Obsidian vault workflow as a whole, asks which lifecycle step should run next, says things like "what should I run first", "which stage am I in", "LLM Wiki", "Karpathy wiki", "Obsidian IDE", "knowledge compiler", "creator knowledge compiler", "personal knowledge base", "second brain", "archive this answer", "归档这个回答", "存回知识库", "复用归档内容", "清理 archive backlog", "先读 wiki/index.md", "这个知识库下一步该做什么", "现在应该初始化/摄取/编译/审校/检索/发布/渲染/体检哪个步骤", or uses Chinese-LLM-Wiki wording such as `中文优先`, `来源页`, `主题页`, `实体页`, `综合页`, `output/analyses`, `output/reports`, `原文证据摘录`, `先读 wiki/index.md 再判断`, or `先判断该做来源页还是综合页` without making the operation explicit. Prefer the operation-specific skills when the user already clearly means init, ingest, compile, review, query, publish, render, or archive maintenance, and only route through this package entry skill when the workflow step is genuinely ambiguous.

2026-07-093

name

kb-init

description

KB Init

One-time setup, migration, and repair for the review-gated workflow.

Quick Start

For a fresh vault, the happy path is four steps:

Init — run kb-init to create the support layer (raw/, wiki/, outputs/, AGENTS.md)
Ingest — run kb-ingest to register raw sources into raw/_manifest.yaml
Compile — run kb-compile to build reviewable drafts
Review — run kb-review to approve drafts into the permanent wiki under wiki/live/

After that, use kb-query to ask questions, kb-render to generate deterministic outward artifacts, and kb-review maintenance mode to audit drift.

This mirrors Karpathy's LLM Wiki pattern: raw sources are immutable evidence, the LLM compiles and maintains the wiki, and you curate by sourcing documents and asking the right questions.

If the user arrives with the simpler raw/wiki/output language from Chinese-LLM-Wiki, keep that as onboarding vocabulary only. The implementation still lands on the review-gated support layer.

Read before writing

Read these shared references first:

../obsidian-notes-karpathy/scripts/skill-contract-registry.json
../obsidian-notes-karpathy/references/file-model.md
../obsidian-notes-karpathy/references/lifecycle-matrix.md
../obsidian-notes-karpathy/references/chinese-llm-wiki-compat.md
../obsidian-notes-karpathy/references/index-home-template.md
../obsidian-notes-karpathy/references/source-manifest-contract.md
../obsidian-notes-karpathy/references/memory-lifecycle.md

Treat skill-contract-registry.json as the canonical source for role, baseline command, required references, and expected write surfaces.

If onkb is available, use these commands first:

onkb --json status <vault-root> to distinguish setup, repair, and needs-migration
onkb --json init <vault-root> ... for fresh setup and non-destructive repair scaffolding
onkb --json migrate <vault-root> ... for legacy single-layer vault migration
onkb --json review governance <vault-root> --write when optional governance scaffolding should be materialized

If onkb is missing, follow the install fallback in ../obsidian-notes-karpathy/references/lifecycle-matrix.md, then rerun the same command.

Load on demand

Load these only when the trigger applies:

../obsidian-notes-karpathy/references/schema-template.md — when vault-wide frontmatter fields beyond this skill's core schema need checking
../obsidian-notes-karpathy/references/summary-template.md — when creating or repairing draft source summaries
../obsidian-notes-karpathy/references/review-template.md — when repairing outputs/reviews/** records
../obsidian-notes-karpathy/references/briefing-template.md — when rebuilding or repairing wiki/briefings/**
../obsidian-notes-karpathy/references/activity-log-template.md — when appending an entry to wiki/log.md
../obsidian-notes-karpathy/references/questions-template.md — when scaffolding or repairing wiki/live/indices/QUESTIONS.md
../obsidian-notes-karpathy/references/provenance-and-alias-policy.md — when alias overlap, duplicate candidates, or provenance drift surfaces
../obsidian-notes-karpathy/references/query-writeback-lifecycle.md — when writeback candidates, writeback_status, or archive backlog work is involved
../obsidian-notes-karpathy/references/taxonomy-and-hubs.md — when repairing the topics layer or curated hubs
../obsidian-notes-karpathy/references/graph-contract.md — when graph exports, related edges, or relationship candidates are involved
../obsidian-notes-karpathy/references/topic-template.md — when shaping or promoting browse-layer topic pages
../obsidian-notes-karpathy/references/profile-contract.md — when account profiles or source_profile metadata is involved
../obsidian-notes-karpathy/references/automation-hooks.md — when wiring or invoking onkb review automation modes
../obsidian-notes-karpathy/references/procedure-template.md — when the durable delta is procedural (workflow or playbook)
../obsidian-notes-karpathy/references/episode-template.md — when outputs/episodes/** work is involved

Profile choice

Surface the operating profile during init or repair:

governed-team for the strictest default governance
standard for lighter maintenance noise without widening truth
fast-personal for solo use where briefings can stay out of default query scope

Persist the chosen profile in scaffolded starter files so later lifecycle and query tooling can see it deterministically.

MEMORY.md is recommended collaboration scaffolding but not a blocking requirement. Solo / fast-personal vaults can skip it by running onkb --json init <vault-root> --skip-memory. The rest of the support layer still lands.

Create or repair the canonical structure

Create the required support layer:

raw/human/{articles,papers,podcasts,repos,assets}
raw/human/data
raw/agents/{role}/
raw/_manifest.yaml
wiki/drafts/{summaries,topics,concepts,entities,procedures,overviews,comparisons,indices}
wiki/live/{summaries,topics,concepts,entities,procedures,overviews,comparisons,indices}
wiki/briefings/
wiki/index.md
wiki/log.md
outputs/reviews/
AGENTS.md
CLAUDE.md

Create downstream output directories such as outputs/qa/, outputs/health/, outputs/reports/, outputs/slides/, outputs/charts/, and outputs/content/** only when the user wants full scaffolding or the later stages need them.

Treat MEMORY.md as recommended collaboration scaffolding. It should hold preferences, editorial priorities, and coordination context, not source-grounded topic knowledge.

Optional governance scaffolding may include:

wiki/live/indices/QUESTIONS.md
wiki/live/indices/GAPS.md
wiki/live/indices/ALIASES.md
wiki/live/indices/ENTITIES.md
wiki/live/indices/RELATIONSHIPS.md

Optional latest-capability scaffolding may include:

outputs/episodes/
outputs/audit/operations.jsonl
outputs/health/graph-snapshot.json

Migration posture

For legacy-layout vaults:

preserve legacy content
explain that direct wiki/summaries/ / wiki/concepts/ pages must move into wiki/live/
scaffold the review-gated directories first
treat migration as a repair step, not as a normal compile or query pass

Checkpoint

Before creating or repairing the support layer, confirm with the user:

which operating profile to use (governed-team, standard, or fast-personal)
whether optional governance scaffolding (QUESTIONS.md, GAPS.md, ALIASES.md) is wanted
whether this is a fresh setup, a repair of an existing vault, or a legacy-layout migration

For a fresh vault with no existing content, proceed after profile selection without further confirmation.

Contract guarantees

raw/ stays immutable
kb-compile writes only to wiki/drafts/
kb-review owns promotion into wiki/live/ and briefing refresh
kb-query must not read drafts as truth
AGENTS.md and CLAUDE.md stay aligned on the review-gated file model
downstream outputs beyond outputs/reviews/ are optional scaffolding, not minimum support-layer requirements

Starter files

Create:

wiki/index.md
wiki/log.md
MEMORY.md
raw/_manifest.yaml
wiki/live/indices/INDEX.md
wiki/live/indices/CONCEPTS.md
wiki/live/indices/SOURCES.md
wiki/live/indices/TOPICS.md
wiki/live/indices/RECENT.md
wiki/live/indices/EDITORIAL-PRIORITIES.md
optional wiki/live/indices/QUESTIONS.md when the user wants governance scaffolding
optional wiki/live/indices/ENTITIES.md and RELATIONSHIPS.md when the user wants graph-friendly navigation
at least one example briefing or a placeholder in wiki/briefings/
a review template example in outputs/reviews/ when the user wants a demonstrable starter

Output to the user

Report:

what was created or migrated
whether a legacy-layout / needs-migration state was detected
what existing content was preserved
the next recommended command, usually kb-compile or kb-review