Name: state-directory-manager
Rating: 76.5 (1 reviews)
Author: majiayu000

Blog Docs Log in Get started

state-directory-manager

Manage persistent state directories for bash scripts

2.96x

Quality

56%

Does it follow best practices?

Impact

89%

2.96x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bash/state-directory-manager-vamseeachanta-workspace-hub/SKILL.md

The canonical home for this skill is state-directory-manager in majiayu000/claude-skill-registry

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 content is highly actionable with executable bash patterns, but it is padded by a duplicated complete module, lacks validation around destructive operations, and inlines content that belongs in a bundled script file.

Suggestions

Move the 'Complete Example: State Manager Module' into a bundled scripts/state-manager.sh and replace the inline copy with a short pointer, eliminating the duplication with sections 3-6.

Add validation checkpoints before destructive calls (e.g. confirm state_reset, guard cache_clear with a confirmation, test-find before -delete) so destructive workflows can score above 3.

Trim or consolidate the per-section init functions so the skill reads as one canonical implementation rather than six variants plus a full re-implementation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable code, but the 200-line 'Complete Example: State Manager Module' re-implements the config/state/cache/log functions already shown in sections 3-6, which is padded duplication that could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready bash functions covering config, state, cache, and log management with concrete usage examples, matching the 'fully executable, copy-paste ready' anchor.	5 / 5
Workflow Clarity	Sequences exist, but destructive operations (state_reset runs 'rm -rf $STATE_BASE_DIR', cache_clear, find -delete) have no validation checkpoints, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Sections are well-organized, but with no bundle files the ~680-line body inlines a reusable module that should be a separate state-manager.sh file, and 'source /path/to/state-manager.sh' references a file that is not bundled.	3 / 5
	Total	14 / 20 Passed

Description

48%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 names a clear, fairly specific domain but relies on one generic verb and omits any 'Use when' trigger guidance, leaving it mid-range on completeness and specificity.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, read, and rotate persistent state, config, and cache directories for bash scripts'.

Append an explicit trigger clause, e.g. 'Use when a bash script needs to persist data, config, or cache between runs, or when following the XDG Base Directory specification'.

Add natural synonyms users actually say (config, cache, XDG, persist data) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description uses a single generic verb ("Manage") plus a domain ("persistent state directories for bash scripts"), matching the anchor 'Names the domain but actions are minimal or generic' rather than the multi-action anchor above.	2 / 5
Completeness	It clearly states the 'what' but has no 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger guidance; it is not a 4 because 'when' is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	It includes relevant natural terms ("persistent state", "state directories", "bash scripts") but omits common variations and synonyms a user might say (config, cache, XDG, save/persist state).	3 / 5
Distinctiveness Conflict Risk	The bash state-directory niche is mostly distinct with only minor overlap risk against general config/directory-management skills; it falls short of 5 because 'Manage' is broad enough to brush adjacent skills.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (690 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: majiayu000/claude-skill-registry-data
Path: bash/state-directory-manager-vamseeachanta-workspace-hub/SKILL.md
Commit: a1e9f44

Reviewed: about 19 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.