Skip to content
Agentmart
Submit a tool

project-memory

Recall and use durable Snipara project memory.

Skill by Snipara

IndexedMIT
Write a review

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/snipara-project-memory

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

Recall and use durable Snipara project memory. Use for questions about prior decisions, workflows, architecture rationale, user preferences, troubleshooting outcomes, or continuity across agents.

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/project-memory

What's inside

Skill name
project-memory
Description
Recall and use durable Snipara project memory. Use for questions about prior decisions, workflows, architecture rationale, user preferences, troubleshooting outcomes, or continuity across agents.
License
MIT
Instructions
17 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Project Memory

Use Snipara as the durable memory layer for Cursor agents.

## Workflow

1. For memory questions, call `snipara_recall` with a focused query and project scope when available.
2. If the exact tool or scope is unclear, call `snipara_help` first and follow its tool guidance.
3. Treat returned memories as context, not as unquestionable truth. Prefer active, approved, high-confidence memories.
4. If memory and repository truth conflict, say so and verify with source files or fresh commands.
5. Do not persist anything unless the user made or validated a durable decision, workflow, preference, or troubleshooting outcome.

## Output

Answer with the relevant memory-derived facts first, then identify any uncertainty or stale context.

From Snipara/snipara-cursor-plugin, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 5, 2026 (3 months ago)
Last release
Jul 5, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

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

More from Snipara

Cite this page

project-memory skill. Agent Mart. https://agentmart.dev/skills/snipara-project-memory (last updated 2026-10-24)