---
id: gh-hermes-imports
name: "hermes-imports"
url: https://skills.yangsir.net/skill/gh-hermes-imports
author: affaan-m
domain: ai-skill-platform-ecosystem
tags: ["workflow-sanitization", "skill-publishing", "data-privacy", "ecosystem-tools", "hermes-ecc"]
install_count: 1400
rating: 4.30 (120 reviews)
github: https://github.com/affaan-m/everything-claude-code/tree/main/skills/hermes-imports
---

# hermes-imports

> 将本地 Hermes 操作员工作流转换为经过净化的 ECC 技能和发布包。确保在公开重用 Hermes 工作流时，不泄露私有工作区状态、凭据或本地路径，实现安全发布和标准化。

**Stats**: 1,400 installs · 4.3/5 (120 reviews)

## Before / After 对比

### 安全发布工作流

**Before**:

在没有标准化工具辅助下，手动审查 Hermes 工作流以移除所有私有数据（如本地路径、凭据、个人信息），耗时且极易遗漏，导致敏感信息泄露风险高，阻碍了工作流的快速共享和复用。

**After**:

通过 SkillForge 的 Hermes 导入工具，遵循明确的净化规则和检查清单，大幅减少人工审查时间，有效避免敏感数据泄露，加速本地工作流向 ECC 技能的安全转换与发布。

| Metric | Before | After | Change |
|---|---|---|---|
| 人工审查时间 | 120分钟 | 30分钟 | -75% |

## Readme

# 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


---
*Source: https://skills.yangsir.net/skill/gh-hermes-imports*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-hermes-imports/markdown*