CtrlK
BlogDocsLog inGet started
Tessl Logo

obsidian-writer

Write well-formatted notes to the atmosphere-vault Obsidian knowledge base. Use this skill whenever creating or updating an ADR, runbook, plan, API doc, guide, session output, or any structured document that should land in the vault — even when the user doesn't say "Obsidian" explicitly. Delegates to obsidian:obsidian-cli to write to the live vault and applies Atmosphere frontmatter and formatting standards.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear sequenced workflow, a verification step, and a properly signaled one-level reference file. Its main weakness is redundancy: directory mappings and CLI command examples are repeated across sections.

Suggestions

Collapse the directory mapping that appears in 'When to Use', the 'Quick Reference' table, and 'Frontmatter Standards' into a single source (e.g., the quick-reference table) to remove repetition.

Merge the 'Key obsidian-cli Patterns' section into the Workflow steps (or vice versa) so each command pattern appears once.

Add an explicit 'if the read-back does not match, fix and re-write' feedback loop to the Verify step to strengthen error recovery for the live-vault write.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but directory mappings are repeated across 'When to Use', the 'Quick Reference' table, and 'Frontmatter Standards', and the obsidian-cli commands appear in both the Workflow steps and the 'Key obsidian-cli Patterns' section — the kind of tightening the score-2 anchor describes rather than the lean score-3 example.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands ('obsidian search query="..." limit=5', 'obsidian create name="..." path="..."', 'obsidian append file="..." content="..."') plus concrete frontmatter templates, matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear five-step sequence (identify type → search → compose → write → verify-and-link) with an explicit verification checkpoint ('read the note back to confirm content landed correctly'), so it is not capped at 2; it meets the score-3 anchor for a clear sequence with validation.

3 / 3

Progressive Disclosure

The body is an overview that repeatedly and clearly signals a single one-level-deep reference ('Read references/vault-structure.md for the complete frontmatter field table'), and that reference file exists and holds the full directory map and field reference — matching the score-3 anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and when to use it, with concrete doc-type triggers and a distinct vault-scoped niche. It is concise yet complete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Write well-formatted notes', 'creating or updating an ADR, runbook, plan, API doc, guide, session output', 'Delegates to obsidian:obsidian-cli to write to the live vault', 'applies Atmosphere frontmatter and formatting standards' — matching the score-3 anchor rather than the partial coverage of score 2.

3 / 3

Completeness

Explicitly answers both what ('Write well-formatted notes... Delegates to obsidian:obsidian-cli... applies Atmosphere frontmatter') and when ('Use this skill whenever creating or updating an ADR, runbook, plan, API doc, guide, session output'), satisfying the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'ADR', 'runbook', 'plan', 'API doc', 'guide', 'Obsidian', 'vault' — and explicitly notes triggering 'even when the user doesn't say Obsidian explicitly', giving good coverage rather than the sparse keyword set of score 2.

3 / 3

Distinctiveness Conflict Risk

Tied to a named 'atmosphere-vault Obsidian knowledge base' with a distinct doc-type vocabulary and a specific delegated CLI, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Atmosphere/atmosphere
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.