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/modes.md
View on GitHub# Domain-specific scaffold profiles
Initialize or adopt the baseline vault first. A profile adds folders, page
types, and index sections in one inspected transaction; it does not replace the
selected organizational methodology (`generic`, `lyt`, `para`, or
`zettelkasten`). Preserve existing notes and routes.
Every profile keeps these invariants:
- immutable captured sources under `.raw/`;
- generated knowledge under `wiki/`;
- `wiki/index.md`, `wiki/log.md`, and `wiki/hot.md` as canonical lifecycle
pages;
- evidence and claim ledgers under `wiki/meta/ledgers/`;
- one operation-level transaction for a requested scaffold;
- no remote, plugin, egress, or Git setup without separate approval.
## Website or content system
Suggested routes: `wiki/pages/`, `wiki/structure/`, `wiki/audits/`,
`wiki/keywords/`, and `wiki/entities/`.
Useful page properties include the source URL, lifecycle status, canonical URL,
last verified date, and internal-link counts. Treat crawl and analytics exports
as sources; do not assert live indexing or HTTP status without current evidence.
## Software repository
Suggested routes: `wiki/modules/`, `wiki/components/`, `wiki/decisions/`,
`wiki/dependencies/`, and `wiki/flows/`.
Record repository-relative paths, purpose, status, dependency relationships,
and evidence from code, tests, issues, or primary documentation. Generated
architecture pages must distinguish observed behavior from inference.
## Business or project
Suggested routes: `wiki/stakeholders/`, `wiki/decisions/`,
`wiki/deliverables/`, `wiki/intel/`, and `wiki/meetings/`.
Record decision date, owner, status, rationale, and source record. Preserve
conflicting recollections as contested evidence instead of rewriting history.
## Personal knowledge vault
Suggested routes: `wiki/goals/`, `wiki/learning/`, `wiki/people/`,
`wiki/areas/`, and `wiki/resources/`.
Default to local-only processing. Confirm privacy and retention before capturing
messages, health, finance, relationship, or voice data. Do not save a whole
conversation when the user asked to preserve only one insight.
## Research
Suggested routes: `wiki/papers/`, `wiki/concepts/`, `wiki/entities/`,
`wiki/syntheses/`, and `wiki/gaps/`.
Track claim support, contradictions, authority, independence, freshness, and
risk in the ledgers. A paper summary is secondary to the captured paper and
does not automatically validate its claims.
## Book or course companion
Suggested routes: `wiki/chapters/`, `wiki/concepts/`, `wiki/people/`,
`wiki/exercises/`, and `wiki/reflections/`.
Capture only material the user is authorized to store. Prefer concise
source-linked notes over reproducing copyrighted chapters or transcripts.
## Applying a profile
1. Inspect the current methodology and representative notes.
2. Draft a folder/page/property map and identify naming conflicts.
3. Show the proposed paths and any schema additions.
4. Apply approved additions once through the transaction core.
5. Run deterministic lint and report unresolved findings.
6. Let actual use determine later refinements rather than prebuilding an empty
hierarchy.
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 |