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-imports
3description: 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.
4origin: ECC
5---
6
7# Hermes Imports
8
9Use this skill when turning a repeated Hermes workflow into something safe to ship in ECC.
10
11Hermes is the operator shell. ECC is the reusable workflow layer. Imports should move stable patterns from Hermes into ECC without moving private state.
12
13## When To Use
14
15- A Hermes workflow has repeated enough times to become reusable.
16- A local operator prompt should become a public ECC skill.
17- A launch, content, research, or engineering workflow needs sanitized handoff docs.
18- A workflow mentions local paths, credentials, personal datasets, or private account names that must be removed before publication.
19
20## Import Rules
21
22- Convert local paths to repo-relative paths or placeholders.
23- Replace live account names with role labels such as `operator`, `default profile`, or `workspace owner`.
24- Describe credential requirements by provider name only.
25- Keep examples narrow and operational.
26- Do not ship raw workspace exports, tokens, OAuth files, health data, CRM data, or finance data.
27- If the workflow requires private state to make sense, keep it local.
28
29## Sanitization Checklist
30
31Before committing an imported workflow, scan for:
32
33- absolute paths such as `/Users/...`
34- `~/.hermes` paths unless the doc is explicitly explaining local setup
35- API keys, tokens, cookies, OAuth files, or bearer strings
36- phone numbers, private email addresses, and personal contact graphs
37- client names, family names, or account names that are not already public
38- revenue, health, or CRM details
39- raw logs that include tool output from private systems
40
41## Conversion Pattern
42
431. Identify the repeatable operator loop.
442. Strip private inputs and outputs.
453. Rewrite local paths as repo-relative examples.
464. Turn one-off instructions into a `When To Use` section and a short process.
475. Add concrete output requirements.
486. Run a secret and local-path scan before opening a PR.
49
50## Example: Launch Handoff
51
52Local Hermes prompt:
53
54```text
55Read my local workspace files and finalize launch copy.
56```
57
58ECC-safe version:
59
60```text
61Use the public release pack under docs/releases/<version>/.
62Return one X thread, one LinkedIn post, one recording checklist, and the missing assets list.
63```
64
65## Example: Quiet-Hours Operator Job
66
67Local Hermes job:
68
69```text
70Run my private inbox, finance, and content checks overnight.
71```
72
73ECC-safe version:
74
75```text
76Describe the scheduler policy, the quiet-hours window, the escalation rules, and the categories of checks. Do not include private data sources or credentials.
77```
78
79## Output Contract
80
81Return:
82
83- candidate ECC skill name
84- sanitized workflow summary
85- required public inputs
86- private inputs removed
87- remaining risks
88- files that should be created or updated
yanacuti1121 