Hermes Skills

Reusable skills for Hermes Agent, centered on workflows that benefit from durable profiles rather than one-off prompt tricks.

The first skill in this repository is profile-design-council: an asynchronous Kanban workflow for cross-profile fusion. Two different Hermes profiles investigate the same question independently. A dependent judge profile then reads both handoffs, extracts common ground, combines compatible strong ideas, compares tradeoffs, and rejects weaker options.

flowchart LR
  A[Investigator A profile] --> J[Judge profile]
  B[Investigator B profile] --> J
  J --> D[Decision handoff]

• profile-design-council: creates a three-card Hermes Kanban council for independent investigation and evidence-based adjudication. The user chooses investigator profile A, investigator profile B, and the judge profile for each council.

Why profiles instead of three model calls? A Hermes profile can carry a different SOUL/personality, durable memory, installed skills, enabled tools, model/provider configuration, and reasoning habits. It also runs with independent context. Those differences matter when you want diverse proposals instead of three variations of the same answer.

The workflow has three phases:

1. Independent investigation: two different profiles research and reason separately under read-only instructions.
2. Evidence-based fusion: the judge reviews the completed handoffs as anonymized proposals.
3. Pruning and decision: the judge keeps common ground, combines compatible strong ideas, weighs tradeoffs, and explains why rejected alternatives lose.

This is not majority vote, and it is not answer concatenation. Agreement is useful signal only when it is supported by evidence.

Install the current skill directly from this GitHub-source identifier:

hermes skills install gregory-chapman/hermes-skills/skills/profile-design-council

This installation fetches SKILL.md plus the runtime support files referenced from it. Tests stay in this source repository and CI; they are not installed in the skill bundle.

• investigate the best solution for migrating our billing exports
• research this topic with independent proposals before deciding
• architect this for me and adjudicate the tradeoffs
• compare build versus buy options for search indexing

Practical use cases include architecture decisions, vendor comparison, migration planning, incident remediation options, rollout strategy, library selection, and policy design.

Before creating a council, the skill asks which profiles to use:

• investigator profile A
• investigator profile B
• judge profile

The two investigator profiles must be different. The judge can be one of the investigators or a third profile.

When the host has ordinary durable preference memory, the invoking agent can remember the user's preferred trio as a workflow preference and suggest it next time. The user still confirms or changes the trio for each council. Agents without durable-memory support simply ask each time. The helper script itself never reads memory; it only accepts explicit CLI arguments.

• Current Hermes Agent with Kanban support.
• At least two named Hermes profiles suitable for independent investigation.
• A judge profile selection, which may reuse one investigator or name a third profile.
• Gateway Kanban dispatcher running.

The skill normally invokes the helper for you, but it can also be run directly:

python3 skills/profile-design-council/scripts/create_council.py \
  "Choose a durable queue design for export jobs" \
  --investigator-a atlas \
  --investigator-b beacon \
  --judge arbiter \
  --workspace "dir:$PWD" \
  --idempotency-key "queue-design"

Use --dry-run --json to inspect the exact three-card plan without mutating Kanban state.

Run the skill tests:

python3 -m unittest discover -s skills/profile-design-council/scripts -p 'test_*.py' -v

Run compile checks:

python3 -m compileall -q scripts skills

Run the repository validator:

python3 scripts/validate_repo.py

The council investigation prompts are read-only and instruct investigators not to mutate files, databases, cloud resources, accounts, or external systems. As with any community skill, review SKILL.md and scripts before installation.

See the Hermes Skills System documentation.