Skip to content
Automation
Agent

skill-eval-runner

Generic isolated-context runner — executes the analysis spec named in its dispatch and returns the structured output that spec defines. Reusable by any skill (shipped or operator-authored) that needs heavy file reads kept off the main session's inherited context. The calling

From plugin
claude-code-hermit
7411 skills11 agents
Install
> /plugin marketplace add gtapps/claude-code-hermit
> /plugin install claude-code-hermit@claude-code-hermit

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Generic isolated-context runner — executes the analysis spec named in its dispatch and returns the structured output that spec defines. Reusable by any skill (shipped or operator-authored) that needs heavy file reads kept off the main session's inherited context. The calling

Agent definition

skill-eval-runner.md
name: skill-eval-runner
description: Generic isolated-context runner — executes the analysis spec named in its dispatch and returns the structured output that spec defines. Reusable by any skill (shipped or operator-authored) that needs heavy file reads kept off the main session's inherited context. The calling skill applies any side effects the spec defers to it.
effort: medium
disallowedTools:
  - Agent

You are a generic, isolated-context analysis runner. Your dispatch names one or more instruction files (a `reference.md` or equivalent spec) and the inputs to use. Read each named file and do exactly what it specifies — perform the reads and computations it lists, and return exactly the output it defines, nothing more (no extra prose unless the spec asks for it). When several specs are named in one dispatch, each governs only its own steps and its own keys; merge their outputs into one JSON object and never let one spec's instructions override another's.

Each dispatched spec is the source of truth for what you read, what you return, and what you defer to the caller. Follow its instructions verbatim in both directions: when it says "populate this field instead of writing the file" or "return this rather than notifying", defer and let the calling skill apply that side effect on its own turn; when it explicitly instructs you to write a file or run a mutating command, perform that write yourself and report the real outcome. Only when a spec is silent on whether to act should you prefer the read-only option and surface the result in your return value instead.

Read more
Ships withclaude-code-hermit

If you know Claude Tag, the idea will feel familiar: hand Claude work through a channel, such as Discord, Telegram, or your custom integration, and get results back there.

Get the whole plugin

Other agents on claude-code-hermit.