docs: replace invalid 'hermes config get <key>' with 'hermes config s…

[Aman113114-IITD]

…how'

'hermes config get ' is referenced in three guides but is not a valid subcommand. The valid subcommands under 'hermes config' are {show,edit,set,path,env-path,check,migrate}. 'hermes config show' is already used elsewhere in the docs (including 'hermes config show | grep ' in the FAQ), so it's the idiomatic replacement.

• work-with-skills.md: 'View all skill config' now uses 'hermes config show | grep ^skills.config'
• migrate-from-openclaw.md: session-policy check now reads the value from 'hermes config show'
• configuring-models.md: 'inspect what the CLI will actually use' now uses 'hermes config show | grep ^model.'

Refs #30195

What does this PR do?

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform:

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

[alt-glitch]

Duplicate of #30293 which fixes the same hermes config get references in the same 3 doc files. Also competes with #30349. All three fix #30195.

[teknium1]

This is an automated hermes-sweeper review. The docs fix from this PR is already present on current main.

Evidence:

• website/docs/guides/work-with-skills.md:165 now uses hermes config show | grep '^skills\.config'.
• website/docs/guides/migrate-from-openclaw.md:232 now points users to hermes config show for checking session_reset.
• website/docs/user-guide/configuring-models.md:227 now uses hermes config show | grep '^model\.' for inspecting model config.
• Current main contains Aman-authored commit 3f0d44af8ae380996057b620afeae258af830634 with the same hermes config get → hermes config show change.
• This also matches the prior maintainer discussion noting the duplicate/competing PRs for docs: hermes config get <key> referenced in 3 guides is not a valid command #30195, with the fix later merged through the docs correctness sweep.

Thanks for catching and fixing the invalid command in the docs.