create-agent

Create agent files with YAML frontmatter and system-prompt bodies.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/YurainSoon/research-director --skill create-agent-yurainsoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-agent
Source: https://github.com/YurainSoon/research-director/tree/main/.claude/skills/create-agent
Command: npx skills add https://github.com/YurainSoon/research-director --skill create-agent-yurainsoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The agent-definition framework helps users create, modify, or redesign an agent file for this project, ensuring consistent structure and clear boundaries between agent responsibilities and orchestrator control.

Core Features & Use Cases

  • Self-contained agent files with YAML frontmatter and a dedicated system-prompt body.
  • Guidance for frontmatter fields (name, description, model, tools) and optional settings, plus how to structure the body.
  • Use cases include writing, creating, updating, or redesigning agents and deciding how agent prompts should be structured.

Quick Start

Create an agent file with proper frontmatter and a self-contained system-prompt body as described.

Frequently Asked Questions about create-agent

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

FAQPage Schema
How do I define an agent with a system prompt and frontmatter?

Defining an agent requires YAML frontmatter specifying name, description, model, and tools, paired with a self-contained system-prompt body. This structure ensures clear boundaries between agent responsibilities and orchestrator control.

What is the required structure for an agent file in a workflow orchestrator?

An agent file structure requires YAML frontmatter for core settings like model and tools, and a dedicated body for the system prompt. Optional resources and guardrails can be added to guarantee safe, interoperable agent definitions.

How do I update or redesign an existing agent prompt?

Updating or redesigning an agent prompt involves modifying the self-contained system-prompt body while maintaining the required frontmatter fields. This ensures consistency across agent and orchestrator boundaries during prompt redesign.

Do I need specific tools to create self-contained agents?

No specific external tools are required to create self-contained agents. The framework automates the creation and management of agent definitions by specifying required frontmatter fields and body structure directly.

How do guardrails work when designing agent prompts?

Guardrails are optional settings included in the agent definition to guarantee safe, interoperable agent operations. They specify boundaries within the system prompt to maintain safe behavior across orchestrator workflows.

Can I use this framework to manage multiple agents in an orchestrator?

Yes, the framework automates management of self-contained agent definitions and ensures consistency across orchestrator boundaries. It standardizes frontmatter and prompt structure for safe interoperability between multiple agents.