agentleFS
jyjejyje/hermes-agent-helm/.claude/skills/hermes-agent-env-rule/SKILL.md

hermes-agent-env-rule

Skill18 starsChanged 31 days agoMITView on GitHub

Keep the chart's "Environment variables" README section (charts/hermes-agent/README.md.gotmpl) in sync with upstream Hermes Agent's supported env vars at the currently pinned appVersion. Use after an image version bump (cron-fetch-image PR), periodically, or when asked to check/update/audit Hermes env vars.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    If the tag doesn't exist upstream (chart's appVersion fell out of sync), fall back to the nearest tag at or before it from gh api …

    line 37
  2. Very specific:

    Don't run this as part of every cron-fetch-image bump automatically.

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Agent env var rule

charts/hermes-agent/README.md.gotmpl has an Environment variables section that links to upstream's official reference and lists a curated "commonly-used" subset, current as of the pinned image ({{ template "chart.appVersion" . }}, i.e. charts/hermes-agent/Chart.yaml → appVersion). Upstream adds/renames/removes env vars between releases; this skill re-checks the curated subset against the exact pinned version and refreshes it.

Source of truth: NousResearch/hermes-agent - Environment Variables (rendered docs site; the underlying source is website/docs/reference/environment-variables.md in the upstream repo).

Steps

  1. Find the pinned version:

    grep '^appVersion:' charts/hermes-agent/Chart.yaml
  2. Fetch the upstream doc at that exact tag (not main: the pinned image may lag behind upstream's latest commits):

    APPVERSION=$(yq '.appVersion' charts/hermes-agent/Chart.yaml)
    gh api "repos/NousResearch/hermes-agent/contents/website/docs/reference/environment-variables.md?ref=${APPVERSION}" \
      --jq '.content' | base64 -d > /tmp/hermes-env-vars-upstream.md

    If the tag doesn't exist upstream (chart's appVersion fell out of sync), fall back to the nearest tag at or before it from gh api repos/NousResearch/hermes-agent/tags --jq '.[].name'. Upstream tags are semver (v0.22.2) since October 2026 and date-based (v2026.9.24) before that, so sort -V ranks the old date tags above every semver tag: pick "nearest" by release date (gh api repos/NousResearch/hermes-agent/releases), not by version sort.

  3. Diff against the curated table in the chart's "Environment variables" section (charts/hermes-agent/README.md.gotmpl) - look specifically for:
    • new provider env vars (new LLM providers added upstream)
    • new messenger/platform integrations
    • renamed or removed vars that are still listed in our curated table
    • changed defaults for the runtime knobs we list (HERMES_MAX_ITERATIONS, HERMES_AGENT_TIMEOUT, SESSION_IDLE_MINUTES, etc.)
  4. Update the curated table in README.md.gotmpl: keep it short (10-15 rows max; it's a teaser, not a copy of the full reference). Prioritize: providers not already covered in that file's "Install options: LLM provider" section, messenger platforms not already covered in its "Messenger integrations" section, and any runtime knob likely to matter for a Kubernetes deployment (timeouts, session/idle behavior, dashboard auth). Don't touch the link to the official reference or the {{ template "chart.appVersion" . }} line - both stay accurate automatically.
  5. Regenerate the README:

    helm-docs --chart-search-root=charts --template-files=README.md.gotmpl
  6. Review the diff (git diff charts/hermes-agent/README.md.gotmpl charts/hermes-agent/README.md) and hand off to the git-commit-helper skill for the commit - this is a 📄 docs(chart) change, not style.

Notes

  • This is about the curated subset only. The full reference link in the README is permanent and never goes stale on its own.
  • Don't run this as part of every cron-fetch-image bump automatically; most version bumps don't add/remove env vars. Run it when asked, or periodically (e.g. once a month, or when a bump's upstream changelog mentions new providers/integrations).

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.