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
- Identify the repeatable operator loop.
- Strip private inputs and outputs.
- Rewrite local paths as repo-relative examples.
- Turn one-off instructions into a
When To Use section and a short process.
- Add concrete output requirements.
- Run a secret and local-path scan before opening a PR.
Example: Launch Handoff
Local Hermes prompt:
Read my local workspace files and finalize launch copy.
ECC-safe version:
Use the public release pack under docs/releases/<version>/.
Return one X thread, one LinkedIn post, one recording checklist, and the missing assets list.
Example: Quiet-Hours Operator Job
Local Hermes job:
Run my private inbox, finance, and content checks overnight.
ECC-safe version:
Describe the scheduler policy, the quiet-hours window, the escalation rules, and the categories of checks. Do not include private data sources or credentials.
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
1---2name: hermes-imports3description: 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.4---56# Hermes Imports78Use this skill when turning a repeated Hermes workflow into something safe to ship in ECC.910Hermes is the operator shell. ECC is the reusable workflow layer. Imports should move stable patterns from Hermes into ECC without moving private state.1112## When To Use1314- A Hermes workflow has repeated enough times to become reusable.15- A local operator prompt should become a public ECC skill.16- A launch, content, research, or engineering workflow needs sanitized handoff docs.17- A workflow mentions local paths, credentials, personal datasets, or private account names that must be removed before publication.1819## Import Rules2021- Convert local paths to repo-relative paths or placeholders.22- Replace live account names with role labels such as `operator`, `default profile`, or `workspace owner`.23- Describe credential requirements by provider name only.24- Keep examples narrow and operational.25- Do not ship raw workspace exports, tokens, OAuth files, health data, CRM data, or finance data.26- If the workflow requires private state to make sense, keep it local.2728## Sanitization Checklist2930Before committing an imported workflow, scan for:3132- absolute paths such as `/Users/...`33- `~/.hermes` paths unless the doc is explicitly explaining local setup34- API keys, tokens, cookies, OAuth files, or bearer strings35- phone numbers, private email addresses, and personal contact graphs36- client names, family names, or account names that are not already public37- revenue, health, or CRM details38- raw logs that include tool output from private systems3940## Conversion Pattern41421. Identify the repeatable operator loop.432. Strip private inputs and outputs.443. Rewrite local paths as repo-relative examples.454. Turn one-off instructions into a `When To Use` section and a short process.465. Add concrete output requirements.476. Run a secret and local-path scan before opening a PR.4849## Example: Launch Handoff5051Local Hermes prompt:5253```text54Read my local workspace files and finalize launch copy.55```5657ECC-safe version:5859```text60Use the public release pack under docs/releases/<version>/.61Return one X thread, one LinkedIn post, one recording checklist, and the missing assets list.62```6364## Example: Quiet-Hours Operator Job6566Local Hermes job:6768```text69Run my private inbox, finance, and content checks overnight.70```7172ECC-safe version:7374```text75Describe the scheduler policy, the quiet-hours window, the escalation rules, and the categories of checks. Do not include private data sources or credentials.76```7778## Output Contract7980Return:8182- candidate ECC skill name83- sanitized workflow summary84- required public inputs85- private inputs removed86- remaining risks87- files that should be created or updated
JunMystery