hermes

Provide unified CLI access to Blueprint framework subcommands and data.

2|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/KwakYounHo/blueprint --skill hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes
Source: https://github.com/KwakYounHo/blueprint/tree/main/templates/claude-skills/hermes
Command: npx skills add https://github.com/KwakYounHo/blueprint --skill hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the critical problem of inconsistent communication in multi-agent systems. By providing immediate access to predefined, structured handoff forms, it ensures clear, standardized communication between different AI Workers, reducing misunderstandings and improving workflow efficiency.

Core Features & Use Cases

  • Handoff Form Viewer: Access predefined, structured forms for communication between specific Worker roles (e.g., Orchestrator to Specifier, Implementer to Reviewer).
  • Inter-Agent Communication Guide: Understand the expected input and output formats for each stage of a multi-agent workflow, ensuring seamless transitions.
  • List Available Handoffs: Quickly see all defined communication pathways and their corresponding forms, providing a complete overview of agent interactions.
  • Use Case: As an Orchestrator, when delegating a task to the 'Implementer' Worker, you need to ensure your instructions are in the correct format. Use Hermes to view the 'orchestrator to implementer' handoff form, guaranteeing clear and structured communication that the Implementer can immediately act upon.

Quick Start

Show me the handoff form for communication from the 'orchestrator' to the 'implementer'.

Frequently Asked Questions about hermes

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

FAQPage Schema
How do I standardize communication between AI agents in a workflow?

Standardized agent communication uses predefined handoff forms that define input and output formats for each stage. Hermes provides immediate access to structured handoff forms for specific worker role transitions, ensuring clear, consistent messaging that reduces misunderstandings and improves workflow efficiency across multi-agent systems.

What's the correct format for handing off a task from an orchestrator to an implementer?

Handoff format depends on the worker roles involved. Hermes retrieves the predefined handoff form for orchestrator-to-implementer communication, showing the exact structure and required fields so your instructions are immediately actionable by the receiving worker.

How do I view all available communication pathways between workers?

List all defined handoff forms to see every worker-to-worker communication pathway. Hermes queries the forms directory and worker registry, displaying all available handoffs so you understand which role transitions are supported in your workflow.

What information do I need before setting up inter-agent handoffs?

Set up inter-agent handoffs by accessing blueprint directories containing gates, templates, front-matters, and worker registries. Hermes reads these data sources via CLI subcommands to render handoff definitions, schemas, and worker listings needed for consistent agent orchestration.

Can I access worker registry and constitution data through the same tool?

Yes. Hermes provides unified CLI access to the Blueprint framework, including worker registry queries, constitution viewing, and schema access alongside handoff forms, all via bash-based subcommands under blueprint.sh.

What happens if agent handoff formats don't match between workflow stages?

Mismatched formats cause miscommunication and workflow breaks. Hermes prevents this by enforcing predefined, structured handoff forms for each worker transition, ensuring format consistency and reducing errors across multi-agent systems.