agentleFS
Sign inStart free
AtlasOmniaAtlasOmnia/hermes-custom-pack/skills/hermes-plugin-evaluation/SKILL.md

hermes-plugin-evaluation

Skill75 starsChanged 4 months agoMITView on GitHub

hermes-plugin-evaluation — Evaluate third-party Hermes Agent plugins before installation: cost, licensing, required services, data flow, dependencies, and setup risk.

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when the user asks about installing, trusting, pricing, or using a third-party Hermes Agent plugin or integration.

    line 24
  2. Distinctive:

    Load authoritative Hermes context first: when the task involves Hermes plugins:

    line 36
  3. Distinctive:

    Prefer official Hermes docs for CLI syntax and plugin lifecycle.

    line 38
  4. Distinctive:

    Do not infer the hosted service is free just because the plugin is public.

    line 48
  5. Very specific:

    If pricing is missing/404/gated, say “pricing not publicly obvious.

    line 51
  6. Distinctive:

    Test in a non-critical Hermes profile or disabled gateway first.

    line 57
  7. Distinctive:

    Avoid putting it on the main gateway until pricing, credentials, and data flow are understood.

    line 58
  8. Very specific:

    Run plugin-specific doctor/diagnostics before enabling public channels.

    line 59
  9. Distinctive:

    Keep it concise and decisive:

    line 63
  10. Distinctive:

    Recommended next step: if installation/security matters.

    line 68
  11. Distinctive:

    Avoid broad explanations of Hermes unless he asks.

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hermes Plugin Evaluation

Use this when the user asks about installing, trusting, pricing, or using a third-party Hermes Agent plugin or integration.

Goal

Give a practical go/no-go read before touching the live Hermes gateway. Separate:

  • Plugin code cost/license — whether the repository itself is public/open-source/free to install.
  • Service cost — required SaaS account, usage billing, phone/SMS/voice costs, model API costs, tunnels, hosted routing, or paid feature gates.
  • Operational risk — what data leaves Hermes, whether the plugin opens public webhooks/tunnels, and whether it modifies gateway behavior.

Fast evaluation workflow

  1. Load authoritative Hermes context first when the task involves Hermes plugins:
  • Load hermes-agent if available.
  • Prefer official Hermes docs for CLI syntax and plugin lifecycle.
  1. Inspect the repository without installing it:
  • README / docs
  • plugin.yaml
  • pyproject.toml, package.json, lockfiles
  • LICENSE, NOTICE, or equivalent
  • setup wizard files and after-install notes
  • tool definitions, platform adapter files, webhook/tunnel code
  1. Answer cost precisely:
  • Say “plugin appears free/public” only for the repo/installable code.
  • Do not infer the hosted service is free just because the plugin is public.
  • Identify paid dependencies: phone numbers, SMS/MMS, voice minutes, hosted tunnels, OpenAI/Anthropic/etc. APIs, storage, or managed accounts.
  1. Check for a public pricing page, but treat absence as unknown, not free:
  • If pricing is missing/404/gated, say “pricing not publicly obvious; confirm with vendor.”
  1. Report required credentials and data paths:
  • Required env vars/API keys.
  • Optional credentials that change cost or data flow.
  • Whether inbound messages/calls pass through vendor infrastructure.
  1. Recommend a safe rollout:
  • Test in a non-critical Hermes profile or disabled gateway first.
  • Avoid putting it on the main gateway until pricing, credentials, and data flow are understood.
  • Run plugin-specific doctor/diagnostics before enabling public channels.

Response shape the user prefers

Keep it concise and decisive:

  • Short answer first: free, paid, mixed, or unclear.
  • What I verified as bullets.
  • Cost implication as bullets.
  • Recommended next step if installation/security matters.

Avoid broad explanations of Hermes unless he asks. He usually wants the practical answer.

Pitfalls

  • Public repo ≠ free service. Many plugins are just glue to a paid platform.
  • No LICENSE file means unclear license, even if GitHub visibility is public.
  • Phone/SMS/voice are rarely free at scale. Assume carrier/service costs unless docs explicitly say otherwise.
  • Hosted tunnels/webhooks imply external data flow. Flag this before installation.
  • Do not install first just to answer pricing/trust questions. Inspect first, then ask/confirm before side effects.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free