菜单
Wire Hermes into workspace-hub ecosystem — multi-repo skills, config sync, session export to learning pipeline, memory cross-pollination, skill patch tracking, and cross-machine health checks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill hermes-ecosystem-integration命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
正在显示 SKILL.md
| name | hermes-ecosystem-integration |
| version | 3.0.0 |
| category | devops |
| description | Wire Hermes into workspace-hub ecosystem — multi-repo skills, config sync, session export to learning pipeline, memory cross-pollination, skill patch tracking, and cross-machine health checks. |
| tags | ["hermes","harness","skills","sync","multi-machine","learning-pipeline"] |
hermes update (git pull)workspace-hub/
config/agents/hermes/
config.yaml.template # Shared config, __WS_HUB_PATH__ placeholder
SOUL.md # System prompt personality
patches/
exclude-archive-skill-dirs.patch # Survives hermes update
scripts/
_core/sync-agent-configs.sh # Smart YAML merge + path substitution
cron/harness-update.sh # Nightly: update → patch → sync → health
cron/hermes-session-export.sh # Sessions → logs/orchestrator/hermes/*.jsonl
cron/sync-agent-memories.sh # Hermes MEMORY.md → .claude/state/hermes-insights.yaml
cron/comprehensive-learning-nightly.sh # Steps 2b, 2c, 3f for Hermes
hooks/track-skill-patches.sh # Post-commit: log .claude/skills/ changes
readiness/harness-config.yaml # Workstation paths + health check defs
logs/orchestrator/hermes/ # gitignored — session JSONL + skill-patches.jsonl
Topology-sensitive: if tier-1 repos are siblings under the same parent as workspace-hub, do not render repo skill paths as workspace-hub/<repo>/.claude/skills. See references/sibling-repo-sso-topology.md for the required verification checklist covering Hermes external_dirs, Codex/Gemini symlinks, AGENTS pointers, and memory drift. Before closeout, use references/sibling-sso-validation-closeout.md for the validation bundle, post-fix adversarial review focus, and interruption/resume handoff shape. During implementation/code-review hardening, use references/sibling-sso-implementation-review.md for the stale-vs-valid provider finding split, portable script guards, and final closeout checklist additions. If adversarial review still returns MAJOR after green targeted tests, use references/sibling-sso-review-remediation.md for the full-registry PASS gate, prose-style AGENTS.md contract rewrite edge case, PyYAML fallback guard, and closeout checklist. If live --apply aborts because repairable skill-symlink actions are grouped with unresolved AGENTS.md blockers, use references/sibling-sso-partial-apply-blockers.md to split safe repairs from residual blockers without falsely closing the issue. After a core SSoT issue closes with residual sibling contract failures, use references/sibling-sso-post-landing-followup.md to verify live state, identify the existing follow-up issue, and avoid implementing from a dirty/diverged control-plane checkout.
INBOUND (Hermes consumes):
6 repos .claude/skills/ ──→ external_dirs ──→ 973+ active skills in system prompt
workspace-hub (387), CAD-DEVELOPMENTS (182), digitalmodel (31),
worldenergydata (20), achantas-data (13), assetutilities (3)
~/.hermes/skills/ is EMPTY — all skills served from repo via external_dirs
(9 MB of local duplicates cleaned in #1944)
mlops nested: some skills under mlops/cloud/, mlops/training/, mlops/inference/ etc.
OUTBOUND (Hermes feeds back):
~/.hermes/sessions/*.json ──→ hermes-session-export.sh ──→ logs/orchestrator/hermes/*.jsonl
~/.hermes/memories/*.md ──→ sync-agent-memories.sh ──→ .claude/state/hermes-insights.yaml
NEW skills/scripts/rules ──→ write DIRECTLY to .claude/skills/ (not ~/.hermes/)
.claude/skills/ changes ──→ track-skill-patches.sh ──→ skill-patches.jsonl
Local→repo drift ──→ backfill-skills-to-repo.sh (auto via harness-update)
All above ──→ comprehensive-learning Phase 1 signal sources
Location: ~/.hermes/config.yaml
skills:
external_dirs:
# workspace-hub root
- /mnt/local-analysis/workspace-hub/.claude/skills
# sibling repo topology: repos are peers of workspace-hub, not children
- /mnt/local-analysis/CAD-DEVELOPMENTS/.claude/skills
- /mnt/local-analysis/worldenergydata/.claude/skills
- /mnt/local-analysis/achantas-data/.claude/skills
- /mnt/local-analysis/assetutilities/.claude/skills
- /mnt/local-analysis/digitalmodel/.claude/skills
~/.hermes/skills/ takes precedence on name collisions.claude/skills path to both template and live configworkspace-hub, not from workspace-hub/<repo>Finding new repos with skills:
find /mnt/local-analysis/workspace-hub -maxdepth 3 -path '*/.claude/skills' -type d \
-exec sh -c 'echo "$(find "$1" -name SKILL.md -not -path "*/_archive/*" | wc -l) $1"' _ {} \; | sort -rn
Location: ~/.hermes/hermes-agent/agent/skill_utils.py
Hermes only excludes .git, .github, .hub by default. Workspace-hub has
2,700+ skills with 2,100+ in _archive/. Without this patch, all get indexed.
EXCLUDED_SKILL_DIRS = frozenset((
".git", ".github", ".hub",
"_archive", "_internal", "_runtime", "_core",
"session-logs",
))
Patch saved to: config/agents/hermes/patches/exclude-archive-skill-dirs.patch
Auto-applied by harness-update.sh after every hermes update.
Template: config/agents/hermes/config.yaml.template
Uses machine-aware placeholders resolved by sync-agent-configs.sh:
__WS_HUB_PATH__ = canonical workspace-hub checkout for the selected machine__REGISTRY_REPO_SKILL_DIRS__ = sibling repo .claude/skills roots derived from config/workstations/registry.yaml for the selected machine, filtered to real paths containing SKILL.mdconfig/workstations/registry.yaml and cross-checks scripts/readiness/harness-config.yaml--machine <name> support for dry-runs and target renderingworkspace-hub/<repo>/.claude/skills paths at render timesync-agent-configs.sh → sync_hermes_yaml_config():
deep_merge(existing, template) — template keys win for scalars, recurse for dictsharness-update.sh → health_check_hermes() validates:
hermes --version)from hermes_cli.main import main)_archive in skill_utils.py)# Make change in ~/.hermes/hermes-agent/
cd ~/.hermes/hermes-agent
# ... edit files ...
git diff > /mnt/local-analysis/workspace-hub/config/agents/hermes/patches/my-fix.patch
# Commit patch to workspace-hub
cd /mnt/local-analysis/workspace-hub
git add config/agents/hermes/patches/my-fix.patch
git commit -m "feat(harness): add my-fix patch for Hermes"
# On the target machine (after git pull on workspace-hub):
bash scripts/_core/sync-agent-configs.sh
# Or wait for nightly cron (dev-primary 01:15, dev-secondary 01:45)
# Run health check standalone:
source <(grep -A65 '^health_check_hermes' scripts/cron/harness-update.sh)
log() { echo "[$(date '+%H:%M:%S')] $*"; }
health_check_hermes && echo "PASS" || echo "FAIL"
# Check patch status:
grep '_archive' ~/.hermes/hermes-agent/agent/skill_utils.py
# Check external_dirs:
python3 -c "
import yaml
with open('$HOME/.hermes/config.yaml') as f:
cfg = yaml.safe_load(f)
print(cfg.get('skills', {}).get('external_dirs', []))
"
Converts ~/.hermes/sessions/*.json → logs/orchestrator/hermes/session_YYYYMMDD.jsonl.
.last-export-ts — incremental by default--all flag to re-export everything, --dry-run to previewReads Hermes MEMORY.md + USER.md (§-separated entries), writes:
.claude/state/hermes-insights.yaml — categorized Hermes knowledge.claude/state/cross-agent-memory.yaml — merged cross-agent factsOne-way: Hermes → Claude (never modifies Hermes files).
Post-commit hook logs .claude/skills/ modifications to
logs/orchestrator/hermes/skill-patches.jsonl with agent attribution.
Install: already appended to .git/hooks/post-commit in workspace-hub.
In harness-update.sh (runs nightly):
update_hermes: backfill_hermes_skills() calls
scripts/hermes/backfill-skills-to-repo.sh --commit
Detects and auto-commits any new skills in ~/.hermes/skills/In comprehensive-learning-nightly.sh:
hermes-session-export.sh (best-effort)codex-session-export.sh (best-effort — #194)sync-agent-memories.sh (best-effort)detect-drift.sh --provider hermescommit-learning-artifacts.sh — snapshots memories, redacts
session-signals, stages all state dirs, legal scan gate, commit + pushcomprehensive-learning/references/pipeline-detail.md updated:
hermes provider row addedTwo monitoring additions:
Daily memory quality scan (05:50 UTC):
Added to config/scheduled-tasks/schedule-tasks.yaml:
- id: memory-health-check
command: uv run --no-project python scripts/memory/eval-memory-quality.py --memory-root .claude/memory/ --format md --check-paths
log: logs/quality/memory-health-*.md
Checks: signal_density, pct_stale_paths, headroom, dedup_candidates. Complements agent-memory-backup (05:00) with quality verification.
48h staleness alert in check-memory-drift.sh:
If .claude/memory/agents.md hasn't been modified in 48+ hours,
the script prints a RED warning and attempts notification via scripts/notify.sh.
Hermes only reads SKILL.md files. But the real knowledge lives in Claude Code
native formats across 22 repos:
Template layer (GSD/gstack, identical across 18 repos):
74 agents/ dirs + 150 commands/ = ~4,000 files (shared infrastructure)
Unique content (high value):
digitalmodel: 103 unique agents (orcaflex/13, gmsh/24, freecad/17, aqwa/7, orcawave/5, cad/5)
CAD-DEVELOPMENTS: 161 commands, 6 knowledge files
workspace-hub: 19 agents, 135 commands, 21 knowledge files
Agent .md files have similar structure to SKILL.md (YAML frontmatter + markdown body).
Convert with scripts/skills/convert-agent-to-skill.py (see #1721):
uv run python scripts/skills/convert-agent-to-skill.py \
--input digitalmodel/.claude/agents/orcaflex \
--output digitalmodel/.claude/skills/engineering/orcaflex-agents
Key conversion differences:
version: 1.0.0, category:, type: reference to frontmatterSKILL.mdPitfalls found during #1721 conversion:
derive_skill_name() can produce names with spaces
(e.g. "Marine Engineering Excel Analyzer") from metadata name: fields,
creating dirs with spaces. Post-hoc: mv "Bad Name" good-name + fix name: in SKILL.md.git commit --no-verify for these reference-doc skills.# Find agent dirs with no corresponding SKILL.md
for d in $(find digitalmodel/.claude/agents -maxdepth 1 -type d | tail -n+2); do
name=$(basename "$d")
skill=$(find digitalmodel/.claude/skills -path "*/$name*/SKILL.md" 2>/dev/null | head -1)
[ -z "$skill" ] && echo "NO SKILL: $name ($(find "$d" -type f | wc -l) agent files)"
done
18 repos have identical 74 agents (GSD template). Check with:
diff <(ls repo-a/.claude/agents/ | sort) <(ls repo-b/.claude/agents/ | sort)
If identical → template. Only convert unique agents per repo.
Hermes can run multiple sessions simultaneously on different providers, burning
separate quotas in parallel. Use -m and --provider flags:
# Terminal A — Anthropic (Claude Max $200 quota)
hermes chat -m claude-sonnet-4-20250514 --provider anthropic -q "$(cat prompt-a.md)"
# Terminal B — OpenAI via Codex auth (ChatGPT Plus $20 quota)
hermes chat -m gpt-5.4 --provider openai-codex -q "$(cat prompt-b.md)"
Model name gotcha (openai-codex): The ChatGPT Codex backend only accepts
gpt-5.4 (the exact model name from ~/.codex/config.toml). Other names like
gpt-4.1, o4-mini, gpt-4o, codex-mini all return HTTP 400. The base_url
is https://chatgpt.com/backend-api/codex — not the standard OpenAI API.
Exhausted credentials: If a provider shows last_status: exhausted, reset it:
hermes auth reset anthropic # or: hermes auth reset openai-codex
Check status: hermes status or parse ~/.hermes/auth.json credential_pool.
Available providers (check with hermes chat --help):
anthropic, openai-codex, openrouter, nous, copilot, huggingface, etc.
For overnight batches: Assign analysis tasks to sonnet (cheaper, Anthropic quota) and implementation tasks to gpt-5.4 (OpenAI quota) — different rate limit pools.
Repo .claude/skills/ is the single source of truth. ~/.hermes/skills/ is empty (9 MB cleaned, 0 SKILL.md files local). external_dirs wiring means both Hermes AND Claude Code see everything written there. No dual-write, no sync drift.
Verified skill counts (active, no _archive): workspace-hub: 696 | CAD-DEVELOPMENTS: 218 | digitalmodel: 31 worldenergydata: 21 | achantas-data: 13 | assetutilities: 3 Total unique: ~1156 across 6 repos
All 4 agents access same skill library:
Per-repo .codex/.gemini skill access:
.codex/skills -> ../.claude/skills when using workspace-hub as its own canonical roottest -e and readlink -f; the older nested-repo pattern .codex/skills -> ../../.claude/skills is usually broken after moving repos to /mnt/local-analysis/<repo> because it resolves toward /mnt/local-analysis/.claude/skills.claude/skills if it is autonomous, or link to the intended central workspace-hub skill root if workspace-hub is the single source of truthWhen creating a new skill, write SKILL.md to
workspace-hub/.claude/skills/<category>/<name>/SKILL.md.
Then: git add .claude/skills/ && git commit -m "hermes: new skill — <name>".
Reusable scripts → scripts/ in repo. If part of a skill → skill's scripts/ subdir.
.claude/rules/<name>.md (CC frontmatter with trigger/glob).claude/hooks/<name>.sh (POSIX shell, auto-fires on CC sessions)All .claude/ writes get git add + commit + push with clear provenance.
scripts/hermes/backfill-skills-to-repo.sh — wired into harness-update.sh
(runs after update_hermes, via backfill_hermes_skills() function).
Detects any skills in ~/.hermes/skills/ that aren't in any repo and copies
them over with per-repo routing (see below).
Usage: backfill-skills-to-repo.sh [--dry-run] [--commit]
Per-Repo Routing (#1948): The backfill script routes skills to the correct repo automatically:
Testing pattern: Create dummy skill in ~/.hermes/skills/ → run --dry-run to verify routing → run --commit for full pipeline → clean up dummy, revert commit.
Skill count verification:
# Total active across all repos:
find /mnt/local-analysis/workspace-hub/{.claude,CAD-DEVELOPMENTS/.claude,\
worldenergydata/.claude,achantas-data/.claude,assetutilities/.claude,\
digitalmodel/.claude}/skills \
-name SKILL.md -not -path "*/_archive/*" | wc -l
hermes update overwrites patches — always save patches to
config/agents/hermes/patches/ so harness-update.sh re-applies them__WS_HUB_PATH__
placeholder; never copy it directly without resolvinghostname.lower() in name.lower()
which is fuzzy; if hostname doesn't match any workstation, falls back to $WS_HUBnightly-readiness.sh --update-baseline after initial setup~/.hermes/skills/ (local). Use patch() on the raw filesystem path
to fix external skills. The skill is immediately visible via skill_view after.!logs/orchestrator/hermes/ and
!logs/orchestrator/codex/ exceptions added to .gitignore. Committed nightly by
commit-learning-artifacts.sh. Session-signals need redaction first (see
agent-learnings-portability skill)..claude/ dirs each have their own agent contract (AGENTS.md often points back
to workspace-hub's canonical contract).git commit --no-verify for skill docs that contain code examples. Do NOT disable
the scanner globally — it's useful for actual skill code.claude plugin update superpowers --scope project can fail with
Plugin "superpowers" not found even when the plugin is installed and enabled.
First inspect claude plugin list --json, then use the returned id field, e.g.
superpowers@claude-plugins-official, with the detected scope:
claude plugin update superpowers@claude-plugins-official --scope project.
For automation, treat claude plugin list --json as the source of truth for
plugin id + scope + enabled state, and summarize installed scopes in dry-run output./mnt/local-analysis/<repo>, audit all of: Hermes external_dirs, config/agents/hermes/config.yaml.template, .codex/skills and .gemini/skills symlink targets, AGENTS.md inheritance pointers, and memory bridge drift. Do not confirm single-source-of-truth flow from the existence of sibling repos alone; verify every path resolves. See references/sibling-repo-sso-topology.md..claude/memory/** diffs separately from config/script/test changes. Treat memory files that rewrite canonical source paths to an agent-worktree path, revert privacy/scope language, or otherwise look like bridge-generated drift as suspect. Do not stage them with SSoT fixes unless the approved issue explicitly requires memory content changes and scripts/memory/check-memory-drift.sh passes afterward. See references/sibling-sso-memory-drift-staging.md.skills.external_dirs coverage, (b) Codex/Gemini symlink resolution per sibling repo, (c) memory bridge drift state, (d) AGENTS inheritance pointers, and (e) whether tools/scripts/commands are actually centralized or repo-local. It is valid for workspace-hub to be the harness/control-plane while tools remain repo-local and skills are only partially wired.config/agents/hermes/config.yaml.template. If it contains stale __WS_HUB_PATH__/<repo>/.claude/skills entries, report the SSoT state as incomplete even when some live ~/.hermes/config.yaml external dirs resolve./mnt/local-analysis/<repo>/.claude/skills entries in config.yaml.template. Use a registry-rendered placeholder such as __REGISTRY_REPO_SKILL_DIRS__ and assert rendered external_dirs equals the real, registry-listed repos with skills.--machine dev-secondary must not reuse the local checkout’s memory/check scripts and then report a false pass. For non-local hosts, run memory/readiness probes through SSH or mark the section not_present/fail with evidence.../AGENTS.md pointers, block symlinked, missing, or non-regular AGENTS.md files. Treat symlinked AGENTS.md as a safety blocker; otherwise apply can overwrite an unintended target.pytest pass can miss SSoT invariant failures. Re-review specifically for registry authority, target-machine truthfulness, symlink overwrite safety, repair-manifest completeness, rollback scope, and stale nested paths before commit/push/closeout.references/sibling-sso-implementation-review.md.uv run --with pyyaml --no-project python, and Python helpers that call platform utilities such as findmnt must guard missing binaries/errors and return structured fallback state instead of crashing. See references/sibling-sso-implementation-review.md.machine.repos, live acceptance is the full registry, not starter fixtures. After a MAJOR review, prove check-sibling-sso-flow.py --machine <machine> --json passes for the named machine or explicitly keep closeout blocked. Include the exact newly modified tests in the rerun bundle.AGENTS.md files can express inheritance as This repository inherits the canonical contract from: followed by a bare ../AGENTS.md line. Treat that two-line pattern as a safe contract pointer rewrite, but keep unrelated prose mentions blocked/unchanged. Use the TDD pattern in references/sibling-sso-review-remediation.md.AGENTS.md, do not let a coarse per-repo blocker prevent all safe repairs unless the approved plan explicitly requires all-or-nothing behavior. Model repairable_actions and blocked_actions separately, apply allowlisted reversible repairs, then keep checker/closeout red until residual blockers are resolved or refiled. See references/sibling-sso-partial-apply-blockers.md.references/sibling-sso-post-landing-followup.md.