- Home
- Skills
- Productivity
- Session Memory Kit
Session Memory Kit
Two markdown files and five habits that stop your agent from forgetting the plan, redoing finished work, or trusting a stale "tests pass" after compaction.
$9
Works with the AI Agents you already use
Session Memory Kit
Example session with this skill installed
I'm back. We had to restart the session. Where were we on the API refactor?
- Read your context and instructions
- Compiled the session memory kit
I have read the progress.md and history.md files to restore the session state. I also verified the current repository state against the last recorded task.
Session Restore: API Refactor
| Component | Status | Notes |
|---|---|---|
| Current Goal | Decouple Auth middleware from Express routing | Targeted for v2.1 compatibility |
| Completed | Extracted auth.logic.ts, created unit tests | Tests passed in previous session |
| Next Action | Update routes/user.ts to use the new provider | Blocked by missing IAuthProvider interface |
| Last Decision | Used Dependency Injection over Singletons | Reason: Testability and avoiding global state issues |
| Failed Path | Manual token extraction in each route | Reason: Resulted in 40% code duplication; reverted |
Verification Check:
git statusconfirmsauth.logic.tsis staged.npm testconfirms 4 new tests are passing.- The
IAuthProviderinterface is indeed missing fromtypes/index.ts.
Next steps
- Define the
IAuthProviderinterface insrc/types/auth.d.ts. - Update the User route constructor to accept the new provider.
- Run the integration test suite to verify the handoff.
Connects securely to your tools. The creator never sees your data.
About this skill
Context compaction and session restarts often cause agents to lose track of completed tasks, leading to redundant work or hallucinated "passing" states. This skill implements a persistent state management system using two lightweight Markdown files in your project root to ensure continuity across long-running coding sessions.
What it does
- Persistent Progress Tracking maintains a
progress.mdfile detailing the current goal, completed steps, and active blockers. - Decision Logging records architectural choices and failed experiments in
history.mdto prevent repetitive errors. - State Verification forces a check of the actual repo state (
git log, test runs) after compaction instead of trusting stale context. - Session Handoffs generates a structured note before shutdown so the next session starts with the correct command.
- Design Pre-approvals requires a short design plan before code execution to ensure alignment on multi-file changes.
How it works
- Initialization: Create
progress.mdandhistory.mdfrom templates if they do not exist in the root. - Resumption: Read
progress.mdimmediately after context compaction or a restart before running other commands. - Observation: Update files only when a unit of work finishes, a decision is made, or a direction changes.
- Completion: Run the full test suite in the current context before declaring any task finished.
Frameworks & tools
This skill is framework-agnostic and works with any terminal-based agent like Claude Code or Cursor. It relies on standard git commands and local Markdown file manipulation.
Why this beats prompting it yourself
Manual prompts for "remember this" are easily lost during context window slides. This skill enforces a disk-backed source of truth that survives restarts, ensuring the agent never retries a failed approach it already discarded two hours ago.
Use cases
- Resuming a complex refactor after a weekend or a long break.
- Preventing the agent from reverting a specific architectural decision during a long session.
- Handing off a half-finished feature to a different agent or a human developer.
- Ensuring "tests pass" claims are verified against the current environment after a summary.
Known limitations
Files must be kept under 180 lines to remain efficient. Requires the agent to have file system write access to the project root.
Requires filesystem write access to the project root. Files must be kept under 180 lines. Relies on the agent correctly identifying compaction events.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 day ago
Requires