hermes-imports

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill hermes-imports-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-imports
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/hermes-imports
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill hermes-imports-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeated local operator workflows often contain private paths, credentials, and personal data that make them unsafe to publish. This Skill converts those Hermes workflows into sanitized, reusable ECC skills without leaking workspace state. ## Core Features & Use Cases - Workflow Sanitization: Rewrites absolute paths, account names, and credential references into repo-relative placeholders and role labels. - Sanitization Checklist: Scans imported workflows for tokens, OAuth files, private contact data, CRM details, and raw private logs before publication. - Structured Output Contract: Returns the candidate skill name, sanitized summary, required public inputs, removed private inputs, remaining risks, and files to create or update. - Use Case: You have a local Hermes launch prompt that reads private workspace files. Use this Skill to rewrite it as a public ECC workflow that operates on a release pack under docs/releases/<version>/ and returns launch copy deliverables. ## Quick Start Convert my local Hermes launch workflow into a sanitized ECC skill and list the private inputs that must be removed.

Frequently Asked Questions about hermes-imports

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a local Hermes workflow into a public ECC skill?▼

Identify the repeatable operator loop, strip private inputs and outputs, rewrite local paths as repo-relative examples, and turn one-off instructions into a When To Use section with a short process. Run a secret and local-path scan before opening a PR.

What private data must be removed before publishing a workflow?▼

Remove absolute paths like /Users/..., API keys, tokens, cookies, OAuth files, phone numbers, private emails, client or family names, revenue, health, and CRM details, plus raw logs from private systems. Describe credential needs by provider name only.

When should a Hermes workflow stay local instead of being imported?▼

Keep the workflow local if it requires private state to make sense, such as personal inbox, finance, or health checks. Only stable, repeatable patterns that work with public inputs should move into ECC.

What output does the Hermes import process return?▼

It returns a candidate ECC skill name, a sanitized workflow summary, required public inputs, the private inputs removed, remaining risks, and the files that should be created or updated.

How should account names and credentials be handled in sanitized docs?▼

Replace live account names with role labels such as operator, default profile, or workspace owner. Describe credential requirements by provider name only, never including actual tokens or OAuth files.