Create Specialist Agent

Create unified specialist agents with runtime persona switching and JSON plan output.

Updated Oct 27, 2025
One-click install
npx skills add https://github.com/jmbish04/core-github-api --skill create-specialist-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create Specialist Agent
Source: https://github.com/jmbish04/core-github-api/tree/main/.agent/skills/create_specialist_agent
Command: npx skills add https://github.com/jmbish04/core-github-api --skill create-specialist-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for implementing a new persona or specialist agent using the unified SpecialistAgent pattern and Workshop UI.

Core Features & Use Cases

  • One flexible Honi-based specialist module created with createAgent(...) that adapts runtime persona via systemPrompt/specialty parameter.
  • Centralized registry update so new specialists appear in the UI through /api/agents/specialists; frontend auto-discovers.
  • Plan generation workflow: a JSON plan is produced for downstream execution via a save_plan tool; memory-aware utilities and shared tooling support this workflow.
  • Keeps code DRY by sharing tooling, memory, and interface conventions across specialists.

Quick Start

Create a new specialist module using createAgent(...) and register it in the specialists registry so it appears in AgentSidebar.

Frequently Asked Questions about Create Specialist Agent

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

FAQPage Schema
How do I create a unified specialist agent that switches personas at runtime?

A unified specialist agent uses a single createAgent(...) module that adapts its persona at runtime via the systemPrompt or specialty parameter to handle specialized tasks like UX, Data, or SRE workflows.

How do I register a new specialist agent so it auto-discovers in the frontend UI?

You register a specialist agent by updating the centralized specialists registry, which exposes the new agent through the /api/agents/specialists endpoint so the frontend AgentSidebar automatically discovers and displays it.

What is the best way to generate a JSON plan for downstream Kanban-driven execution?

The best way to generate a JSON plan for Kanban-driven execution is to use the save_plan tool within the specialist agent workflow, which persists the output via Drizzle-based storage for downstream processing.

Does the specialist agent pattern work for both frontend and backend workflows?

Yes, the specialist agent pattern applies to both frontend and backend workflows, allowing a single adaptable agent core to switch personas and fulfill specialized tasks across the entire tech stack.

How do I keep tooling and memory conventions DRY across multiple specialist agents?

You keep code DRY by sharing tooling, memory-aware utilities, and interface conventions across all specialists through the unified SpecialistAgent pattern and its centralized registry.