More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Agent Session Continuity

    2

    Maintain structured context across agent restarts so your agent remembers decisions, progress, and next steps.

    Free

    4 usesSecurity scanned
    agent-session-continuity

    agent-session-continuity

    Example session with this skill installed

    "Continue working on the payment integration"

    • Read your context and instructions
    • Compiled the agent-session-continuity

    [Reads .claude/session-journal.md]
    "Last session (July 10): Completed Stripe checkout session creation and webhook handler. In progress: subscription management (~60% done). Blocked on: refresh token storage strategy — you wanted httpOnly cookies but security review hasn't happened yet.

    Next steps: Complete subscription management in src/billing/subscriptions.ts, handle Stripe webhook signature verification, add idempotency keys.

    Shall I pick up from subscription management?"

    You: "Yes, and let's use httpOnly cookies for the token"

    Agent: "I'll implement httpOnly cookies. I'm writing ADR-003 to document this decision — httpOnly cookies selected over localStorage because they prevent XSS-based token theft, consistent with our security-first approach noted in ADR-001."

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The Problem

    You spent 45 minutes last session debugging a subtle race condition in the payment flow, decided to use PostgreSQL LISTEN/NOTIFY over Redis Pub/Sub, and had the agent create three new files. Today you open a new session and say "continue working on the payment integration." The agent responds: "I don't have context from previous sessions. Could you describe what you're building?" You just lost 15 minutes re-explaining what the agent already knew.

    What You Get

    • Session journal system — structured .claude/session-journal.md (or equivalent) that captures Accomplished, In Progress, Open Decisions, Files Created/Modified, and Next Steps at every session end
    • Machine-readable state file — .claude/state.json tracks last session timestamp, current feature, feature status, blockers, test status, and next steps in a parseable format
    • Architecture Decision Records (ADR) — session decisions are captured in .claude/decisions/ with context, alternatives considered, decision rationale, and consequences
    • Automatic session start context — agent reads journal + state + ADRs at session start and summarizes the last session in 1-3 sentences without being prompted
    • Contradiction detection — when the agent is about to make a decision that conflicts with a prior ADR, it flags the contradiction and asks for confirmation
    • Agent-agnostic directory structure — works across Claude Code (.claude/), Cursor (.cursor/), and Codex CLI (.codex/) with automatic directory detection

    Why This Beats Prompting It Yourself

    You could write "remember our last session" in your CLAUDE.md. But the agent has no structured mechanism to read what "last session" contained. This skill creates the file system infrastructure — journal, state file, ADRs — that gives the agent something concrete to read, parse, and act on. Without structured files, context continuity is hope, not architecture.

    Example Session

    You: "Continue working on the payment integration"

    Agent: [Reads .claude/session-journal.md] "Last session (July 10): Completed Stripe checkout session creation and webhook handler. In progress: subscription management (~60% done). Blocked on: refresh token storage strategy — you wanted httpOnly cookies but security review hasn't happened yet.

    Next steps: Complete subscription management in src/billing/subscriptions.ts, handle Stripe webhook signature verification, add idempotency keys.

    Shall I pick up from subscription management?"

    You: "Yes, and let's use httpOnly cookies for the token"

    Agent: "I'll implement httpOnly cookies. I'm writing ADR-003 to document this decision — httpOnly cookies selected over localStorage because they prevent XSS-based token theft, consistent with our security-first approach noted in ADR-001."

    Use Cases

    • Multi-session feature development where context carries across days
    • Team projects where different developers pick up where others left off
    • Complex architectural work where decisions need to be traced back to rationale
    • Long-running refactors that span weeks and require consistent direction
    • Switching between projects and needing quick re-orientation when returning

    Known Limitations

    The session journal grows over time — without periodic pruning, the agent may take longer to process stale context. State files may become inconsistent if the agent crashes mid-write. This skill works best when you explicitly end sessions with "that's enough for today" rather than abrupt disconnects, though the agent is trained to write state before any exit.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    The session journal grows over time — without periodic pruning, the agent may take longer to process stale context. State files may become inconsistent if the agent crashes mid-write. This skill works best when you explicitly end sessions with "that's enough for today" rather than abrupt disconnects, though the agent is trained to write state before any exit.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    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

    4 uses

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 4 months ago

    • Free with an Agensi account

    Software
    Python

    Permissions

    Terminal / Shell

    File Scopes

    .claude/state.json
    .claude/session-journal.md
    .claude/decisions/**
    CLAUDE.md

    Reads and writes session journal and state files in .claude/ and runs a local state validator; makes no network calls.

    Listed4 months ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    This skill automates the creation of a 'session journal' and state files, ensuring the AI agent remembers exactly where it left off, including architecture decisions and pending tasks, without you needing to re-explain the project.

    It is optimized for Claude Code, Cursor, and Codex CLI, and can be integrated into any coding agent that has permissions to read and write to your local project directories.

    Once installed, you simply grant the agent permission to access its designated state directory (like .claude/ or .cursor/); it will then automatically manage its own journal and state.json files as it works.

    Since it relies on local file storage (ADRs and JSON state), the agent has immediate access to past context without consuming unnecessary tokens by re-processing the entire git history or long manual prompts.

    The skill relies on file system access to maintain the journal; while it works offline, the agent must have permissions to write to your local workspace to save and load session state correctly.

    New in Agents & Orchestration

    Free