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.
Security Assessment
About hermes-imports
The hermes-imports skill converts local Hermes operator workflows into sanitized ECC skills and release-pack artifacts. It addresses the critical problem of preparing private, ad-hoc operator workflows for public reuse without exposing sensitive workspace state, credentials, local file paths, or personal data. When a Hermes workflow has proven its value through repeated use, this skill provides a structured process to transform it into a safe, reusable ECC component.
The skill's main capabilities include sanitization of local paths into repo-relative references, replacement of live account names with role labels, removal of credentials and tokens, and conversion of one-off instructions into structured documentation. It enforces a comprehensive sanitization checklist that scans for absolute paths, API keys, personal contact information, client names, health data, CRM details, and raw logs from private systems. The conversion pattern guides users through identifying repeatable operator loops, stripping private inputs and outputs, rewriting paths, and adding concrete output requirements.
This skill is designed for operators, engineering teams, and content creators who need to share stable workflow patterns across teams or publish them publicly. Common use cases include converting launch workflows into public handoff documentation, transforming research processes into reusable skills, and preparing engineering workflows for team-wide adoption. It ensures that valuable operational knowledge can be shared safely without compromising security, privacy, or organizational confidentiality.
FAQ
When should I use hermes-imports instead of keeping a workflow local?
Use hermes-imports when a Hermes workflow has repeated enough times to become reusable and you need to share it with others. If the workflow requires private state, credentials, or personal data to make sense, keep it local in Hermes rather than converting it to ECC.
What types of sensitive information does the sanitization process remove?
The sanitization checklist removes absolute paths, API keys and tokens, OAuth files, phone numbers, private email addresses, client and family names, account credentials, revenue data, health information, CRM details, and raw logs from private systems. Local paths are converted to repo-relative examples or placeholders.
What is the difference between Hermes and ECC in this context?
Hermes is the operator shell for private, ad-hoc workflows that may contain sensitive data and local state. ECC is the reusable workflow layer for public, sanitized patterns. Imports move stable patterns from Hermes into ECC without moving private state or credentials.
What should the output of a conversion include?
The output should include a candidate ECC skill name, sanitized workflow summary, required public inputs, documentation of private inputs that were removed, assessment of remaining risks, and a list of files that should be created or updated.
How do I handle workflows that reference local credentials or account names?
Replace live account names with role labels such as 'operator', 'default profile', or 'workspace owner'. Describe credential requirements by provider name only without including actual tokens or keys. If the workflow heavily depends on private credentials, consider whether it should remain local.
Install hermes-imports
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
affaan-m/everything-claude-code