Skip to content
Agentmart
Submit a tool

attic-recall

Pull ONE item back out of .attic/ by slug or search words and summarise it.

Skill by NishikantaRay

IndexedMIT★ 5
Write a review

Chalk Labs

Need help deploying attic-recall?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/nishikantaray-attic-recall

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Pull ONE item back out of .attic/ by slug or search words and summarise it. Use when the question names a TOPIC: "what did we find about X", "recall X", "what's in the attic about X", or when the user references an attic:<slug> handle. A question with no topic that just asks what the attic contains goes to attic-index instead.

Use cases: agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/attic-recall

What's inside

Skill name
attic-recall
Description
Pull ONE item back out of .attic/ by slug or search words and summarise it. Use when the question names a TOPIC: "what did we find about X", "recall X", "what's in the attic about X", or when the user references an attic:<slug> handle. A question with no topic that just asks what the attic contains goes to attic-index instead.
License
MIT
Instructions
49 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Recall from the attic

First, in the same shell command as anything below, locate the script:

```bash
ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)
```

Query: `$ARGUMENTS`.

```bash
node "$ATTIC_JS" recall "$ARGUMENTS"
```

The script scores slug, index hook and item body, returns the best match, and
lists alternatives.

1. No `.attic/` yet, or nothing matches: say so in one line and stop. Do not
   invent an answer or go read source files unless the user asks.
2. Several plausible matches: report the best one, then list the alternative
   handles in one line so the user can redirect.
3. Report the item in at most ten lines. Keep code, paths and commands
   verbatim. End with the handle.

Never rewrite or delete items while recalling.

## Freshness

Recall prints a trust line above the body, and for anything that is not
current, a warning with the reason. Pass it on — an item's staleness is part
of the item, and dropping it while quoting the conclusion is the failure this
release exists to prevent.

| What recall says | What you do |
|---|---|
| `current` | Use it. Mention the item is current only if asked. |
| `possibly-stale` | Quote it, then say which files changed and that it needs checking before it is relied on. |
| `needs-review` | As above, and do not present the claim as fact. A cited file may be gone. |
| `unverified` | Say it was recorded but never checked. |
| no trust line at all | An item from before 1.6. Treat its provenance as unknown, not as verified. |

The distinction to hold on to: `possibly-stale` means **a file underneath this
finding moved**, not that the finding is false. Report it as something to
check, never as something that is now wrong — you have not checked it either.

If the user acts on a stale item, offer to verify it against the current code
and record the result with `/attic-review`. Recall itself never writes.

From NishikantaRay/Attic, MIT.

More from NishikantaRay/Attic

Signals

Stars
5
Forks
0
Open issues
0
Last commit (this folder)
Sep 23, 2026 (1 month ago)
Last release
Sep 23, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from NishikantaRay

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get attic-recall running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying attic-recall?

CallGet help
Cite this page

attic-recall skill. Agent Mart. https://agentmart.dev/skills/nishikantaray-attic-recall (last updated 2026-10-24)