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.
Install with Tessl CLI
npx tessl i github:anthropics/claude-plugins-official --skill plugin-settingsOverall
score
88%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
90%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the 'what' portion focuses on documentation rather than concrete actions Claude would perform. The description could be improved by specifying actionable capabilities like 'create', 'read', or 'modify' plugin configuration files.
Suggestions
Replace 'Documents the pattern' with concrete actions like 'Creates, reads, and modifies plugin configuration files using the .claude/plugin-name.local.md pattern'
Add specific use cases such as 'storing API keys', 'saving user preferences', or 'persisting plugin state between sessions' to clarify practical applications
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (plugin configuration) and mentions specific elements like 'YAML frontmatter', '.local.md files', and 'per-project plugin settings', but the core action is vague - 'Documents the pattern' rather than concrete actions like 'create', 'read', 'modify', or 'validate'. | 2 / 3 |
Completeness | Explicitly answers both what ('Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content') and when ('should be used when the user asks about...' with explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'plugin settings', 'store plugin configuration', 'user-configurable plugin', '.local.md files', 'plugin state files', 'read YAML frontmatter', 'per-project plugin settings'. These are specific and varied. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific triggers like '.local.md files', 'plugin-name.local.md pattern', and 'per-project plugin settings'. Unlikely to conflict with general YAML or markdown skills due to the specific plugin configuration context. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill document with excellent actionability - nearly every concept has executable bash code. The workflow clarity is good with validation patterns and security considerations. The main weakness is some redundancy in showing the same parsing patterns multiple times, which inflates the document length without adding proportional value.
Suggestions
Consolidate the frontmatter parsing examples into a single 'Parsing Reference' section and reference it from other sections instead of repeating the sed commands 4+ times
Remove or significantly condense the 'Real-World Examples' section as it largely repeats patterns already shown in 'Common Patterns'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the same parsing patterns are shown multiple times (frontmatter extraction appears 4+ times), and some explanations could be tightened. The 'Real-World Examples' section largely repeats earlier content. | 2 / 3 |
Actionability | Excellent executable code throughout - bash scripts are complete and copy-paste ready, file templates are concrete, and parsing patterns include actual sed/awk commands. Every pattern has working code examples. | 3 / 3 |
Workflow Clarity | Clear workflows with explicit validation steps (e.g., 'Validate settings values' section with range checking), quick-exit patterns for safety, and the 'Implementation Workflow' section provides a clear 7-step process. Security considerations include path traversal validation. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, organized sections, and appropriate references to external files (references/, examples/, scripts/). The 'Quick Reference' section provides a scannable summary. References are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
82%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- 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.