hermes-imports
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseHermes Imports
Hermes 导入
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.
当你要将重复执行的Hermes工作流转换为可安全发布到ECC的内容时,请使用此技能。
Hermes是操作符shell,ECC是可复用工作流层。导入操作应将Hermes中的稳定模式迁移到ECC,同时不迁移私有状态。
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.
- Hermes工作流已重复执行足够多次,具备复用价值。
- 本地operator提示需要转换为公开的ECC skill。
- 启动、内容创作、研究或工程工作流需要经过清理的交接文档。
- 工作流中提及了本地路径、凭据、个人数据集或私有账户名称,这些内容在发布前必须移除。
Import Rules
导入规则
- Convert local paths to repo-relative paths or placeholders.
- Replace live account names with role labels such as ,
operator, ordefault profile.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.
- 将本地路径转换为相对仓库路径或占位符。
- 将真实账户名称替换为角色标签,例如、
operator或default profile。workspace owner - 仅按提供商名称描述凭据要求。
- 示例应简洁且具备可操作性。
- 不得传输原始工作区导出文件、令牌、OAuth文件、健康数据、CRM数据或财务数据。
- 如果工作流需要依赖私有状态才能正常运行,请保持其本地化。
Sanitization Checklist
清理检查清单
Before committing an imported workflow, scan for:
- absolute paths such as
/Users/... - paths unless the doc is explicitly explaining local setup
~/.hermes - 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
在提交导入的工作流之前,请检查以下内容:
- 绝对路径,例如
/Users/... - 路径(除非文档明确说明是本地设置)
~/.hermes - API密钥、令牌、Cookie、OAuth文件或Bearer字符串
- 电话号码、私有电子邮件地址和个人联系人信息
- 未公开的客户名称、姓氏或账户名称
- 收入、健康或CRM详情
- 包含私有系统工具输出的原始日志
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 section and a short process.
When To Use - Add concrete output requirements.
- Run a secret and local-path scan before opening a PR.
- 识别可重复的操作符循环。
- 移除私有输入和输出。
- 将本地路径重写为相对仓库的示例。
- 将一次性指令转换为“使用场景”部分和简短流程。
- 添加具体的输出要求。
- 在发起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.本地Hermes提示:
text
Read my local workspace files and finalize launch copy.ECC安全版本:
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.本地Hermes任务:
text
Run my private inbox, finance, and content checks overnight.ECC安全版本:
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
返回:
- 候选ECC skill名称
- 经过清理的工作流摘要
- 必需的公开输入
- 已移除的私有输入
- 剩余风险
- 应创建或更新的文件