AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ai Raccoon Memory

skill-arasz-ai-badger-ai-raccoon-memory · by Arasz

>-

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-arasz-ai-badger-ai-raccoon-memory

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-arasz-ai-badger-ai-raccoon-memory)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
17d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ai Raccoon Memory? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AiRaccoon Memory

When NOT to Use

  • A one-off lookup ("have we seen X before?") — run memory_search and be done, no watch ritual, no write-back
  • No docs directory to watch and no durable fact to write — the ritual adds ceremony, not value
  • The memory-grade hook when you only need one answer — it is opt-in by env var; don't enable it for a single search

1. Watch-on-docs ritual (do this first)

On session start, run memory_watch_status(projectId) for this project. If the docs directory is not in the watched list, run memory_watch_add(projectId, ) to mirror it into memory. The watch starts scanning and settles to healthy; an already-watched path is a no-op.

CLI prerequisite (only when the watch errors): watching-disabled or path-outside-scope means the one-time per-install setup is missing (quote the * so the shell does not expand it): ai-raccoon watch scope add '' , then ai-raccoon watch enable '' true. If the memory_watch_* tools are not listed at all (older tool build on another machine), update the tool: dotnet tool update -g arasz.ai-raccoon.

2. Search-first workflow

Always pass projectId. Before web search, code search, or asking the user, run memory_search(projectId, scope=all) with 2-3 formulations: exact phrase → keywords → plain-English restatement. Entries carry source paths — cite them as evidence.

3. Escalation by result

  • Decisive hit → use it; cite the source path.
  • Partial hit → one targeted external search, then reconcile.
  • No hit → search externally, then write the finding back with memory_write (source path included).

4. Write discipline

Durable facts only, one per entry, source included. Plain writes land in committed project memory (project:). For in-progress notes use workspace isolation: memory_workspace_beginmemory_workspace_statusmemory_workspace_consolidate(keep=[...]) (or ["all"] to promote everything; memory_workspace_discard to drop). Promote durable cross-project facts with memory_share — never automatically. memory_sweep removes old low-rated entries; shared entries are exempt.

5. Scopes

scope=all (default: shared + project), scope=project, scope=shared (the promotion tier only).

6. Gotchas

  • memory_write has no path param — the entry path is derived from its content.
  • Never pass context unless workspace isolation is intended: it silently sets

scope='custom', invisible to project-scoped search.

  • memory_embed_pending: omit limit to process all pending entries.
  • memory_delete_context requires full access mode.

7. Bulk ops

memory_ingest_file / memory_ingest_directory bulk-load files; memory_stats reports bank size; memory_sync exchanges snapshots with cloud storage when configured.

8. Verification Checklist

  • [ ] memory_watch_status shows the docs dir healthy
  • [ ] memory_search(projectId, scope=all) returns docs-derived hits
  • [ ] A durable finding was written back with memory_write, source path included

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.