anthropics-agent-identifier

Convert user requests into Claude Code agent configuration markdown files.

Updated Aug 27, 2026

Search Tags:#templates #validation #agent #claude-code #frontmatter #triggering #system-prompt

One-click install

npx skills add https://github.com/program-the-brain-not-the-heartbeat/dotfiles --skill anthropics-agent-identifier

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: anthropics-agent-identifier
Source: https://github.com/program-the-brain-not-the-heartbeat/dotfiles/tree/main/config/claude/skills/anthropics-agent-identifier
Command: npx skills add https://github.com/program-the-brain-not-the-heartbeat/dotfiles --skill anthropics-agent-identifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured blueprint to convert user requests into production-ready Claude Code agent configurations, ensuring consistent frontmatter, system prompts, triggering guidelines, and CLAUDE.md alignment. <example> Context: User wants to create a new agent configuration from plain language user: "I need an agent that handles code review scaffolding" assistant: "I'll generate the anthropics-agent-identifier configuration to standardize this agent." <commentary> Triggering this skill when a user requests a new agent skeleton or a standardized agent frontmatter. </commentary> </example> <example> Context: User asks for guidance on agent structure for Claude Code plugins user: "How should I define an agent frontmatter?" assistant: "I'll generate the proper metadata skeleton with frontmatter and system prompt." <commentary> User needs a concrete metadata skeleton; trigger anthropics-agent-identifier to produce it. </commentary> </example>

Core Features & Use Cases

Generate a unique identifier, frontmatter, and a complete agent skeleton from a user description.
Validate all required fields (name, description, model, color, dependencies, components) against CLAUDE.md guidance.
Produce a robust system prompt in second person with clear responsibilities and an explicit output format.
Include 2-4 triggering examples in the description to ensure reliable activation. <example>

Context: You want a production-ready agent for Code Plugins user: "Create an agent that reviews pull requests for code quality" assistant: "I'll use the anthropics-agent-identifier to generate the agent skeleton." <commentary> Proactive generation of the agent skeleton to match the requested task. </commentary> </example> <example> Context: User asks for agent frontmatter and system prompt blueprint user: "I need a metadata template for a code-generation agent" assistant: "I'll generate the anthropics-agent-identifier configuration to standardize this agent." <commentary> Ensures standardized frontmatter and system prompt structure. </commentary> </example>

Quick Start

From a user request, generate a complete agent markdown file with frontmatter, system prompt, examples, and optional resource directories.

Frequently Asked Questions about anthropics-agent-identifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a Claude Code agent from a plain text request?▼

To create a Claude Code agent, you convert a user request into a markdown file with validated frontmatter, defined triggering rules, and a comprehensive system prompt for autonomous operation.

What is the correct frontmatter structure for a Claude Code agent configuration?▼

The correct frontmatter structure for a Claude Code agent includes required fields like name, description, model, color, dependencies, and components, validated against CLAUDE.md guidance.

How do I write a system prompt for an autonomous Claude Code plugin agent?▼

You write a system prompt in second person with clear responsibilities, explicit output formats, and 2-4 triggering examples in the description to ensure reliable agent activation.

Can I generate a standardized agent skeleton from a simple description?▼

Yes, you can generate a unique identifier, frontmatter, and a complete agent skeleton directly from a user description to standardize agent creation for Claude Code.

Why are triggering examples needed in agent frontmatter descriptions?▼

Triggering examples are needed in agent frontmatter descriptions to ensure reliable activation of the agent when matching user requests occur during autonomous operation.