AgriciDaniel/claude-obsidian / skills/wiki
wiki
VerifiedInitialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/coordination.md | markdown | 1.9 KB |
| references/css-snippets.md | markdown | 4.3 KB |
| references/dataview.md | markdown | 1.6 KB |
| references/frontmatter.md | markdown | 2.7 KB |
| references/git-setup.md | markdown | 2.5 KB |
| references/install-modes.md | markdown | 1.9 KB |
| references/knowledge-recipes.md | markdown | 3.3 KB |
| references/mcp-setup.md | markdown | 1.9 KB |
| references/model-guidance.md | markdown | 1.6 KB |
| references/modes.md | markdown | 3.1 KB |
| references/operation-transactions.md | markdown | 6.0 KB |
| references/plugins.md | markdown | 2.7 KB |
| references/provenance.md | markdown | 3.2 KB |
| references/rest-api.md | markdown | 1.4 KB |
references/frontmatter.md
View on GitHub# Frontmatter conventions
Preserve an existing vault's valid property vocabulary. For a new generic
claude-obsidian page, use flat YAML properties, block lists, and explicit
evidence fields where they apply.
## Common properties
```yaml
---
type: concept
title: "Human-readable title"
created: YYYY-MM-DD
updated: YYYY-MM-DD
status: developing
tags:
- concept
related:
- "[[Related page]]"
sources:
- "[[Source page]]"
claim_ids:
- claim-example
---
```
Page types are declared once in `claude_obsidian/page_schema.py` and documented in
[WIKI.md](../../../WIKI.md). This file previously restated a shorter list that
omitted `session` and `fold`, which is how a vault ends up carrying values one
document calls invalid. Statuses are still described in prose in both places and
are out of this change's scope. A custom scaffold may add types when
its schema is documented. `status` commonly progresses through `seed`,
`developing`, `mature`, and `evergreen`; preserve other established values in an
adopted vault.
## Source properties
```yaml
source_type: article
author: ""
date_published: YYYY-MM-DD
url: ""
source_id: ""
sha256: ""
authority: unknown
independence_key: ""
review_state: unreviewed
key_claims:
- "No claims extracted yet."
```
Allowed authority values and evidence semantics are defined in
[provenance.md](provenance.md). A missing value remains empty or `unknown`; do
not manufacture metadata to complete a form.
## Other type-specific properties
```yaml
# entity
entity_type: organization
role: ""
first_mentioned: "[[Source page]]"
# concept
complexity: intermediate
domain: ""
aliases:
- Alternative name
# comparison
subjects:
- "[[Thing A]]"
- "[[Thing B]]"
dimensions:
- cost
- reliability
assessment: provisional
risk: low
# question
question: "What is being asked?"
assessment: unsupported
risk: low
```
## Rules
1. Keep generated properties flat; do not introduce nested mappings.
2. Write dates as `YYYY-MM-DD` unless an existing schema requires a timestamp.
3. Use block lists for generated multi-value properties.
4. Quote wikilinks in YAML.
5. Keep external locators on source records; use wikilinks for internal
`related` and `sources` relationships.
6. Update `updated` only when the page content or assessed state changes.
7. Preserve unknown valid properties during an edit.
8. Do not treat a frontmatter confidence label as evidence; the claim ledger
and linked active sources determine support.
9. A numeric-only tag is invalid even when quoted. Use `year/2026` or `y2026`,
or a numeric `year` property. Preserve existing user metadata unless its
correction is explicitly requested. See [Obsidian Tags](https://obsidian.md/help/tags),
checked 2026-10-17.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |