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.

81

1.84x
Quality

Does it follow best practices?

Impact

94%

1.84x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is a thorough, largely actionable reference for the .local.md settings pattern, but it is held back by significant repetition, stub-filled hook examples, and references to example files that are not bundled. Tightening the redundancy and either adding or removing the dangling examples/* references would lift it.

Suggestions

De-duplicate the frontmatter parsing snippet: show it once in "Parsing Techniques" / the reference file and reference it elsewhere instead of repeating the full sed/grep blocks five times.

Provide the missing examples/read-settings-hook.sh, examples/create-settings-command.md, and examples/example-settings.md, or remove the "Example Files" listing and the "See examples/read-settings-hook.sh" pointer so no referenced path dangles.

Either complete the stubbed hook scripts (replace `# ...` / `# Apply strict validation` placeholders with real logic) or explicitly mark them as illustrative skeletons, and fold validation checkpoints into the workflow steps rather than isolating them in Best Practices.

DimensionReasoningScore

Conciseness

The body is accurate but padded: the sed frontmatter-extraction snippet is repeated five times, the "Quick Reference" section restates earlier sections, and the real-world examples re-show configs already presented under "Common Patterns".

2 / 3

Actionability

Parsing snippets (sed/grep/awk) are executable and copy-paste ready, but several hook scripts contain `# ...` placeholder logic, and the referenced "complete working example" examples/read-settings-hook.sh does not exist.

2 / 3

Workflow Clarity

A clear 7-step "Implementation Workflow" is present, but validation checkpoints live in a separate Best Practices section rather than inline in the workflows, and there is no validate→fix→retry feedback loop.

2 / 3

Progressive Disclosure

references/parsing-techniques.md, references/real-world-examples.md, and the two scripts/ files exist and are signaled, but the three referenced examples/* files (and the examples/ directory) are missing, and content duplicated inline could live in those reference files.

2 / 3

Total

8

/

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, well-constructed description: it states a clear niche, lists concrete actions, gives explicit trigger guidance, and stays in third person. It earns top marks across all dimensions with no fluff or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "storing plugin-specific configuration with YAML frontmatter and markdown content", "read YAML frontmatter", "make plugin behavior configurable" — rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ("Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration...") and when ("This skill should be used when the user asks about...").

3 / 3

Trigger Term Quality

Good coverage of natural phrases a user would say, including "plugin settings", ".local.md files", "plugin state files", and "per-project plugin settings", with several phrasing variations.

3 / 3

Distinctiveness Conflict Risk

The .local.md / YAML-frontmatter plugin-settings niche is specific and its triggers ("plugin state files", ".local.md files") are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.