memory-recall

Recalls durable Atmina Knowledge Base memory and verifies artifact claims before acting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-recall-latentminds-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-recall
Source: https://github.com/latentminds-ai/atmina-plugins/tree/main/plugins/atmina-codex/.agents/skills/memory-recall
Command: npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-recall-latentminds-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents acting on stale or unverified organizational memory cause real incidents, such as sending a renewal from the wrong CRM record because a procedure page named an account that no longer exists. This Skill enforces a verify-before-act discipline when reading durable memory from an Atmina Knowledge Base, so claims about artifacts are checked against their locators before any action is taken. ## Core Features & Use Cases - Ordered recall procedure: Orients with whoami, list_kbs, and get_context, then matches named artifacts via exhaustive list_files on the /applies_to pointer, and searches only the durable wiki/ scope with recency boosts. - Verify-before-act gate: Reads the product-computed attestation block (attested, drifted, unresolved, external) or runs a manual pin-and-span check with file_history and read_file before acting on any artifact claim. - Structured STOP and UNVERIFIED outcomes: Produces a fixed stop shape naming the claim, evidence id, locator, result, and what is not being done, and never substitutes a near match. - Use Case: A procedure page says to send a renewal from Salesforce account A-104. The account does not exist and only a similarly named HubSpot company is found; the Skill stops, reports the unresolved locator, and refuses to substitute the near match. ## Quick Start Ask the agent to look up a recorded decision or procedure from the Atmina Knowledge Base and verify it before acting on it.

Frequently Asked Questions about memory-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recall a decision or procedure from an Atmina Knowledge Base?

Orient with whoami, list_kbs, and get_context, then search scoped to wiki/ with recency boosts on event_date and updated_at. If the task names an artifact, first run list_files with an /applies_to eq filter, which is an exhaustive catalog match rather than a search.

How does verify-before-act work on a claim read from memory?

If the read_file response carries an attestation block, act on the entry's state: attested means proceed on the span, drifted or unresolved means stop, external means resolve the locator against the live system of record. Without the block, run the manual check using file_history, pinned version reads, and the span hash.

What is the difference between wiki, chronicle, and _consolidated in Atmina?

wiki/ holds durable primitives and is the only surface that can authorize action after verification. chronicle/ is the working notes layer, and _consolidated/ plus Pulse and Current State are compiled conveniences where source wiki content wins on any conflict.

Why does the applies_to filter return an error instead of matches?

The /applies_to pointer must be registered and the KB's query projection must be ready, otherwise list_files returns an error rather than an empty result. An error means the filter did not run, so fall through to durable search instead of reporting no matches.

Can this skill update stale or drifted memory it finds?

No, this path never writes. Stale, contradictory, or drifted durable content is reported through the STOP shape, and corrections are handled by the separate commit and maintain skills.

What happens when durable memory has no answer to a question?

The agent states that durable memory has no maintained answer and continues with live systems of record such as CRM, tickets, calendars, or ledgers. Absence from the wiki is not treated as proof that no truth exists elsewhere.