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.
Get the complete skill folder, including its scripts and reference files.
·
When to use this skill
Use Hermes Imports when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Hermes Imports when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/hermes-imports # Save SKILL.md to ~/.claude/skills/hermes-imports/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/hermes-imports/SKILL.md. For a shared project, commit the folder at .claude/skills/hermes-imports/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Hermes Imports skill for this task: A Hermes workflow has repeated enough times to become reusable. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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:
```text Read my local workspace files and finalize launch copy. ```
ECC-safe version:
```text 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:
```text Run my private inbox, finance, and content checks overnight. ```
ECC-safe version:
```text 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
Intended uses
- 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.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.