CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentmemory-rest-api

The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.

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

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, copy-paste-ready quick start with sound auth and conventions sections and a correct keep-the-bulk-in-REFERENCE.md instinct. Its one material defect is that both files it navigates to (REFERENCE.md, TROUBLESHOOTING.md) are missing from the bundle, leaving the disclosure chain broken.

Suggestions

Ship REFERENCE.md and TROUBLESHOOTING.md in the skill bundle (or remove/inline the pointers) so the body's links to the full endpoint list and failure guidance resolve instead of dangling.

Move the remote-daemon and .env secret edge cases from the Auth paragraph into TROUBLESHOOTING.md, keeping only the localhost secret-loading rule inline.

Add one explicit error-recovery line for common failures (e.g., 'on 400, check field names against REFERENCE.md and retry') to close the feedback loop the status-code conventions imply.

DimensionReasoningScore

Conciseness

Quotes: the Quick start is lean executable curl with only essential comments, and Conventions is tight bullets ('Save returns 201, reads return 200, validation errors return 400'). The Auth paragraph packs many edge cases inline ('if the daemon uses a secret from its .env... For a remote daemon, require an explicit credential... Never forward a local-file secret or follow an authenticated redirect'), some of which could be trimmed or moved to TROUBLESHOOTING.md, so it is efficient-with-minor-trimmings (anchor 4) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Quotes: complete copy-paste curl commands for liveness, save ('-d '{"content":"chose JWT refresh rotation","concepts":["jwt-refresh-rotation"]}'' with Authorization and Content-Type headers), and recall, plus a working secret-loading snippet with a guard ('test -n "$agentmemory_secret" || exit 1'). The examples are fully executable and cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Quotes: an implicit clear sequence (liveness check → load/validate secret → authenticated calls) with an explicit checkpoint ('test -n "$agentmemory_secret" || exit 1') and error semantics ('Requests without the header get 401', 'validation errors return 400') plus a TROUBLESHOOTING.md pointer for failures. It is anchor 4 rather than anchor 5 because there is no explicit validate-and-retry loop (e.g., what to do on a 400 beyond the reference pointer), though as a simple single-purpose skill it avoids the destructive/batch cap.

4 / 5

Progressive Disclosure

Quotes: 'The full endpoint list with methods lives in REFERENCE.md' and 'See [TROUBLESHOOTING.md](TROUBLESHOOTING.md)' — the right disclosure pattern (few key examples inline, bulk deferred), but neither file exists in the bundle (no references/, scripts/, assets/, or root-level REFERENCE.md/TROUBLESHOOTING.md are present), so the skill's navigation points to dangling files. Scoring against the actual bundle structure per the rubric guideline, the broken references are a real organization flaw that offsets the otherwise good sectioning, landing at anchor 3 rather than anchor 4.

3 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit and well-conditions 'Use when...' clause and clear REST-vs-MCP positioning. Its main weakness is that it describes the surface without naming any concrete memory operations, leaving the 'what' slightly generic.

DimensionReasoningScore

Specificity

Quotes: 'The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server' names the domain, and 'calling agentmemory over HTTP... integrating a host that does not speak MCP' gives 1-2 concrete usage actions. It matches anchor 3 (domain plus a couple of concrete actions) rather than anchor 4 because it never enumerates the actual memory operations (save, recall, search) the API supports, and anchor 2 fits less well since it goes beyond bare domain naming.

3 / 5

Completeness

Quotes: what — 'The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server'; when — 'Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.' Both what and when are answered explicitly with three concrete trigger conditions, matching anchor 5; anchor 4's 'when could be more explicit' does not apply since the when clause is highly specific.

5 / 5

Trigger Term Quality

Quotes: 'calling agentmemory over HTTP', 'MCP is unavailable and you need a fallback', 'integrating a host that does not speak MCP' — natural phrases a user in this domain would say. Good keyword coverage (HTTP, REST, API, MCP, fallback) but a few natural terms like 'endpoint', 'curl', or 'localhost' are missing, so it sits at anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'primary protocol for talking to the memory server', 'when MCP is unavailable and you need a fallback' — clear niche positioning against the MCP bridge. Minor overlap risk remains with the closely related agentmemory-mcp-tools skill for generic 'use agentmemory' requests, placing it at anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

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-rest-api/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.