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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted, lean instruction skill: concrete import rules, a practical sanitization checklist, before/after conversion examples, and a defined output contract, all in clearly organized sections. The only improvements are naming the actual scan tool/command and adding an explicit fix-and-rescan loop after the validation step.

Suggestions

Make step 6 of the Conversion Pattern executable by naming the concrete scan tool or command to run (e.g., a grep pattern for absolute paths and token formats), so the validation step is copy-paste ready.

Add an explicit feedback loop after the sanitization scan: if the scan finds a leak, fix it and re-scan before proceeding to the PR step.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; the only background lines ("Hermes is the operator shell. ECC is the reusable workflow layer.") are non-obvious domain context that justifies their tokens, matching the 'every token earns its place' anchor.	5 / 5
Actionability	Guidance is concrete and executable for an instruction-only skill — specific replacement rules ("Replace live account names with role labels such as `operator`"), a concrete scan checklist, and before/after examples. It stops short of the 5 anchor because step 6 ("Run a secret and local-path scan") names no tool or command, leaving a minor gap in copy-paste readiness.	4 / 5
Workflow Clarity	The 6-step Conversion Pattern is clearly sequenced with a validation gate ("Run a secret and local-path scan before opening a PR") plus a pre-commit sanitization checklist, so the missing-validation cap does not apply. It falls short of the 5 anchor because there is no explicit validate-fix-retry feedback loop if the scan finds something.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), and the ~80-line body is well-sectioned and self-contained with nothing inlined that belongs in a separate file and no nested references — an appropriately structured single-file skill with easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, with an explicit 'Use when...' clause carrying concrete triggers around private state, credentials, and local paths. The only weakness is that the capability list is limited to roughly two actions rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	"Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts" names the domain and two concrete actions (convert, sanitize), matching the 1-2-action anchor; it does not list several specific actions, so it falls short of the 4 anchor.	3 / 5
Completeness	It explicitly answers both what ("Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts") and when ("Use when preparing a Hermes workflow for public ECC reuse without leaking private workspace state, credentials, or local-only paths") with concrete trigger phrases, matching the 5 anchor; the when-clause is explicit, not weakly implied as at 4.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ("public ECC reuse", "credentials", "local-only paths", "private workspace state") with good coverage, but common synonyms such as "publish", "share", or "sanitize this workflow" are missing, so it falls just below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The named-domain niche (Hermes operator workflows imported into ECC) with distinct trigger terms gives it a clear niche with minimal overlap risk against other skills, matching the 5 anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/hermes-imports/SKILL.md
Commit: c70874f

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.