Hermes Imports

This is the bridge between your messy local Hermes workflows and clean public ECC skills. It walks you through sanitizing operator prompts so you can ship them without leaking workspace paths, credentials, client names, or private data. The checklist is aggressive: it catches absolute paths, OAuth files, phone numbers, and anything that looks like real account details. The conversion pattern is simple: identify the loop, strip the private bits, turn local paths into repo-relative examples, and scan before you commit. Honestly, if you've ever copied a prompt from your terminal into a doc and then panicked about what might be in there, you need this.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill hermes-imports --agent claude-code

Installs into .claude/skills of the current project.

Files

Hermes Imports

Use this skill when turning a repeated Hermes workflow into something safe to ship in ECC.

Hermes is the operator shell. ECC is the reusable workflow layer. Imports should move stable patterns from Hermes into ECC without moving private state.

When To Use

A Hermes workflow has repeated enough times to become reusable.
A local operator prompt should become a public ECC skill.
A launch, content, research, or engineering workflow needs sanitized handoff docs.
A workflow mentions local paths, credentials, personal datasets, or private account names that must be removed before publication.

Import Rules

Convert local paths to repo-relative paths or placeholders.
Replace live account names with role labels such as operator, default profile, or workspace owner.
Describe credential requirements by provider name only.
Keep examples narrow and operational.
Do not ship raw workspace exports, tokens, OAuth files, health data, CRM data, or finance data.
If the workflow requires private state to make sense, keep it local.