Use this as the main Claude Scholar skill for a vault-first, project-scoped Obsidian research knowledge base rooted at Research/{project-slug}/. It owns bootstrap, routing, daily logging, hub/plan/index maintenance, registry updates, lifecycle actions, and lint orchestration.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add gabrielmoreira/agent-skills-mirror --skill obsidian-project-kb-core --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Obsidian Project Kb Core?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gabrielmoreira-obsidian-project-kb-core)More formats (shields.io, HTML) on the badges page.
---
name: obsidian-project-kb-core
description: Use this as the main Claude Scholar skill for a vault-first, project-scoped Obsidian research knowledge base rooted at Research/{project-slug}/. It owns bootstrap, routing, daily logging, hub/plan/index maintenance, registry updates, lifecycle actions, and lint orchestration.
---
# 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`

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!