# Create Obsidian Markdown Notes

Obsidian notes need links, embeds, callouts, and properties that render correctly. This skill helps Claude, Codex, and Claude Code write Obsidian Flavored Markdown for vault-ready notes.

## Install

```bash
npx skillstore add kepano/obsidian-markdown
```

## Metadata

- Status: approved
- Slug: kepano-obsidian-markdown
- Skillstore revision: r1
- Version status: missing
- Tree hash: b01b112eaad32caf0d4d9e58b0cf78d6bf04130432646603df96baa9eb1163db
- Author: kepano
- GitHub username: kepano
- License: MIT
- Repository: https://github.com/kepano/obsidian-skills/tree/main/skills/obsidian-markdown
- Ref: b8ca75d2c0a7e7102978993058777d82b8ab2610
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/kepano-obsidian-markdown
- Manifest: https://skillstore.pages.dev/api/skills/kepano-obsidian-markdown/manifest

## Capabilities

- Creates notes with YAML properties, tags, aliases, status fields, and dates.
- Formats internal wikilinks to notes, headings, and block IDs.
- Adds embeds for notes, images, PDFs, audio, video, and query blocks.
- Builds Obsidian callouts, including foldable and nested callouts.
- Uses Obsidian comments, highlights, LaTeX math, Mermaid diagrams, and footnotes.

## Use Cases

- Build linked research notes: Researchers can turn source notes into Obsidian notes with wikilinks, tags, callouts, and embeds.
- Standardize project documentation: Project teams can apply consistent properties, task lists, status fields, and internal links across notes.
- Convert Markdown for a vault: Writers can adapt plain Markdown into Obsidian Flavored Markdown without losing headings, tables, or links.

## Prompt Templates

### Create a Basic Note

```
Create an Obsidian note about [topic]. Include YAML properties, tags, one wikilink, and one simple callout.
```

### Improve an Existing Note

```
Review this Obsidian note and improve wikilinks, tags, aliases, and callouts. Keep my existing content intact: [paste note].
```

### Design a Vault Entry Template

```
Create an Obsidian note template for [workflow]. Include properties for status, dates, related notes, tasks, and review notes.
```

### Refactor a Linked Knowledge Map

```
Analyze these related notes and propose Obsidian wikilinks, embeds, block links, and callouts that connect them cleanly: [paste notes].
```

## Limitations

- Does not run Obsidian or verify rendering in a live vault.
- Does not inspect a full vault unless the files are provided.
- Does not install plugins or change Obsidian settings.
- Embedded files and external media still depend on user-provided paths and links.

## Best Practices

- Provide exact note names when you want reliable wikilinks.
- Define required properties before asking for long notes or templates.
- Review embeds and callouts in Obsidian reading view before publishing.

## Anti Patterns

- Do not ask it to invent vault filenames when exact links matter.
- Do not rely on it for final rendering without opening Obsidian.
- Do not mix external web links and internal wikilinks without clear labels.

## Security Audit

- Audited at: 2026-07-06T18:25:32.536\+00:00
- Summary: All 52 static findings were adjudicated as false positives from Markdown syntax examples, sample URLs, and documentation links. No evidence found for command execution, reconnaissance, network activity, prompt injection, or data exfiltration.

## Stats

- Views: 200
- Downloads: 24
- Favorites: 1
- Popularity score: 0