メニュー
Reference for Obsidian-specific markdown syntax beyond standard CommonMark — wikilinks, callouts, embeds, properties, dataview, and templater. Use when creating or editing files intended for the Obsidian vault.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cdeistopened/skill-stack-skills --skill obsidian-markdownコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Build and use an affirmation practice based on Scott Adams' specific methodology. Use when someone says 'how do affirmations work', 'teach me affirmations', 'does Adams really write affirmations', 'how to manifest goals', 'affirmation practice', 'I want to try affirmations', or 'what's Adams' affirmation system.' Teaches Adams' specific 15x daily writing practice with his caveats and track record.
Resolve apparent contradictions using Zakery Kline's three-strategy framework from How to Think. Use when someone says 'these two things both seem true but they contradict each other', 'how can X and Y both be right', 'this doesn't make sense — on one hand... but on the other hand', 'I'm confused by an apparent contradiction', 'these claims seem incompatible', or 'help me reconcile these two positions.' Walks through distinction-making, level analysis, and temporal resolution to determine whether the contradiction is real or resolvable.
Analyze text for logical fallacies using Zakery Kline's framework from Chapter 3 of How to Think. Use when someone says 'check this argument', 'find the fallacies', 'is this reasoning valid', 'analyze this debate', 'what's wrong with this argument', 'logical fallacies', 'is this logically sound', 'audit this essay', 'check my reasoning', or 'fallacy check.' Scans for all 10 named fallacies, quotes the specific passages, and shows how to fix each one.
| name | obsidian-markdown |
| description | Reference for Obsidian-specific markdown syntax beyond standard CommonMark — wikilinks, callouts, embeds, properties, dataview, and templater. Use when creating or editing files intended for the Obsidian vault. |
Reference for Obsidian-specific markdown syntax beyond standard CommonMark. Use when creating or editing files intended for the Obsidian vault.
YAML block at file start, delimited by ---. Obsidian reads these as typed properties.
---
title: My Note
date: 2026-03-01
tags:
- project/alpha
- status/active
status: in_progress
aliases:
- Alt Name
cssclasses:
- wide-page
---
Property types: text, number, checkbox, date, datetime, list, tags
Reserved properties: tags, aliases, cssclasses
[[Note Name]] # Link to note
[[Note Name|Display Text]] # Link with alias
[[Note Name#Heading]] # Link to heading
[[Note Name#^block-id]] # Link to block
[[Note Name#Heading|Display]] # Heading link with alias
Embeds — prefix with ! to render inline:
![[Note Name]] # Embed entire note
![[Note Name#Heading]] # Embed section
![[image.png]] # Embed image
![[image.png|300]] # Embed image with width
![[audio.mp3]] # Embed audio player
![[video.mp4]] # Embed video player
![[document.pdf]] # Embed PDF
![[document.pdf#page=3]] # Embed specific PDF page
Add a ^block-id at the end of any block (paragraph, list item, etc.):
This is a paragraph I want to reference. ^my-block
- List item with reference ^list-ref
Link to it: [[Note Name#^my-block]]
Embed it: ![[Note Name#^my-block]]
Block IDs: lowercase letters, numbers, hyphens. Obsidian auto-generates 6-char hex IDs when you type ^ in the link autocomplete.
#tag # Simple tag
#nested/tag # Nested tag (creates hierarchy)
#project/alpha # Convention: category/value
Tags work in body text and in tags: frontmatter property. Nested tags create browsable hierarchies in the tag pane.
> [!note] Optional Title
> Callout body content.
> [!warning]
> No title — uses type name as title.
> [!tip]- Foldable (collapsed by default)
> Content hidden until expanded.
> [!tip]+ Foldable (expanded by default)
> Content visible, can be collapsed.
Built-in types: note, abstract/summary/tldr, info, todo, tip/hint/important, success/check/done, question/help/faq, warning/caution/attention, failure/fail/missing, danger/error, bug, example, quote/cite
Nesting: Callouts can nest inside each other with additional > levels.
%%This text is invisible in reading view%%
%%
Multi-line comments
also work
%%
Here is a sentence with a footnote.[^1]
[^1]: This is the footnote content.
Inline footnote^[This is inline footnote content].
Inline: $E = mc^2$
Block:
$$
\sum_{i=1}^{n} x_i = x_1 + x_2 + \cdots + x_n
$$
| Left | Center | Right |
|:-----|:------:|------:|
| a | b | c |
- [ ] Unchecked
- [x] Checked
- [/] In progress (community convention)
- [-] Cancelled (community convention)
==highlighted text== # Yellow highlight
**bold** and *italic* # Standard
~~strikethrough~~ # Standard
`inline code` # Standard
[[Note]]) not markdown links for internal vault linkstitle, date, tags#status/active, #project/opened, #type/podcast%%...%%) for Claude-only notes that shouldn't render in Obsidian