unified-memory

Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.

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

81%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.

The body is highly actionable with executable CLI examples, a clearly sequenced workflow, and genuine validation feedback loops. Its main weakness is conciseness — the evidence-handling policy prose and domain background pad the file beyond what operating the vault requires.

Suggestions

Trim or move the "Recall is evidence, not certainty" policy prose and the "portable part of Desk-style memory" paragraph into a reference file; keep only the operational rules (bind lookup to workspace, handle ECC_MEMORY_INCOMPLETE, check source freshness) inline.

Split MCP setup (server command, environment variables, exposed tool list) into a references/mcp-setup.md file and keep a one-line pointer in the main body.

Clarify the `mcp-configs/mcp-servers.json` reference — it points outside the skill bundle, so state where that file lives or inline the minimal server entry.

Dimension	Reasoning	Score
Conciseness	Mostly operational, but sections like "This is the portable part of Desk-style memory: scoped evidence, current-state checks and explicit uncertainty ... Supplier relationship graphs remain an optional domain-specific adapter" and the long "Recall is evidence, not certainty" policy prose explain domain background Claude does not need and could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout: `ecc memory search "authentication migration" --target-harness codex`, the complete `printf ... \| ecc memory save --title ... --stdin` pipeline, `ecc memory handoff --from codex ... --body-file handoff.md`, `ecc memory doctor`, plus named MCP tools and setup commands covering the common cases.	5 / 5
Workflow Clarity	Clear numbered sequence (recall before writing → save → hand off → validate) with explicit validation (`ecc memory doctor`, prerequisite `command -v ecc-memory-mcp`) and a real feedback loop: `ECC_MEMORY_INCOMPLETE` → "Repair the reported vault problem; do not tell the caller the memory does not exist."	5 / 5
Progressive Disclosure	Well-organized sections with clear headers, but the ~190-line body inlines the MCP setup details and a long policy section that could live in reference files; the pointer to `mcp-configs/mcp-servers.json` references a file outside the skill bundle.	4 / 5
	Total	17 / 20 Passed

Description

87%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, concrete, and explicit about both capabilities and trigger conditions, with named agent platforms giving it a distinct activation niche. Its only weaknesses are a missing synonym for plain "memory" and omission of the vault-diagnosis use case.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions ("save work state, transfer context, resume another agent's task, or search shared project knowledge") with only a minor gap — the diagnose/validate use case from the body is not mentioned.	4 / 5
Completeness	Clearly answers both: the what ("Share durable, inspectable context and handoffs between ... agents through the local ECC Memory Vault") and an explicit "Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge" trigger clause.	5 / 5
Trigger Term Quality	Good keyword coverage including natural phrases ("handoffs", "save work state", "resume another agent's task", "search shared project knowledge") and named agents (Claude, Codex, Hermes, Cursor, OpenCode), but a few natural synonyms such as plain "memory" are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche — cross-agent memory vault handoffs — with distinct triggers (named harnesses, "ECC Memory Vault", "handoffs") that are unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/unified-memory/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.