Lean Transfer

    1

    Create a private, source-backed handoff note with session state, evidence, decisions, open questions, and next actions.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Lean Transfer

    Example session with this skill installed

    Prepare a handoff for this session. We’re migrating the billing webhook worker from a single process to a queue-backed worker. The event schema is finalized in docs/events.md; the retry policy is still undecided. The integration test fixture is at tests/fixtures/invoice-paid.json. We agreed to keep the existing endpoint during migration. Write the private handoff file and report its path. Don’t invent progress or include secrets.

    • Read your context and instructions
    • Compiled the lean transfer

    Handoff written to: /tmp/handoff-20250308-1612.md

    
    # Session handoff
    
    ## Session log path
    `/workspace/project/.logs/session-20250308.jsonl`
    
    ## Scope
    Migrate the billing webhook worker from a single process to a queue-backed worker.
    
    ## Status
    The event schema is finalized. The retry policy remains undecided. The existing webhook endpoint will stay available during migration.
    
    ## Evidence
    - Event schema: `docs/events.md` (provided as finalized in the session).
    - Integration test fixture: `tests/fixtures/invoice-paid.json`.
    - No deployment or queue implementation was reported as complete.
    
    ## Decisions
    - Keep the existing endpoint during migration.
    
    ## Open questions
    - What retry schedule and maximum attempt count should the queue use?
    - What is the cutover and rollback procedure?
    
    ## Next actions
    1. Decide and document the retry policy.
    2. Add a queue-worker test using `tests/fixtures/invoice-paid.json`.
    3. Define cutover and rollback checks before deployment.
    

    Next steps

    Start the next session by reviewing the two referenced files and resolving the retry policy before changing worker behavior.

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

    About this skill

    Lean Transfer preserves selected session context in a timestamped Markdown handoff file under $TMPDIR. The note records the session log path, scope, current status, verified evidence and artifact paths, decisions, open questions, and immediate next actions. It distinguishes evidence from assumptions, cites sources, and redacts secrets and personal information. The skill reports the resulting absolute path so another session can continue from the handoff.

    Use it when ending a session that has produced decisions, research, or artifacts another person or agent needs to pick up.

    Requires filesystem write permissions. Does not auto-inject context into new sessions; the generated path must be manually provided to the next agent.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    lean transfer prevents 'context drift' and token waste by distilling your current session into a structured, machine-readable Markdown snapshot that highlights only what matters—like verified facts and blockers—rather than re-reading thousands of lines of chat history.

    This skill is environment-agnostic; as long as your agent has filesystem access to a terminal or IDE (like VS Code, Cursor, or Windsurf), it can execute the state export regardless of the underlying LLM or framework.

    Safety is a priority; the skill includes an automated security scrubbing layer that detects and redacts common patterns for secrets, keys, and PII before the handoff file is ever written to your local disk.

    The handoff file is saved to your system's temporary directory ($TMPDIR) with restricted mode-600 permissions, meaning it is only readable by your user account for maximum local security.

    You receive the complete skill definition, the structured Markdown schema for state exports, and a guide on how to point a new agent to the generated file for an instant resume.

    Currently, the user must provide the generated file path to the next agent, ensuring you have full control over when and where your technical context is shared between sessions.

    New in Agents & Orchestration