Hermes Imports

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

• 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

Read my local workspace files and finalize launch copy.

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

Run my private inbox, finance, and content checks overnight.

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

• candidate ECC skill name
• sanitized workflow summary
• required public inputs
• private inputs removed
• remaining risks
• files that should be created or updated