agent-delegation-edho-ferdian

Delegates tasks to named agent roles via Hermes delegate_task with prebuilt system prompts.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill agent-delegation-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-delegation-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.hermes/skills/agent-delegation-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill agent-delegation-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hermes' delegate_task tool is goal-based and has no static per-agent file format, so every delegation to a recurring role would otherwise require writing an ad-hoc persona prompt from scratch, producing inconsistent agent behavior across sessions. ## Core Features & Use Cases - Named Agent Roster: Provides ready-made delegation prompts for the edho-ferdian ecosystem's agents (code review, backend engineering, build fixing, billing ops, API design, and more), each generated from the canonical agents/*/AGENT.md definitions. - Role-Aware Delegation: Specifies whether each agent should run as role="leaf" or role="orchestrator", including guidance on Hermes' delegation.max_spawn_depth setting for nested delegation. - Use Case: When a task calls for a senior-engineer code review inside Hermes, delegate to code-reviewer-edho-ferdian using the provided delegate_task call instead of improvising a reviewer persona, keeping behavior identical to the canonical agent definition. ## Quick Start Ask the assistant to delegate the current code review task to the code-reviewer agent using this skill's delegation roster.

Frequently Asked Questions about agent-delegation-edho-ferdian

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

FAQPage Schema
How do I delegate a task to a named agent in Hermes?

Call Hermes' delegate_task tool with role="leaf" and pass the agent's system prompt from this roster as the context parameter. This gives the delegate the same persona as the canonical agent definition instead of an improvised prompt.

What is the difference between leaf and orchestrator roles in Hermes delegation?

A leaf agent executes its scoped task and reports back, while an orchestrator can delegate further to sub-agents. Orchestrator only works if Hermes' delegation.max_spawn_depth is set to 2 or higher; at the default of 1 it is silently forced back to leaf.

Why does nested agent delegation not work in Hermes by default?

Hermes defaults delegation.max_spawn_depth to 1, which blocks agent-to-agent delegation and silently downgrades orchestrator roles to leaf. Check the setting with hermes config get delegation.max_spawn_depth before relying on nested delegation.

Can I edit the agent prompts in this skill directly?

No. The file is generated from the ecosystem's canonical agents/*/AGENT.md definitions and must be regenerated with scripts/export_agents_hermes.py. Hand edits would drift from the canonical definitions used by other harnesses.

When should I use an agent delegate instead of the skill directly?

Delegate when the task justifies isolated or parallel execution, such as a whole-app audit or an independent adversarial critique. Small, single-step tasks should use the corresponding skill directly to avoid delegation overhead.