CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentmemory-agents

How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an efficient, highly actionable connector guide with concrete commands, host-specific flags, and a workflow that includes authorization and validation checkpoints. Its main weaknesses are the dangling references to REFERENCE.md and TROUBLESHOOTING.md, which are absent from the bundle and break the progressive-disclosure structure the workflow depends on, plus minor time-sensitive detail (a pinned npx version) in the Notes.

Suggestions

Ship REFERENCE.md (with the adapter table) and TROUBLESHOOTING.md in the skill bundle — Workflow step 2 directs the reader to "the table in REFERENCE.md", which is currently missing and blocks execution for unlisted hosts.

Move the pinned "npx skills@1.7.1" version and the provenance note "generated from src/cli/connect/" out of the body (e.g., into REFERENCE.md or a maintenance section) to keep the main file free of time-sensitive tokens.

Add an explicit recovery loop to Workflow step 3 (what to do when the save/recall check fails or the host still doesn't list agentmemory's tools) instead of relying solely on the TROUBLESHOOTING.md link.

DimensionReasoningScore

Conciseness

The body is lean and operational with no concept explanations Claude already knows, but the pinned "npx skills@1.7.1" is time-sensitive version information outside any deprecated/old-patterns section, and "generated from `src/cli/connect/`" is repo-internal detail that costs tokens without aiding execution. Not 5 because of these trimmable tokens; not 3 because padding is minimal and isolated.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: "agentmemory connect claude-code", "agentmemory connect pi --with-mcp", "agentmemory connect dsh --with-hooks", "devin plugins install rohitg00/agentmemory#plugin", "npx skills@1.7.1 add rohitg00/agentmemory --agent hermes-agent --skill '*'", plus concrete reload/verification commands (/reload, /agentmemory-status, /mcp).

5 / 5

Workflow Clarity

The 3-step Workflow has clear sequencing with an authorization guard ("If unknown, ask which host to configure before changing files"), an explicit failure signal ("an adapter that prints manual setup instructions has not completed installation"), and validation ("inspect its actual tool inventory, and perform an authorized save/recall check"). Not 5 because there is no stated recovery path if the save/recall check fails — recovery is delegated to a TROUBLESHOOTING.md link rather than a feedback loop.

4 / 5

Progressive Disclosure

Sections are well organized and the references are clearly signaled and one level deep ("[TROUBLESHOOTING.md](TROUBLESHOOTING.md)", "lives in REFERENCE.md"), but the bundle contains no files at all — neither REFERENCE.md nor TROUBLESHOOTING.md exists — so Workflow step 2's required adapter-name table is unreachable. Not 4 because a missing critical reference is more than a minor organization gap; not 2 because the inline content is appropriately placed and well structured for the main level.

3 / 5

Total

16

/

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: it states a concrete capability, gives an explicit multi-trigger "Use when" clause in third person, and occupies a distinct niche. Minor room to improve by mentioning what the connect command actually does (merge config, preserve existing servers) or naming common hosts.

DimensionReasoningScore

Specificity

"How agentmemory wires into host coding agents via the connect command" names the tool, domain, and command, and the when-clause adds three concrete actions ("installing agentmemory into a specific agent", "asked which agents are supported", "a connect adapter writes the wrong config path"). Not 5 because the description only partially conveys what connect actually does (merging config, preserving existing servers, wiring the MCP bridge); not 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both questions: the what ("How agentmemory wires into host coding agents via the connect command") and the when ("Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path") with three concrete trigger phrases, matching the top anchor pattern.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as "installing agentmemory into a specific agent", "which agents are supported", and "writes the wrong config path". Not 5 because it omits host-name keywords (claude code, cursor, codex) and common synonyms like "set up" or "integrate"; not 3 because the trigger vocabulary is specific and varied rather than partially covered.

4 / 5

Distinctiveness Conflict Risk

"agentmemory" is a distinct named tool and the triggers are specific to the connect command and its adapters, creating a clear niche with minimal conflict risk. It is clearly distinguishable from sibling agentmemory skills (mcp-tools, rest-api, hooks) whose triggers concern tool usage rather than host wiring.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

rohitg00/agentmemory

Path

plugin/skills/agentmemory-agents/SKILL.md

Reviewed

Table of Contents

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.