Home / jellydn / my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/handoffs/SKILL.md · GitHub

handoffs skillA

Name: handoffs
Author: jellydn

handoffs is agent-read markdown (skill) from jellydn/my-ai-tools: Create handoff plans for continuing work across sessions.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# Session Handoff Plan

Creates a detailed handoff plan of the conversation for continuing the work in a new session.

The user specified purpose:

<purpose>$ARGUMENTS</purpose>

You are creating a summary specifically so that it can be continued by another agent. For this to work you MUST have a purpose. If no specified purpose was provided in the `<purpose>...</purpose>` tag you must STOP IMMEDIATELY and ask the user what the purpose is.

Do not continue before asking for the purpose as you will otherwise not understand the instructions and do not assume a purpose!

## Goal

Create a detailed summary of the conversation so far, paying close attention to the user's explicit purpose for the next steps.
This handoff plan should be thorough in capturing technical details, code patterns, and architectural decisions that will be essential for continuing development work without losing context.

## Process

Before providing your final plan, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points:

1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
…

Read the whole file at its exact version.

How to install

Latest version

mdr add jellydn/my-ai-tools/handoffs@git:20260814.d1987f5

Exact content

mdr add jellydn/my-ai-tools/handoffs@sha256:8becc6a93facf082

Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.

Badge

[![mdr](https://markdownregistry.com/badge/art_fg75bbvvvgl3pbfb.svg)](https://markdownregistry.com/a/art_fg75bbvvvgl3pbfb)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260814.d1987f5 latest	2026-08-14	d1987f5	5,333 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Deterministic, no model, same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5333 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

jellydn/my-ai-tools · 121 stars · license MIT · pushed 2026-09-24 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_fg75bbvvvgl3pbfb
GET https://markdownregistry.com/api/v1/resolve?ref=jellydn/my-ai-tools/handoffs
GET https://markdownregistry.com/api/v1/blob/8becc6a93facf08213ad321a519d03a02b0c03ac4977d462e424c6ad2f690be3

Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

More from jellydn/my-ai-tools

AGENTS.md agents

jellydn/my-ai-tools · AGENTS.md

git:20260805.03f0789 · audit A · 121 stars

AGENTS.md@configs/amp agents

jellydn/my-ai-tools · configs/amp/AGENTS.md