obsidian-project-kb-core
The obsidian-project-kb-core skill manages a vault-first Obsidian knowledge base organized under Research/{project-slug}/, handling project bootstrap, note routing into designated folders, maintenance of hub and index documents, registry updates, lifecycle actions like create and archive, and lint orchestration. Use this when setting up or maintaining a structured research project knowledge base that requires deterministic health checks and consistent organization across sources, knowledge, experiments, and results.
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar /tmp/obsidian-project-kb-core && cp -r /tmp/obsidian-project-kb-core/skills/obsidian-project-kb-core ~/.claude/skills/obsidian-project-kb-coreSKILL.md
# Obsidian Project KB Core
This is the **main workflow authority** for project-scoped Obsidian knowledge maintenance.
Default project root:
```text
Research/{project-slug}/
```
Default structure:
```text
00-Hub.md
01-Plan.md
02-Index.md
Sources/
Knowledge/
Experiments/
Results/
Reports/
Writing/
Daily/
Maps/
Archive/
_system/
```
## Core rules
- Keep all durable project knowledge inside the current `Research/{project-slug}/`.
- Keep repo-local `.claude/project-memory/*` only as the runtime binding layer.
- `_system/registry.md` is the only visible project registry.
- `02-Index.md` is a human navigation note, not a registry mirror.
- `Maps/` is a derived-artifact area; do not generate non-essential canvases by default.
- `Results/Reports/` is the default subdirectory for round and batch experiment reports.
## Responsibilities
- detect and bind the current repo to a project root
- bootstrap the project skeleton
- route notes into `Sources / Knowledge / Experiments / Results / Results/Reports / Writing / Daily / Maps / Archive`
- update `00-Hub.md`, `01-Plan.md`, `02-Index.md`
- update `_system/registry.md`, `_system/schema.md`, `_system/lint-report.md`
- handle note lifecycle actions: create, update, rename, archive, purge, promote, and link repair
- run deterministic health checks through helper scripts
## Deterministic helpers
Use the scripts under `scripts/` for:
- scaffold
- registry consistency
- link checks
- index checks
- canvas checks
- lint aggregation
Use agents for:
- note routing
- daily promotion decisions
- source vs knowledge judgment
- stable-result judgment
- semantic Hub and Index updates
## Read next
- `references/DIRECTORY-SCHEMA.md`
- `references/HUB-PLAN-INDEX.md`
- `references/REGISTRY.md`
- `references/DAILY-PROMOTION.md`
- `references/LIFECYCLE.md`
- `references/LINT.md`
- `references/BINDING-LAYER.md`Use when creating or configuring Claude Code agents and their frontmatter.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.