Session Relay
Create a Markdown handoff so another AI coding agent or a fresh session can resume work without re-deriving the context.
Free
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsSession Relay
Example session with this skill installed
The backend Tasks API is done, and my context window is nearly full. Please write a handoff for the frontend agent. The routes are in server/routes/tasks.ts, the Task type is in server/types/task.ts, and the frontend is in web/. All routes require a Bearer token. GET /api/tasks returns { "tasks": Task[] }. POST /api/tasks accepts { "title": string } and returns a Task. PATCH /api/tasks/:id accepts { "status": "todo" | "done" } and returns a Task. A Task has id, title, and status; status is todo or done. Errors use { "error": { "code": string, "message": string } }; unauthenticated requests return 401 and invalid input returns 422. The backend route tests pass. The frontend has not been started.
- Read your context and instructions
- Compiled the session relay
Tasks API to frontend handoff
Output: docs/tasks-api-frontend-handoff.md
Agenda
The backend Tasks API is complete. The next agent should connect the frontend in web/ to it without re-deriving the route and response shapes.
Files that matter
| File | Purpose |
|---|---|
server/routes/tasks.ts | Tasks API routes. |
server/types/task.ts | Task data shape. |
web/ | Frontend app; integration has not started. |
API contract
| Request | Body | Success response |
|---|---|---|
GET /api/tasks | None | { "tasks": Task[] } |
POST /api/tasks | { "title": string } | A Task |
PATCH /api/tasks/:id | { "status": "todo" | "done" } | A Task |
Task contains id, title, and status. Every route requires a Bearer token. Errors have the shape { "error": { "code": string, "message": string } }. Expect 401 when the token is missing or invalid and 422 for invalid input.
Current state
Backend route tests pass, as reported in this session. No frontend API client or task UI has been started. The exact test command was not provided, so rerun the relevant backend tests if you need to verify that result.
Open questions
- Where does
web/obtain the Bearer token? Inspect its existing auth flow before writing the API client.
Next steps
- Inspect the existing patterns in
web/, then add a typed Tasks API client using the contract above. - Connect the task list, create action, and status update to their corresponding routes.
- Send the Bearer token with each request. Show a useful state for 401 and display the validation message from 422 responses.
- Test the three frontend flows against the backend and record any contract mismatch before changing either side.
Connects securely to your tools. The creator never sees your data.
About this skill
Session Relay distills an AI coding session into a concise Markdown document when the session is near its context limit. It records the goal, relevant files, changes, decisions, current state, open questions, and actionable next steps. The output is written to docs/<slug>-handoff.md for another agent or session to pick up.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 1 day ago
- Free to download with an account
Requires