CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-settings

This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.

84

1.84x
Quality

79%

Does it follow best practices?

Impact

94%

1.84x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/plugin-dev/skills/plugin-settings/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 concrete, executable bash and real plugin examples, but it is significantly over-long and repetitive, inlining material that duplicates the reference files and assuming little of Claude's knowledge. Progressive disclosure is undermined by a missing examples/ directory referenced in the text and by content that should live in the bundled references being kept inline.

Suggestions

Trim the body to an overview and move the repeated sed/grep parsing snippets and full hook implementations into references/ (which already hold them), keeping SKILL.md to the pattern, one minimal example, and the file index.

Either create the referenced examples/ directory (read-settings-hook.sh, create-settings-command.md, example-settings.md) or remove those dangling references so every cited path resolves.

Cut beginner-level explanations (what YAML frontmatter is, gitignore basics, quote escaping) and de-duplicate the frontmatter-extraction recipe so it appears once in Quick Reference rather than in four sections.

DimensionReasoningScore

Conciseness

At 544 lines the body is noticeably verbose, repeating the same sed/grep frontmatter-extraction snippets across Reading Settings, Parsing Techniques, Common Patterns, and Quick Reference, and restating basics Claude already knows (what YAML frontmatter is, gitignore, quote escaping) rather than assuming competence.

2 / 5

Actionability

Provides copy-paste-ready bash (sed/awk frontmatter extraction, jq JSON construction, atomic update pattern, numeric-range validation) plus complete real hook implementations for multi-agent-swarm and ralph-loop, covering the common cases concretely.

5 / 5

Workflow Clarity

A 7-step Implementation Workflow and a Quick Exit validation pattern (check file exists, check enabled) give a clear sequence with most checkpoints present; it falls short of 5 because the settings-creation flow lacks an explicit validate->fix->retry feedback loop.

4 / 5

Progressive Disclosure

Section structure and real references exist (references/parsing-techniques.md, references/real-world-examples.md, scripts/validate-settings.sh, scripts/parse-frontmatter.sh), but ~544 lines of inlined content duplicate the two reference files and the body points to an examples/ directory (read-settings-hook.sh, create-settings-command.md, example-settings.md) that does not exist in the bundle.

3 / 5

Total

14

/

20

Passed

Description

95%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 is strong: it clearly states the pattern it documents, provides a rich set of natural trigger phrases including the file extension, and explicitly pairs a 'what' with a 'when' clause in third person. The only soft spot is that the stated action is a single 'documents/storing' verb rather than a list of several concrete capabilities.

DimensionReasoningScore

Specificity

Names the concrete mechanism ("Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content") but describes a single documenting/storing action rather than enumerating several distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Documents the .claude/plugin-name.local.md pattern...") and when ("This skill should be used when the user asks about... or wants to make plugin behavior configurable") with concrete trigger phrases, in third person.

5 / 5

Trigger Term Quality

Comprehensive quoted trigger phrases including synonyms and the file extension — "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings" — matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (the local .local.md plugin settings pattern) with distinctive triggers like ".local.md files" and "plugin state files", giving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (545 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
anthropics/claude-plugins-official
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.