configured-agent
A pattern for storing plugin configuration in project-specific local markdown files.
Install
mkdir -p .claude/skills/configured-agent && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/430" && unzip -o skill.zip -d .claude/skills/configured-agent && rm skill.zipInstalls to .claude/skills/configured-agent
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Store plugin configuration in .claude/plugin-name.local.md
- →Read YAML frontmatter for structured settings
- →Parse markdown body for supplementary instructions
- →Implement quick-exit patterns in bash hooks
- →Manage per-project plugin state and flags
How it works
The pattern uses a local markdown file with YAML frontmatter to store settings, which hooks and commands parse using standard shell utilities like sed and awk.
Inputs & outputs
When to use configured-agent
- →Setting per-project plugin flags
- →Configuring plugin-specific behavior
- →Storing persistent plugin state per repository
- →Defining plugin-specific instructions
About configured-agent
Allows plugins to read structured settings from .claude/[plugin-name].local.md files. Supports YAML frontmatter for configuration and markdown for supplementary instructions.
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.
When not to use it
- →Storing sensitive credentials or secrets
- →Sharing configuration across different users
- →Storing data that must be committed to version control
Prerequisites
Limitations
- →Requires a Claude Code restart to apply configuration changes
- →Hooks cannot be hot-swapped during a session
How it compares
Unlike hardcoded configurations, this approach allows per-project settings that are user-managed and excluded from version control.
Compared to similar skills
configured-agent side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| configured-agent (this skill) | 5 | 12mo | Review | Beginner |
| changelog-automation | 8 | 5mo | Review | Intermediate |
| plugin-settings | 2 | 9mo | Review | Beginner |
| skill-builder | 4 | 9mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by anthropics
View all by anthropics →You might also like
changelog-automation
wshobson
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
plugin-settings
anthropics
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.
skill-builder
ruvnet
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.
skill-creator-doctor
ananddtyagi
Create, repair, maintain, and consolidate skills. This skill should be used when users want to create new skills, fix broken skills that won't load, diagnose skill system issues, maintain skill health, or consolidate duplicate/obsolete skills. Automatically detects and repairs common skill loading problems including missing registry entries, metadata format issues, and structural problems. Provides comprehensive skill ecosystem management including duplicate detection, merge workflows, and archival processes.
slash-command-creator
greatSumini
Guide for creating Claude Code slash commands. Use when the user wants to create a new slash command, update an existing slash command, or asks about slash command syntax, frontmatter options, or best practices.
obsidian-core-workflow-a
jeremylongshore
Execute Obsidian primary workflow: note manipulation and vault operations. Use when implementing file operations, frontmatter handling, or programmatic note creation and modification. Trigger with phrases like "obsidian vault operations", "obsidian file manipulation", "obsidian note management".