hermes-imports

Topics in the source

• Hermes Imports
• When To Use
• Import Rules
• Sanitization Checklist
• Conversion Pattern
• Example: Launch Handoff
• Example: Quiet-Hours Operator Job
• Output Contract

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. 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. 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. 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 s

This is an excerpt. Refer to the complete source and its current requirements.