Lion-1209/dsh-plugin-wiki-skills / skills/wiki
wiki
VerifiedClaude + Obsidian knowledge companion. Sets up a persistent wiki vault, scaffolds structure from a one-sentence description, and routes to specialized sub-skills. Use for setup, scaffolding, cross-project referencing, and hot cache management. Triggers on: "set up wiki", "scaffold vault", "create knowledge base", "/wiki", "wiki setup", "obsidian vault", "knowledge base", "second brain setup", "running notetaker", "persistent memory", "llm wiki".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.6 KB |
| references/css-snippets.md | markdown | 4.2 KB |
| references/frontmatter.md | markdown | 2.1 KB |
| references/git-setup.md | markdown | 1.1 KB |
| references/mcp-setup.md | markdown | 4.3 KB |
| references/modes.md | markdown | 7.8 KB |
| references/plugins.md | markdown | 3.4 KB |
| references/rest-api.md | markdown | 2.1 KB |
references/frontmatter.md
View on GitHub# Frontmatter Schema
Every wiki page starts with flat YAML frontmatter. No nested objects. Obsidian's Properties UI requires flat structure.
---
## Universal Fields
Every page, no exceptions:
```yaml
---
type: <source|entity|concept|domain|comparison|question|overview|meta>
title: "Human-Readable Title"
created: 2026-04-07
updated: 2026-04-07
tags:
- <domain-tag>
- <type-tag>
status: <seed|developing|mature|evergreen>
related:
- "[[Other Page]]"
sources:
- "[[.raw/articles/source-file.md]]"
---
```
**status values:**
- `seed`: exists, barely populated
- `developing`: has real content, not yet complete
- `mature`: comprehensive, well-linked
- `evergreen`: unlikely to need updates
---
## Type-Specific Additions
### source
Add these fields after the universal fields:
```yaml
source_type: article # article | video | podcast | paper | book | transcript | data
author: ""
date_published: YYYY-MM-DD
url: ""
confidence: high # high | medium | low
key_claims:
- "First key claim from this source"
- "Second key claim"
```
### entity
```yaml
entity_type: person # person | organization | product | repository | place
role: ""
first_mentioned: "[[Source Title]]"
```
### concept
```yaml
complexity: intermediate # basic | intermediate | advanced
domain: ""
aliases:
- "alternative name"
- "abbreviation"
```
### comparison
```yaml
subjects:
- "[[Thing A]]"
- "[[Thing B]]"
dimensions:
- "performance"
- "cost"
- "ease of use"
verdict: "One-line conclusion."
```
### question
```yaml
question: "The original query as asked."
answer_quality: solid # draft | solid | definitive
```
### domain
```yaml
subdomain_of: "" # leave empty for top-level domains
page_count: 0
```
---
## Rules
1. Use flat YAML only. Never nest objects.
2. Dates as `YYYY-MM-DD` strings, not ISO datetime.
3. Lists always use the `- item` format, not inline `[a, b, c]`.
4. Wikilinks in YAML fields must be quoted: `"[[Page Name]]"`.
5. Keep `related` and `sources` as wikilinks, not plain URLs.
6. Update `updated` every time you edit the page content.
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 |