菜单
Use when creating or editing notes in an Obsidian vault, writing to ~/knowledge, or using Obsidian-specific syntax (wikilinks, callouts, embeds, frontmatter properties).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when asked to document work, record decisions, create session records, write ADRs or RFCs, or update knowledge notes in ~/knowledge. Also use when confused about who a person is, what a company is, what situation the user is referring to, or any personal or professional context — read the vault before asking.
Use when reviewing any implementation. Replaces fixed spec+quality two-step with category-driven parallel specialists: an assessor picks relevant categories for the specific artifact, one specialist per category reviews in parallel, controller aggregates. Use after implementer completes a task in subagent-driven-development.
Use when dispatching work to background agents, defining custom subagents, or choosing between local agent dispatch and VM-based workers (claude-ctl).
Use when working with Kubernetes clusters, GitOps deployments, Flux reconciliation, Helm releases, or cluster troubleshooting. Guides declarative cluster management and GitOps workflows. Not for secrets encryption or SOPS operations — route those to secrets-management.
Use when sending a notification to ntfy from a homelab service, loop, or agent. Covers the canonical in-cluster publish pattern and the silent-failure trap of posting to the Authentik-gated public URL.
Use when encrypting secrets with SOPS/age, managing Kubernetes Secret manifests, rotating credentials, or setting up secret delivery (sops-nix, sealed secrets). Not for application code that reads env vars or auth tokens at runtime.
| name | obsidian-markdown |
| description | Use when creating or editing notes in an Obsidian vault, writing to ~/knowledge, or using Obsidian-specific syntax (wikilinks, callouts, embeds, frontmatter properties). |
| allowed-tools | Bash, Read, Grep, Glob, Write, Edit |
| injectable | true |
Extends CommonMark/GFM with wikilinks, embeds, callouts, and properties. Standard Markdown (headings, bold, lists, tables) is assumed.
[[Note Name]] Link to note (Obsidian tracks renames)
[[Note Name|Display Text]] Custom display text
[[Note Name#Heading]] Link to heading
[[Note Name#^block-id]] Link to block
[[#Heading]] Same-note heading
Use [[wikilinks]] for vault-internal notes; [text](url) for external URLs only.
Define a block ID by appending ^my-id to any paragraph (lists/quotes: put it on a separate line after).
![[Note Name]] Embed full note
![[Note Name#Heading]] Embed section
![[image.png|300]] Embed image with width
![[document.pdf#page=3]] Embed PDF page
> [!note]
> Basic callout.
> [!warning] Custom Title
> Callout with custom title.
> [!faq]- Collapsed by default
> - collapsed, + expanded
Common types: note tip warning info example quote bug danger success todo
---
date: 2024-01-15
tags:
- project
- active
aliases:
- Alternative Name
---
tags — searchable labels. aliases — alternative names for link suggestions.
==Highlighted text== Highlight
%%hidden comment%% Hidden in reading view
#nested/tag Inline tag with hierarchy
$e^{i\pi} + 1 = 0$ Inline LaTeX
~/knowledge)This vault uses the ICM (Interpreted Context Methodology) structure:
| Convention | Pattern |
|---|---|
| Session records | sessions/ai-sessions/YYYY-MM-DD-slug.md |
| ADRs | <room>/decisions/ADR-NNN-slug.md |
| RFCs | <room>/decisions/RFC-YYYY-MM-slug.md |
| Room routing | INDEX.md (discovery) + CONTEXT.md (activation) |
| Cross-room links | Wikilinks: [[sessions/ai-sessions/2024-01-15-slug]] |
Frontmatter for session records:
---
date: 2026-04-11
type: ai-session # or: meeting, work-session
project: homelab
goal: "one sentence"
outcome: "result"
session_id: abc123
---
Frontmatter for ADRs:
---
status: accepted # proposed | accepted | deprecated | superseded
date: 2026-04-11
supersedes: null
related: []
---
Required ADR sections: Context, Decision (one sentence), Options Considered (table), Consequences, Links.