chat-to-obsidian

chat-to-obsidian is a skill for Claude Code from Howie126313/obsidian-vault-kit. It costs 72 tokens per session (680 once invoked), scanned A, original, Apache-2.0.

A tool that turns conversation content into a structured technical article and saves it as a note in an Obsidian vault, a folder of linked Markdown notes.

In plain words
What is it for?
Analyzing a discussion, organizing its technical lessons, adding relevant links, and writing the result into the appropriate Obsidian directory.
Why use it?
It saves the useful ideas, code, comparisons, and conclusions from a chat without leaving them buried in the conversation transcript.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the obsidian-vault-kit plugin — 6 skills shipped together

Good fit Analyzing a discussion, organizing its technical lessons, adding relevant links, and writing the result into the appropriate Obsidian directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/howie126313/obsidian-vault-kit/chat-to-obsidian
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Howie126313/obsidian-vault-kit --skill chat-to-obsidian
Clone the repo
git clone --depth 1 https://github.com/Howie126313/obsidian-vault-kit

Made for: Claude Code.

Or install obsidian-vault-kit, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for chat-to-obsidian

README.md
[![agentmods](https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/chat-to-obsidian/github.svg)](https://agentmods.dev/skills/howie126313/obsidian-vault-kit/chat-to-obsidian)
Your own site
<a href="https://agentmods.dev/skills/howie126313/obsidian-vault-kit/chat-to-obsidian"><img src="https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/chat-to-obsidian/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for chat-to-obsidian

Your own site · 80×15
<a href="https://agentmods.dev/skills/howie126313/obsidian-vault-kit/chat-to-obsidian"><img src="https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/chat-to-obsidian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 680 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.00680
Opus 5 $0.00036 $0.00340
Sonnet 5 $0.00014 $0.00136
Haiku 4.5 $0.00007 $0.00068

Measured 11d ago against content hash 4675d30cfb79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

chat-to-obsidian scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/chat-to-obsidian/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chat to Obsidian

Convert conversation content into a deep, well-structured technical article and save it to the Obsidian vault.

Workflow

Step 1: Environment Detection & Content Analysis

1a. Detect vault root — follow ../../_shared/common-steps.md "Vault Detection" section.

1b. Analyze conversation content:

  1. Identify the core topic(s) and key knowledge points discussed
  2. Extract code examples, diagrams, comparisons, and insights
  3. Determine the article's scope — what to include, what to skip

1c. Determine target directory — follow the Directory Mapping Rules in ../../_shared/common-steps.md. Use the article's primary topic to match.

1d. Search for bidirectional links — follow the Bidirectional Link Search in ../../_shared/common-steps.md.

Step 2: Write the Article

Follow the template in references/article-template.md strictly.

Key principles:

  • Not a conversation transcript — restructure, reorganize, and deepen the content
  • Scene-driven opening — start with a concrete engineering problem, not abstract definitions
  • Numbered sections (1, 2, 3...) with --- separators
  • Rich code examples with inline comments explaining key points
  • ASCII diagrams and tables for visualizing complex concepts
  • > **Key takeaway** blockquotes after key sections
  • Bold key terms with **bold**
  • Depth over breadth — go deep on each point rather than skimming many
  • Include [[wikilink]] connections identified in Step 1d
  • YAML frontmatter: title, date (today), tags (3-8), summary, source ("Claude conversation")

Step 3: Save and Confirm

3a. Save — follow the Save and Open in Obsidian section in ../../_shared/common-steps.md.

3b. Update index.md — follow the Index Update section in ../../_shared/common-steps.md. Use the article's title, summary (condensed to under 80 chars), and top 2 tags.

Read the full file on GitHub · 65 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 65 lines · 72 tokens per session scan A 4675d30cfb79

Subscribe to this mod's changes

chat-to-obsidian is a skill published in the GitHub repository Howie126313/obsidian-vault-kit (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 680 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

llm-wiki

Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…

praneybehl/llm-wiki-plugin · 221 tokens

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

google-ads-audit

Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…

nowork-studio/notfair-plugin · 86 tokens

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…

nowork-studio/notfair-plugin · 235 tokens

critical-code-reviewer

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

posit-dev/skills · 67 tokens

shiny-bslib

Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…

posit-dev/skills · 107 tokens