watcher-hermes/hermes-skills/actor-runtime

Claude Code and agent skill by watcher-hermes/hermes-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Build an AutoGen v0.4-shaped actor runtime with private state, inbox-per-actor, message-only IPC, fault isolation, and a dead-letter queue.

Install

npx vskill@latest install watcher-hermes/hermes-skills/actor-runtime

SKILL.md

The same SKILL.md was published earlier as watcher-hermes/hermes-skills/actor-runtime.

Given a multi-agent task, produce an actor runtime and the agent actors needed.

Produce:

  1. A Message type with sender, recipient, topic, body, mid.
  2. An Actor base class with receive(message, runtime). Actor state is private.
  3. A Runtime with a shared queue, send(), run_until_idle(), and a dead-letter queue. Exceptions in handlers go to DLQ; do not propagate.
  4. One topology helper: RoundRobin (fixed rotation), Selector (LLM picks next), or custom broadcast.
  5. Observability hooks per message: emit OTel spans with gen_ai.agent.name and gen_ai.operation.name per Lesson 23.

Hard rejects:

  • Synchronous message passing that blocks the sender until the recipient returns. That is the v0.2 model; it breaks fault isolation.
  • Shared mutable state across actors. Actors read state via messages or not at all.
  • A runtime that propagates handler exceptions. Failures belong in the DLQ; let other actors keep running.

Refusal rules:

  • If the task has only two actors with a fixed back-and-forth, refuse the actor framing and suggest a prompt chain (Lesson 12). Actors earn cost when there are >=3 actors or async concurrency.
  • If the user wants "synchronous mode" for "easier debugging," refuse. Suggest logging + tracing (Lesson 23) instead.
  • If the domain is strictly request/response with a single specialist, suggest routing (Lesson 12) instead of an actor team.

Output: message.py, actor.py, runtime.py, teams.py, README.md explaining DLQ policy, the topology choice, and how OTel spans are wired. End with "what to read next" pointing to Lesson 25 (multi-agent debate) if actors negotiate, Lesson 23 (OTel) if tracing is required, or Microsoft Agent Framework if you want the forward-looking runtime.

Security

  • Security scanPassed, 98 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/watcher-hermes/hermes-skills/actor-runtime/badge)](https://verified-skill.com/skills/watcher-hermes/hermes-skills/actor-runtime)

Something wrong with this skill or its page? Tell us.