cursor-subagent-creator

Create Cursor subagents with standardized frontmatter in .cursor/agents/.

59|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/guilhermemarketing/esc-skills --skill cursor-subagent-creator-guilhermemarketing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cursor-subagent-creator
Source: https://github.com/guilhermemarketing/esc-skills/tree/main/skills/cursor-subagent-creator
Command: npx skills add https://github.com/guilhermemarketing/esc-skills --skill cursor-subagent-creator-guilhermemarketing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cursor subagent creation is often tedious and error-prone due to the need to follow Cursor's patterns, directory conventions, and frontmatter structure. This skill provides a standardized template and guidance to create subagents with isolated contexts, ensuring consistency across projects.

Core Features & Use Cases

  • Standardized frontmatter templates for new subagents.
  • Validation of folder structure and optional components (scripts, references, assets).
  • Clear invocation patterns for automatic delegation and explicit requests.
  • Supports versioning and documentation of subagent prompts.

Quick Start

Create a new Cursor subagent following the standard frontmatter and place it in .cursor/agents/.

Frequently Asked Questions about cursor-subagent-creator

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

FAQPage Schema
How do I create Cursor subagents with isolated contexts for multi-step workflows?

To create Cursor subagents with isolated contexts, use a standardized template that satisfies frontmatter metadata, required fields, and structured prompt conventions, placing the definitions in the .cursor/agents/ directory.

What is the correct folder structure and frontmatter format for a Cursor subagent?

The correct frontmatter format for a Cursor subagent requires standardized metadata fields and structured prompt definitions located within the .cursor/agents/ directory, alongside optional components like scripts, references, and assets.

Why does my Cursor subagent delegation fail to follow project patterns?

Cursor subagent delegation often fails when definitions lack standardized frontmatter, required fields, or proper placement in the .cursor/agents/ directory, disrupting verifiable specialization for complex workflows.

Can I use automated templates to generate Cursor subagent prompts?

Yes, you can use automated templates to generate Cursor subagent prompts, which streamlines validation of folder structures, enforces required frontmatter fields, and supports versioning and documentation of the resulting AI agents.

When do I need to set up isolated context subagents in Cursor?

You need to set up isolated context subagents in Cursor when managing complex multi-step workflows that require verifiable specialization, ensuring consistency across projects through standardized prompt conventions and metadata.