CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentmemory-hooks

The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.

Quality

82%

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

75%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 dense, actionable instruction skill: almost every line is a specific command, flag, limit, or gotcha rather than general knowledge, and install flows include verification steps. The main defects are the vague Hermes/OpenClaw setup pointer and the two referenced files being absent from the provided bundle, which leaves the skill's progressive-disclosure links unresolvable.

Suggestions

Ship TROUBLESHOOTING.md and REFERENCE.md in the skill bundle (e.g., under references/); both are linked from the body but neither file exists in the provided bundle, so the links currently dangle.

For Hermes and OpenClaw, anchor "Follow the matching integration setup instructions" to a concrete path or link so the setup step is executable like the other platforms.

Tighten lines that restate the obvious, e.g. "They send what they record to the local agentmemory server, which stores it on this machine" — the storage behavior is already conveyed by the spool and server notes.

DimensionReasoningScore

Conciseness

Nearly every line carries plugin-specific facts Claude would not know ("registers 12 hooks", "at most 5 MiB, kept up to 7 days", AGENTMEMORY_* flags, "up to 4,000 characters") with no padding about general concepts. Minor trimming is possible (e.g., "They send what they record to the local agentmemory server, which stores it on this machine"), keeping it at anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Copy-paste-ready commands cover the main platforms ("/plugin marketplace add rohitg00/agentmemory", "devin plugins install rohitg00/agentmemory#plugin", "agentmemory connect pi --with-mcp", "/hooks", "/agentmemory-status", "http://localhost:3113"). Not 5 because the Hermes/OpenClaw branch says only "Follow the matching integration setup instructions" without saying where those instructions live — a concrete gap in executable guidance.

4 / 5

Workflow Clarity

Each install flow is sequenced with explicit verification checkpoints ("Run /hooks inside Devin to confirm the agentmemory hooks are loaded", "verify a real turn creates an observation", "inspect /agentmemory-status") plus an error-recovery path ("If observations are missing, confirm the plugin is enabled and the server is running"). Anchor 5 is not reached because the fix-retry loop is delegated to a TROUBLESHOOTING.md that is not in the bundle and the Hermes/OpenClaw sequence is underspecified.

4 / 5

Progressive Disclosure

The pattern is right: a concise overview with clearly signaled one-level references ("See [TROUBLESHOOTING.md](TROUBLESHOOTING.md)", "The exact registered hook events live in REFERENCE.md, generated from plugin/hooks/hooks.json") and a "See also" section for sibling skills. Scored against the actual bundle, however, neither referenced file exists (no references/, scripts/, or assets/ directories and no TROUBLESHOOTING.md or REFERENCE.md alongside SKILL.md), so the best links dangle — a minor organization gap per anchor 4 rather than a well-resolved anchor 5.

4 / 5

Total

16

/

20

Passed

Description

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

The description cleanly states what the hooks do and provides three explicit, natural trigger scenarios, closely matching the rubric's good-example pattern. Remaining upside is modest: broader synonym coverage and a sharper boundary versus the config skill.

DimensionReasoningScore

Specificity

"capture observations automatically across the agent session lifecycle" names the concrete function, and the enumerated scenarios ("explaining how memory gets captured without manual saves", "debugging missing observations", "tuning what gets recorded") are concrete use cases. It sits above anchor 3 (only 1-2 actions, not comprehensive) because three specific scenarios are given, but below anchor 5 because the skill itself is described as a single capability rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both: what ("plugin hooks that capture observations automatically across the agent session lifecycle") and when ("Use when explaining... when debugging missing observations, or when tuning what gets recorded") with three concrete trigger phrases. This matches the anchor-5 example pattern; anchor 4's 'when could be more explicit' does not apply since the triggers are enumerated and specific.

5 / 5

Trigger Term Quality

Phrases like "debugging missing observations", "without manual saves", and "tuning what gets recorded" are natural things a user would say. Not 5 because common variations and synonyms (e.g., "memory not saving", "recall", "hook events") are missing; not 3 because the included terms go beyond domain keywords to genuine user phrasings.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (automatic capture via plugin lifecycle hooks) and triggers are distinct, but "tuning what gets recorded" overlaps the sibling agentmemory-config skill's territory (which the body says owns "the capture and injection flags"). Mostly distinct with minor overlap risk against a closely related skill, per anchor 4.

4 / 5

Total

17

/

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-hooks/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.