agentsclimarketplace

Obsidian markdown

Skill lionellau/capture-concept/skills/obsidian-markdown

Obsidian knowledge-distillery skill for Claude Code and Codex — AI-assisted concept capture, Markdown notes, and reusable learning maps for your vault.

Install
npx -y skills add lionellau/capture-concept --skill obsidian-markdown

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Required companion skill for writing Obsidian-native Markdown notes with YAML properties, wikilinks, callouts, embeds, block IDs, tags, aliases, MOCs, and graph-friendly note structure. Use whenever creating or editing notes in an Obsidian vault.

SKILL.md

2.4 KB, as published. Nobody here has run it

Obsidian Markdown

Use this skill whenever writing or editing notes inside an Obsidian vault.

Core Rules

  • Use YAML frontmatter for note properties.
  • Use Obsidian wikilinks for internal links: [[note-slug]] or [[note-slug|Title]].
  • Use heading links for precise references: [[note-slug#Heading]].
  • Use block IDs for reusable definitions or claims: ^definition, ^key-claim.
  • Use Obsidian callouts for scannable structure.
  • Use embeds only when the target exists: ![[note-slug#^definition]].
  • Keep sections chunkable; split sections that exceed about 300 words.

Frontmatter Pattern

---
title: "Human Title"
type: concept
domain: software-engineering
depth: working
scenario: S1
tags:
  - domain/software-engineering
  - status/active
  - topic/caching
  - source/conversation
related:
  - "cache-invalidation"
created: "2026-06-11"
updated: "2026-06-11"
confidence: medium
provenance: inferred
aliases:
  - "alternate name"
stub_candidates:
  - "missing-related-concept"
---

Callouts

Prefer these callouts:

  • > [!tldr] for retrieval hooks.
  • > [!note] for disambiguation.
  • > [!tip] for decision criteria or rules of thumb.
  • > [!warning] for pitfalls.
  • > [!failure]- for anti-patterns or dead ends.
  • > [!bug]- for known limitations or failure modes.
  • > [!quote] for attributed source claims.
  • > [!question]- for open questions and stubs.

Use foldable callouts with - when details are useful but not essential.

Tags

  • Use slash tags: domain/software-engineering, topic/debugging, source/article.
  • Do not use broad generic topic tags.
  • Keep topic tags specific and limited.
  • Prefer mechanism tags over surface-area tags.

Links

Only place verified existing notes in related:. Missing concepts belong in stub_candidates: until a note exists.

In the body, every related link should explain the relationship:

- [[cache-invalidation]] - broader failure class behind this bug.

MOCs And Indexes

MOCs should help navigation, not duplicate tags. Include:

  • Recent notes
  • Learning paths
  • Important gaps
  • Links grouped by practical use

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.