hermes-config-audit-gotchas
Audit Hermes custom config keys and migrated skill settings safely, with verified command behavior and stale-path checks.
Best use case
hermes-config-audit-gotchas is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit Hermes custom config keys and migrated skill settings safely, with verified command behavior and stale-path checks.
Teams using hermes-config-audit-gotchas should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hermes-config-audit-gotchas/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hermes-config-audit-gotchas Compares
| Feature / Agent | hermes-config-audit-gotchas | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit Hermes custom config keys and migrated skill settings safely, with verified command behavior and stale-path checks.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Hermes Config Audit Gotchas Use when reviewing Hermes configuration after `hermes config migrate`, `hermes setup`, or when a prompt mentions new skill settings such as `wiki.path`. ## What this skill is for Hermes can prompt for skill-defined config keys during migration, but the displayed logical key (for example `wiki.path`) is not always the exact stored path in config, and migrated defaults may point at directories that do not exist. ## Verified workflow 1. Load relevant config/documentation skills if available (`hermes-agent`, any skill declaring the config key). 2. Check live config with: - `hermes config show` - `hermes config check` - `hermes config path` - `hermes config env-path` 3. Do not assume `hermes config list` or `hermes config get` exist. - In the audited build, both are invalid subcommands. 4. Confirm the storage shape if needed by inspecting the config file with normal file tools. 5. Verify the configured filesystem path actually exists before recommending it. 6. If the prompted key is a skill key, remember Hermes stores it under `skills.config.*` even if the prompt shows only the logical key. ## Key findings - `wiki.path` from `llm-wiki` is stored as `skills.config.wiki.path`. - `hermes config show` is the authoritative read command in the audited build. - `hermes config list` and `hermes config get` are not supported in the audited build. - A migrated default like `~/wiki` can be stale. Verify the real wiki root before accepting it. - On the audited machine, `/home/vamsee/wiki` was missing while `/mnt/local-analysis/workspace-hub/knowledge/wikis` existed and was the better candidate for the workspace-hub multi-wiki layout. ## Recommended review pattern For each prompted config item: 1. Identify which skill declared it. 2. Confirm how Hermes stores it in config. 3. Check whether the current configured value exists and is meaningful. 4. Propose the corrected `hermes config set ...` command using the stored key path, not just the displayed logical key. ## Example Prompted item: - `wiki.path — Path to the LLM Wiki knowledge base directory` Recommended command form: ```bash hermes config set skills.config.wiki.path /mnt/local-analysis/workspace-hub/knowledge/wikis ``` ## Pitfalls - Do not trust migrated defaults without a filesystem existence check. - Do not rely on unsupported subcommands like `list` or `get`. - Do not confuse the displayed logical key with the stored YAML key path.
Related Skills
llm-wiki-audit-feedback-loop
Durable feedback loop for correcting llm-wiki pages without losing the correction to chat history. Use when (1) a human notices a wiki page is wrong, outdated, or contradicts a source, (2) processing the `audit/` inbox of a domain wiki, (3) reviewing what feedback has been resolved vs deferred, (4) needing to leave a comment on a specific text range that survives line- number drift. Implements the anchored-text audit file pattern from lewislulu/llm-wiki-skill, adapted for workspace-hub's domain-wiki layout under /mnt/local-analysis/llm-wiki/wikis/<domain>/. Extends the 5-op model (compile/ingest/query/lint) from research/llm-wiki with the missing `audit` op. Never silently delete feedback — rejected audits stay archived with rejection rationale.
telegram-hermes-bot
Install a private, single-user Telegram bot connected to a Hermes gateway on a Linux host. Covers BotFather provisioning, token hygiene, systemd drop-in override for durable env loading, single-user allowlist enforcement, approval-mode posture, and the mobile destructive-action smoke test. Reusable for any `@<name>Bot` / host pair.
hermes-memory-bridge
Architecture and scripts for syncing Hermes memory into git-tracked .claude/memory/ so all machines get context via git pull. Covers quality gate, drift detection, topic mirroring, and cron automation.
hermes-kanban-readability
Reapply the Hermes Kanban dashboard readability customizations (clickable bare URLs in card descriptions + readable card-text font, a visible horizontal scrollbar so all columns are reachable) as a user-override plugin that survives hermes-agent updates. Use when the Kanban board reverts to the Mondwest display font / plain-text Source URLs after a hermes update, or when bootstrapping a machine whose ~/.hermes was wiped.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
provider-session-ecosystem-audit-and-exporters
Build and maintain cross-provider session-log audits for Codex, Codex, Hermes, and Gemini, including exporter design, normalization, and behavioral verification.
orcawave-orcaflex-readiness-audit
Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.
toml-section-scoping-config-debug
Diagnose TOML config errors caused by misplaced keys in table sections
read-only-pre-implementation-audit
Systematic cross-check workflow to validate assumptions before TDD coding begins
portable-config-baseline-pattern
Extract machine-agnostic settings into portable template files while keeping machine-specific hooks and plugins separate
portable-baseline-configuration-pattern
Separate portable/universal config from machine-specific settings to enable safe template reuse across environments