Hermes GIS Skills: GIS workflows for Hermes Agent

Understand the public package structure, catalog, validator, release maturity, and safe update path.

The public package lives at github.com/daraobeirnecode/hermes-gis-skills. It is a portable, sanitized export of reusable GIS skills—not a copy of a live Hermes profile.

Repository structure

hermes-gis-skills/
├── README.md
├── INSTALL.md
├── SECURITY.md
├── CONTRIBUTING.md
├── CHANGELOG.md
├── LICENSE
├── catalog.json
├── scripts/
│   └── validate.py
└── <21 skill directories>/
    ├── SKILL.md
    └── references/

The initial package contains 21 skills, 116 supporting references, and 146 tracked files.

catalog.json records each skill's directory, name, description, version, author, license status, and reference count. Use it for inventory and documentation generation; use each SKILL.md as the procedural source.

Package validator

Run:

python3 scripts/validate.py

The dependency-free validator checks package structure, frontmatter, referenced files, portability, and common secret patterns. A passing validator means the package is structurally consistent; it does not certify every workflow against your data, GIS versions, credentials, or production controls.

Version and maturity

The package is v0.1.0 and pre-1.0. Treat workflows as a transparent starting point that still requires project-specific source, schema, dependency, security, and output validation.

Safe updates

git -C "$HOME/.hermes/skills/gis" status --short --branch
git -C "$HOME/.hermes/skills/gis" pull --ff-only
python3 "$HOME/.hermes/skills/gis/scripts/validate.py"

If local changes exist, preserve them in a branch or fork. Do not reset or overwrite a customized skill directory just to take an upstream update.

Rollback

Record the installed commit before updating:

git -C "$HOME/.hermes/skills/gis" rev-parse HEAD

To test an earlier release, use a separate clone or reviewed branch. Avoid forceful checkout/reset commands in a live customized directory unless you have verified the path and preserved local work.

Contribution boundary

Before contributing changes:

remove credentials, private URLs, client data, and user-specific paths;
generalize organization-specific assumptions;
verify every referenced file and command;
run the validator and review the Git diff;
submit the update through a pull request.

Repository and versioning