npx claudepluginhub teslasoft-de/claude-skills-marketplace --plugin vault-bootThis skill uses the workspace's default tool permissions.
---
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
This skill eliminates the multi-step cold-start problem when beginning a new Cowork session. Instead of 10+ sequential tool calls to piece together vault state, this procedure loads everything in two parallel batches and renders a single status briefing.
/jarvis skill instead if drone is running)The Obsidian MCP server must be connected and serving the Teslasoft vault.
If obsidian_get_file_contents calls fail, fall back to direct file reads
from the vault root directory.
Fire ALL of these obsidian_get_file_contents calls in one parallel batch:
| # | File | Purpose |
|---|---|---|
| 1 | TASKS.md | Active/waiting/someday tasks |
| 2 | PROJECT_STATE.md | Goal status, active projects, KRs, constraints |
| 3 | AGENTS.md | Vault conventions, PARA structure, edit rules |
| 4 | coordination/harness-control.md | Thread control, active threads, CI-001 |
| 5 | coordination/improvement-queue.md | Pending improvements, recent implementations |
| 6 | coordination/policies/policies.index.yaml | Active policy catalog |
That is 6 parallel calls in a single message. This is the most important optimization — it replaces 6 sequential round-trips with 1.
After Step 1 completes, fire these calls in parallel:
| # | Call | Purpose |
|---|---|---|
| 7 | obsidian_list_files_in_dir("coordination/threads") | Active thread specs |
| 8 | obsidian_list_files_in_dir("coordination/agent-state") | Agent state files |
| 9 | obsidian_list_files_in_dir("00_Inbox") | Inbox item count |
| 10 | obsidian_get_file_contents("Dashboard.md") | Dataview queries reference |
Open the dashboard in the default browser using a platform-appropriate command:
In Claude Code sessions (WSL), use:
cmd.exe /c start "" "$(wslpath -w '00_Dashboard/dashboard.html')"
In Windows Shell, use:
Start-Process "00_Dashboard\dashboard.html"
If neither is available, note the path 00_Dashboard/dashboard.html for manual opening.
This is non-blocking and takes <1 second. Do NOT wait for Chrome tab context or navigate via Chrome MCP — the shell approach is faster and more reliable.
Compile the loaded data into this exact template. Keep it concise — the user can drill down into any area on request.
## Teslasoft Vault — Status ({date})
**Goal Q1 2026:** {goal_description}
| KR | Status | Project |
|----|--------|---------|
| {kr1} | {status} | {project_link} |
| {kr2} | {status} | {project_link} |
| {kr3} | {status} | {project_link} |
**Active Tasks:**
{render each active task from TASKS.md as a bullet}
**Blocked:** {list blocked tasks with reason}
**Harness:** {master_switch on/off}, {N} active threads, {N} archived
**Inbox:** {N} items
**Improvements:** {N} pending, {N} implemented this week
**Policies:** {N} active ({list key policy IDs})
**Dashboard:** Opened in browser
End with a brief ready message in the user's language (German for Christian):
Kontext geladen. Womit moechtest du weitermachen?
If active threads or P0/P1 alerts exist, surface them prominently before the ready prompt.
If Obsidian MCP is unreachable or timing out:
The entire boot procedure should complete in 2 tool-call turns (Steps 1+2 as parallel batches) plus 1 turn for the dashboard + rendering. Total wall time target: < 15 seconds, down from ~60 seconds with sequential loading.
These are facts about the vault that help you interpret the loaded data correctly. You don't need to present these to the user, but they inform your understanding.
T-P{project}-{role_initial}{N} (e.g., T-P38-T9)