hermes-imports
Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts. Use when preparing a Hermes workflow for public ECC reuse without leaking private workspace state, credentials, or local-only paths.
By affaan-m · 2,797 installs
npx skills add affaan-m/ecc --skill hermes-imports
Source repository · Upstream listing
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.
Sanitization Checklist
Before committing an imported workflow, scan for:
absolute paths such as /Users/...
~/.hermes paths unless the doc is explicitly explaining local setup
API keys, tokens, cookies, OAuth files, or bearer strings
phone numbers, private email addresses, and personal contact graphs
client names, family names, or account names that are not already public
revenue, health, or CRM details
raw logs that include tool output from private systems
Conversion Pattern
1. Identify the repeatable operator loop.
2. Strip private inputs and outputs.
3. Rewrite local paths as repo relative examples.
4. Turn one off instructions into a When To Use section and a short process.
5. Add concrete output requirements.
6. Run a secret and local path scan before opening a PR.
Example: Launch Handoff
Local Hermes prompt:
ECC safe version:
Example: Quiet Hours Operator Job
Local Hermes job:
ECC safe version:
Output Contract
Return:
candidate ECC skill name
sanitized workflow summary
required public inputs
private inputs removed
remaining risks
files that should be created or updated