This skill enables Claude Code to create and edit valid Obsidian Flavored Markdown, including all Obsidian-specific syntax extensions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionobsidian-markdownExecute the skills CLI command in your project's root directory to begin installation:
Fetches obsidian-markdown from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate obsidian-markdown. Access via /obsidian-markdown in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
This skill enables Claude Code to create and edit valid Obsidian Flavored Markdown, including all Obsidian-specific syntax extensions.
Obsidian uses a combination of Markdown flavors:
This is a paragraph.
This is another paragraph (blank line between creates separate paragraphs).
For a line break within a paragraph, add two spaces at the end
or use Shift+Enter.
# Heading 1
## Heading 2
### Heading 3
#### Heading 4
##### Heading 5
###### Heading 6
| Style | Syntax | Example | Output |
|---|---|---|---|
| Bold | **text** or __text__ |
**Bold** |
Bold |
| Italic | *text* or _text_ |
*Italic* |
Italic |
| Bold + Italic | ***text*** |
***Both*** |
Both |
| Strikethrough | ~~text~~ |
~~Striked~~ |
|
| Highlight | ==text== |
==Highlighted== |
==Highlighted== |
| Inline code | `code` |
`code` |
code |
Use backslash to escape special characters:
\*This won't be italic\*
\#This won't be a heading
1\. This won't be a list item
Common characters to escape: \*, \_, \#, \`, \|, \~
[[Note Name]]
[[Note Name.md]]
[[Note Name|Display Text]]
[[Note Name#Heading]]
[[Note Name#Heading|Custom Text]]
[[#Heading in same note]]
[[##Search all headings in vault]]
[[Note Name#^block-id]]
[[Note Name#^block-id|Custom Text]]
Define a block ID by adding ^block-id at the end of a paragraph:
This is a paragraph that can be linked to. ^my-block-id
For lists and quotes, add the block ID on a separate line:
> This is a quote
> With multiple lines
^quote-id
[[##heading]] Search for headings containing "heading"
[[^^block]] Search for blocks containing "block"
[Display Text](Note%20Name.md)
[Display Text](Note%20Name.md#Heading)
[Display Text](https://example.com)
[Note](obsidian://open?vault=VaultName&file=Note.md)
Note: Spaces must be URL-encoded as %20 in Markdown links.
![[Note Name]]
![[Note Name#Heading]]
![[Note Name#^block-id]]
![[image.png]]
![[image.png|640x480]] Width x Height
![[image.png|300]] Width only (maintains aspect ratio)
![[audio.mp3]]
![[audio.ogg]]
![[document.pdf]]
![[document.pdf#page=3]]
![[document.pdf#height=400]]
![[Note#^list-id]]
Where the list has been defined with a block ID:
- Item 1
- Item 2
- Item 3
^list-id
```query
tag:#project status:done
```
> [!note]
> This is a note callout.
> [!info] Custom Title
> This callout has a custom title.
> [!tip] Title Only
> [!faq]- Collapsed by default
> This content is hidden until expanded.
> [!faq]+ Expanded by default
> This content is visible but can be collapsed.
> [!question] Outer callout
> > [!note] Inner callout
> > Nested content
| Type | Aliases | Description |
|---|---|---|
note |
- | Blue, pencil icon |
abstract |
summary, tldr |
Teal, clipboard icon |
info |
- | Blue, info icon |
todo |
- | Blue, checkbox icon |
tip |
hint, important |
Cyan, flame icon |
success |
check, done |
Green, checkmark icon |
question |
help, faq |
Yellow, question mark |
warning |
caution, attention |
Orange, warning icon |
failure |
fail, missing |
Red, X icon |
danger |
error |
Red, zap icon |
bug |
- | Red, bug icon |
example |
- | Purple, list icon |
quote |
cite |
Gray, quote icon |
.callout[data-callout="custom-type"] {
--callout-color: 255, 0, 0;
--callout-icon: lucide-alert-circle;
}
- Item 1
- Item 2
- Nested item
- Another nested
- Item 3
* Also works with asterisks
+ Or plus signs
1. First item
2. Second item
1. Nested numbered
2. Another nested
3. Third item
1) Alternative syntax
2) With parentheses
- [ ] Incomplete task
- [x] Completed task
- [ ] Task with sub-tasks
- [ ] Subtask 1
- [x] Subtask 2
> This is a blockquote.
> It can span multiple lines.
>
> And include multiple paragraphs.
>
> > Nested quotes work too.
Use `backticks` for inline code.
Use double backticks for ``code with a ` backtick inside``.
```
Plain code block
```
```javascript
// Syntax highlighted code block
function hello() {
console.log("Hello, world!");
}
```
```python
# Python example
def greet(name):
print(f"Hello, {name}!")
```
Use more backticks or tildes for the outer block:
````markdown
Here's how to create a code block:
```js
console.log("Hello")
```
````
| Header 1 | Header 2 | Header 3 |
|----------|----------|----------|
| Cell 1 | Cell 2 | Cell 3 |
| Cell 4 | Cell 5 | Cell 6 |
| Left | Center | Right |
|:---------|:--------:|---------:|
| Left | Center | Right |
Escape pipes with backslash:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for obsidian-markdown matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend obsidian-markdown for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
obsidian-markdown fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
obsidian-markdown fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend obsidian-markdown for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
obsidian-markdown reduced setup friction for our internal harness; good balance of opinion and flexibility.
obsidian-markdown has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: obsidian-markdown is focused, and the summary matches what you get after install.
obsidian-markdown is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
obsidian-markdown reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 28