affaan-m/ecc

hermes-imports

Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/affaan-m/ecc --skill hermes-imports

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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

Related by task

from this repository

More skills

All skills
affaan-m
Community

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24h installs
489
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1h installs
5
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20
affaan-m
Community

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20