agent-creator

Scaffold vexjoy-agent operator .md files with YAML frontmatter and routing contracts.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill agent-creator-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-creator
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/meta/agent-creator
Command: npx skills add https://github.com/notque/vexjoy-agent --skill agent-creator-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates properly structured vexjoy-agent operator .md files so new agents don’t ship with broken routing, missing required fields, or non-compliant instruction patterns.

Core Features & Use Cases

  • DISCOVER overlap protection: checks for existing domain coverage and steers you to references instead of duplicating an agent.
  • DESIGN routing and contract planning: defines role, triggers, pairs_with, allowed tools, complexity tier, and creates tight boundaries with redirect targets.
  • SCAFFOLD deterministic scaffolding: generates the full operator file layout (phases, gates, error handling, reference loading table) and validates YAML structure and positive-instruction compliance.
  • REGISTER and VALIDATE readiness: updates agents/INDEX.json and runs reference/structure validation scripts so the router can reliably discover and execute the new agent.

Quick Start

Scaffold a new vexjoy-agent operator file by running the agent-creator workflow for your agent name and domain, then follow the phase gates to ensure routing triggers, pairs_with, and reference loading tables are correct before registration and validation.

Frequently Asked Questions about agent-creator

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

FAQPage Schema
How do I scaffold agent operator files with correct YAML frontmatter and routing contracts?

Scaffolding agent operator files requires generating a full `.md` layout with phases, gates, and a reference loading table, then validating YAML frontmatter fields and routing triggers for strict compliance.

What is agent scaffolding and when do I need workflow gates and routing triggers?

Agent scaffolding creates structured `.md` files defining agent boundaries and execution phases. You need workflow gates and routing triggers to ensure deterministic validation and reliable router discovery.

How to validate operator file structure and prevent overlapping domain agent coverage?

Validating operator file structure involves running reference and structure validation scripts. To prevent overlap, a discovery phase checks existing domain coverage and redirects you to references.

Does agent scaffolding require specific fields in the YAML frontmatter for CI validation?

Yes, agent scaffolding requires specific YAML frontmatter fields including name, description, routing triggers, pairs_with, complexity, category, allowed-tools, and user_invocable for deterministic CI validation.

Why does my new agent fail routing validation during the registration phase?

Routing validation fails during registration when the operator `.md` file has missing required YAML fields, broken routing contracts, or non-compliant instruction patterns that fail the deterministic validation scripts.