Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Session Handover: Pick Up Where You Left Off

    1

    Use when you stop mid-task or hand work to someone else. Writes a handover note with the current state, what is already verified, and the first step to resume.

    Free

    Security scanned
    Session Handover: Pick Up Where You Left Off

    Session Handover: Pick Up Where You Left Off

    Example session with this skill installed

    I'm heading out. Summarize the state of the API auth refactor based on the last three hours of logs. Mention the failing JWT test and the backup I made of the old handler.

    • Read your context and instructions
    • Compiled the session handover

    I have prepared the handover document for the API auth refactor.

    Project Handover: API Auth Refactor

    Goal and current state

    • Refactor legacy auth handler to support JWT: Paused
    • Outcome: Partial migration complete; integration tests failing.

    Finished items

    • JWT Helper Module: Successfully implemented. Evidence in src/utils/jwt.ts (v1.2).
    • Env Variable Config: RSA keys added to .env.local. Evidence in local environment (v1.0).
    • Middleware Scaffolding: Not provided.

    Remaining items

    1. Fix signature verification logic in authMiddleware.ts.
    2. Update login.ts controller to use new helper.
    3. (Waiting) Await frontend team confirmation on header key name.

    First action
    Fix authMiddleware.ts signature mismatch. Completion signal: npm test tests/auth.test.ts returns 0 errors.

    Changes and Backups

    • Object: src/middleware/legacyAuth.ts
    • Backup Location: /tmp/legacyAuth.ts.bak

    Restore Trigger: Run cp /tmp/legacyAuth.ts.bak src/middleware/legacyAuth.ts if JWT validation latency exceeds 200ms.

    Next steps

    • Verify the backup file exists in the /tmp directory.
    • Review the failing test logs in tests/auth.test.ts to identify the specific claim mismatch.

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

    About this skill

    Context loss and fragmented task tracking kill developer velocity during context switching. This skill generates a high-density handover document that allows a new agent or developer to resume work without re-reading entire chat histories or logs.

    What it does

    • Goal tracking provides a clear status of current objectives as done, paused, or cancelled.
    • Evidence mapping links finished items to specific versions and storage locations.
    • Dependency ordering sequences remaining tasks so the next person works on independent items first.
    • Immediate action identification defines the exact verb and completion signal for the very next step.
    • State recovery tracks object changes, backup locations, and restore triggers for safety.

    How it works

    1. Material review where the agent scans existing logs, code, and status updates for the current project state.
    2. Drafting the resume document using the five-point structure defined in the skill instructions.
    3. Validation against required boundaries to ensure cancelled items stay closed and unknown side effects aren't re-executed.
    4. Final delivery of the handover document to the console or a specified submission tool.

    Frameworks & tools

    This skill is platform agnostic and works with any text-based project environment. It specifically manages state transitions for agents using file-system backups and versioned deliverables.

    Why this beats prompting it yourself

    Generic summaries often miss critical technical details like restore triggers or version-specific evidence gaps. This skill enforces strict logic for "unknown" states to prevent double-spending or duplicate API calls during handoffs.

    Use cases

    • Shift handovers when passing a complex debugging task to a teammate or a second agent.
    • Context pausing when stopping work on a feature branch to address a production hotfix.
    • Outcome auditing to document exactly which versions of a deliverable were verified and where they are stored.

    Known limitations

    Does not perform the actual business tasks or fix broken code. Requires existing logs or material to generate the report.

    Does not execute tasks; only documents state. Requires existing context or logs to function. Cannot invent missing backup locations or success records.

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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed7 days ago
    Updated6 days ago

    What's inside

    Frequently Asked Questions

    The skill creates a high-density "Resume Document" featuring goal tracking, evidence mapping, dependency ordering, and specific state recovery triggers to prevent context loss during handovers.

    This skill is platform-agnostic and designed to work with any LLM-based agent that has access to project logs, file systems, or chat histories.

    No, this skill is a documentation and state-tracking engine; it analyzes existing logs and code to generate the report but does not execute business logic or fix bugs itself.

    The skill identifies 'unknown' states and side effects, ensuring that the next agent doesn't accidentally trigger duplicate API calls or re-process tasks that were already completed.

    You receive the specialized logic for the five-point handover structure, including the validation framework and state recovery identification protocols.

    It is ideal for shift changes between developers, pausing long-term feature work for urgent hotfixes, and creating verifiable outcome audits for project stakeholders.

    New in Agents & Orchestration