CtrlK
BlogDocsLog inGet started
Tessl Logo

obsidian-layout-adjustment

Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets. Also use it when the user says a visual CSS change did nothing, still looks wrapped, is not lifted, is unreadable, or needs to be refactored without changing the current appearance.

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%Weight 40%Scale 1-5

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 operating loop, screenshot verification gate, and recovery feedback loops, plus a cleanly signaled one-level-deep reference. Minor conciseness gains are available in the duplicated mapping tables.

Suggestions

Trim the Stable Layer Stack table in SKILL.md since the full selector mapping already lives in references/workflow-reference.md; keep only a brief pointer.

Add the literal Obsidian reload command (or the 'reload snippets' setting action) alongside the screenshot step so the reload action is copy-paste ready.

Consolidate the Change-Type Split and What To Change First lists, which overlap on treatment guidance, to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the Stable Layer Stack table and some list-heavy sections overlap with the reference and could be tightened slightly.

4 / 5

Actionability

Provides concrete paths and commands (appearance.json, enabledCssSnippets, snippet-archive, screencapture -R, AppleScript frontmost check); minor gap is the lack of a literal reload command.

4 / 5

Workflow Clarity

The 13-step Operating Loop is clearly sequenced with explicit checkpoints (save checkpoint, re-read exact block, screenshot gate) and feedback loops (restore on failure, restore last good checkpoint after two failed directions).

5 / 5

Progressive Disclosure

SKILL.md is an overview that clearly signals a one-level-deep reference (references/workflow-reference.md, verified present) with explicit trigger conditions for when to read it; detailed selector tables are appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 explicitly states both the capability and the trigger conditions, with rich natural trigger terms drawn from real user phrasing. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists many concrete restyling actions across the Obsidian surface (restyle, tune layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, CSS snippets) with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (changing how Obsidian looks via CSS snippets) and 'when' (two explicit 'Use this whenever/also use it when...' clauses with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger vocabulary including both request phrasing ('restyle', 'tune a vault's visual layout') and the user's own complaint phrases ('did nothing', 'still looks wrapped', 'is not lifted', 'is unreadable').

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Obsidian CSS snippet restyling) with distinct, domain-specific triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

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
Ar9av/obsidian-wiki
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.