Skip to main content
Glama
liza-studio

skillmem — long-term memory for Claude Code & Codex

by liza-studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mem_pin

Pin a record so decay never marks it irrelevant and archiving cannot remove it, or unpin it to restore normal decay. Changes only the pin flag; text and approval stay intact.

Instructions

Pin a record so it never decays and is never archived, or unpin it (pinned=false). WRITES the flag and nothing else — reversible, and text, approval and updated_at are untouched. For a rule that matters precisely because it is rarely needed — a deploy gate, a safety constraint — where decay would read rarity as irrelevance. A pinned record cannot be archived until unpinned; unpinning does not un-archive it, and pinning an archived record leaves it archived. Only the owner changes the pin of a record they wrote or approved. Fails for an unknown slug. Returns the slug, the pinned state, whether the flag changed, and the record's current lifecycle. Use mem_reinforce for skills that should earn their strength. Retiring a record is the owner's own call at a terminal (skillmem skills-archive <slug>), not an agent's.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug of the record to pin (any kind).
pinnedNotrue to pin (default), false to unpin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.1
    • changedInput schema / properties / slug / description
      Previous value: -"Skill slug to pin."New value: +"Slug of the record to pin (any kind)."
  2. First observedv0.10.5

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does: it discloses the write is flag-only and reversible, that text/approval/updated_at are untouched, the archived-state interactions, the owner-only authorization rule, and the unknown-slug failure mode.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and effect, and the trailing sentences are edge cases and routing rather than filler. It is dense and long, but nearly every clause carries distinct operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param mutation tool with no output schema, the description covers effect, reversibility, authorization, failure mode, and even enumerates the return payload, leaving nothing an agent needs missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3, but the description adds real semantics beyond it: the default-true behavior of the flag, plus the non-obvious interaction that pinning an archived record leaves it archived. That is meaning the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (pin/unpin) and resource (record) with the exact effect: never decays, never archived. Explicitly separates itself from mem_reinforce and from the CLI archive path, so an agent can route without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the when ('a rule that matters precisely because it is rarely needed — a deploy gate, a safety constraint'), the alternative ('Use mem_reinforce for skills that should earn their strength'), and an explicit exclusion ('Retiring a record is the owner's own call at a terminal ... not an agent's').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools