cursor-subagent-creator

Create Cursor subagent definitions with required frontmatter fields and standardized prompts.

1|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill cursor-subagent-creator-ramonsdka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cursor-subagent-creator
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/cursor-subagent-creator
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill cursor-subagent-creator-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cursor subagent creation consolidates the process of designing focused, context-isolated agents for the Cursor editor, ensuring consistent structure and safe prompts.

Core Features & Use Cases

  • Provides a standardized blueprint for frontmatter (name, description, model, readonly, is_background).
  • Outlines the required subagent file layout, including optional directories (scripts/, references/, assets/) and the location for project-specific subagents.
  • Supports automatic delegation patterns and explicit invocation guidelines to keep workflows predictable.

Quick Start

Create a new subagent in .cursor/agents named your-subagent and define its frontmatter and prompt following this guide.

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 context-isolated subagents in Cursor for multi-step workflows?

Cursor subagent creation enforces required frontmatter fields like name, description, model, readonly, and is_background to generate standardized, context-isolated agent definitions for safe, reusable execution.

What frontmatter fields are required for a Cursor subagent configuration?

A Cursor subagent configuration requires name, description, model, readonly, and is_background frontmatter fields to enforce predictable workflows and maintain consistent file layouts.

How do I structure the file layout for a Cursor subagent?

Structuring a Cursor subagent file layout involves placing the definition in .cursor/agents and utilizing optional directories like scripts/, references/, and assets/ for project-specific resources.

When should I use context-isolated subagents in Cursor workflows?

Use context-isolated subagents in Cursor workflows when your project requires multi-step automation, versioned agents, and frontmatter-driven configuration to keep workflows predictable and safe.

Does automatic delegation work with frontmatter-driven Cursor subagents?

Automatic delegation patterns work with frontmatter-driven Cursor subagents by applying explicit invocation guidelines that keep multi-step workflows predictable and isolated.