create-subagent

Create specialized AI subagents with YAML frontmatter and Markdown prompts.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill create-subagent-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-subagent
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.cursor/skills-cursor/create-subagent
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill create-subagent-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subagents enable specialized AI assistants to run in isolated contexts with custom prompts.

Core Features & Use Cases

  • Create project-level subagents under .cursor/agents/ to share within a team
  • Create user-level subagents under ~/.cursor/agents/ for personal use across projects
  • Define configuration via YAML frontmatter and implement system prompts in the Markdown body
  • Test and deploy subagents by invoking them with task descriptions, then reuse configurations across projects

Quick Start

Create the subagent file at your preferred location, add the required frontmatter fields, and write the system prompt in the body, then test by invoking the new agent.

Frequently Asked Questions about create-subagent

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

FAQPage Schema
How do I create specialized AI subagents for isolated workflows?

AI subagents are specialized assistants that run in isolated contexts with custom system prompts, enabling you to standardize agent configurations and reuse them across project-level or user-level automation workflows.

How do I set up project-level AI agents to share with my team?

Set up project-level AI agents by creating subagent Markdown files under the .cursor/agents/ directory, allowing standardized agent configurations to be shared within your team's codebase workflows.

Can I reuse custom AI agent configurations across multiple projects?

You can reuse custom AI agent configurations across multiple projects by placing the subagent Markdown files in the ~/.cursor/agents/ directory for user-level personal automation.

Do I need YAML frontmatter to define custom AI agent prompts?

YAML frontmatter is required to define custom AI agent prompts, specifically requiring name and description fields at the top of the Markdown file to properly configure the subagent behavior.

What are the limitations of extending AI subagent behavior with scripts?

Extending AI subagent behavior with scripts is limited to optional scripts, references, and assets directories alongside the main Markdown file, constraining behavior extensions to these specific structural boundaries.