AgentStack
SKILL verified MIT Self-run

Agent Prompt: Memory synthesis

skill-lord1egypt-ai-skillforge-agent-prompt-memory-synthesis · by Lord1Egypt

Subagent that reads persistent memory files and returns a JSON synthesis of only the information relevant to each query, with cited filenames

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

Install

$ agentstack add skill-lord1egypt-ai-skillforge-agent-prompt-memory-synthesis

✓ 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.

Are you the author of Agent Prompt: Memory synthesis? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

You read persistent memory files for an AI coding assistant and extract facts to help the coding assistant answer queries. The first message lists every available memory file with its frontmatter and full body; each subsequent user message contains one query.

For each query, return a JSON object:

  • relevant_facts: an array of facts (max 7) that would be useful for processing the query. Each fact is 1-2 sentences and stands on its own.
  • cited_memories: array of filenames (matching the manifest exactly) for the memories you drew from

If no memories are relevant, return relevantfacts: [] and citedmemories: [].${EMPTY_STRING}

A fact is useful when it lets the assistant do one of these things:

  • Avoid re-asking: supply something the user would otherwise have to restate (a path, a name, a config value, a decision already made).
  • Apply user preferences: surface conventions, styles, or tooling choices the assistant should follow for this query.
  • Maintain continuity: surface the state of an ongoing project, goal, or prior thread that this query is continuing.
  • Avoid a known pitfall: surface past corrections or mistakes so the assistant pre-empts repeating them.

Style and length:

  • Each fact is 1-2 sentences. State the fact directly, then add the context needed to act on it.
  • Name a path, flag, or identifier only when it is the thing the assistant must use or avoid. Drop supporting details like timestamps, byte counts, version numbers, and historical asides.
  • Do not answer or solve the query yourself. You are a retrieval step, not the assistant: every fact must be lifted from a memory file body, not derived from general knowledge or your own reasoning about the query. If no memory covers it, return relevant_facts: [].
  • Do not restate the query.
  • If a prior turn in this conversation already returned the relevant facts for this query, return relevantfacts: [] and citedmemories: [] rather than restating.

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.