dotfiles-manager

Comprehensive knowledge of dotfiles management, configuration file organization, symlink strategies, and cross-platform environment setup. Use when the user needs to organize, sync, or deploy dotfiles and development configurations.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/dotfiles-manager/SKILL.md

Quality

Content

65%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.

The body is highly actionable with complete, executable scripts and a clear sequence, but it is padded with concepts Claude already knows, lacks validation checkpoints around destructive stow operations, and inlines all detail rather than progressively disclosing it. These keep conciseness, workflow clarity, and progressive disclosure at the mid-level.

Suggestions

Trim or remove the 'Common Configuration Files', 'Common Tools to Configure', and generic 'Core Principles'/'Best Practices' sections — Claude already knows what .zshrc, tmux, and vim are; keep only dotfiles-specific guidance.

Add validation/verification to the bootstrap and Makefile workflows (e.g., check for existing files and back them up before 'stow', verify symlinks resolved, fail-fast on missing stow) so the batch/destructive operations clear the workflow-clarity cap of 3.

Move the long bootstrap script, Makefile, and reference catalogs into separate files under references/ or scripts/ and link to them from SKILL.md, turning the body into a concise overview with one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code, but padded sections explain what Claude already knows — '.zshrc / .bashrc: Interactive shell config', '.gitconfig: Global Git settings', the 'Common Tools to Configure' list, and generic 'Core Principles'/'Best Practices' bullets — fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than a 4.	3 / 5
Actionability	Provides copy-paste-ready, fully executable guidance — the complete bootstrap script (install_deps/setup_symlinks/setup_plugins), the Makefile (install/bootstrap/update/clean), platform detection, and stow/dotbot examples — covering the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	The bootstrap script and Makefile give a clear sequence, but there are no validation checkpoints before or after batch/destructive operations like 'stow zsh vim tmux git' (which can clobber existing configs) or 'stow -D' clean — per the rubric this caps workflow clarity at 3 even though the sequence itself is coherent.	3 / 5
Progressive Disclosure	Good section headers give structure, but at 225 lines everything (bootstrap script, tool reference lists, config-file catalog) is inlined in one file with no one-level-deep references to separate materials, so it reads as a detailed monolith rather than an overview pointing outward — the simple-skill (<50 line) exception does not apply.	3 / 5
	Total	14 / 20 Passed

Description

87%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.

The description clearly states both what the skill covers and when to use it, with natural trigger terms and a distinct niche around dotfiles management. Its only weakness is a knowledge-framed 'what' clause that lists topics rather than crisp verb-actions.

Dimension	Reasoning	Score
Specificity	Quotes 'dotfiles management, configuration file organization, symlink strategies, and cross-platform environment setup' plus the trigger actions 'organize, sync, or deploy' — it lists several specific capabilities with only minor gaps, though the 'what' is framed as knowledge areas rather than direct verb-actions, keeping it just below a 5.	4 / 5
Completeness	Explicitly answers 'what' ('Comprehensive knowledge of dotfiles management...') and 'when' ('Use when the user needs to organize, sync, or deploy dotfiles and development configurations') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Quotes 'organize, sync, or deploy dotfiles and development configurations' — these are natural phrases a user would say, giving good keyword coverage; a few synonyms (e.g., 'manage', 'backup') are missing, so it falls short of the comprehensive-synonym bar for a 5.	4 / 5
Distinctiveness Conflict Risk	'dotfiles management' is a clear niche with distinct triggers ('dotfiles', 'symlink strategies') and minimal overlap risk with other skills; the broad 'development configurations' clause only marginally tempers this but does not pull it down to a 4.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: einverne/dotfiles
Path: claude/skills/dotfiles-manager/SKILL.md
Commit: 837e856

Reviewed: ~6 hours ago

Table of Contents

Discovery Implementation Validation

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.