Run any Skill in Manus with one click

handoff

Stars2

Forks1

UpdatedMay 15, 2026 at 07:34

Compact the current conversation into a handoff document for another agent session to pick up. Use when the user says "handoff", "hand off", "save context", "write a handoff", "summarize for next session", or wants to capture the current session state so a fresh agent can continue the work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rafalschmidt97

rafalschmidt97/opencode-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	handoff
description	Compact the current conversation into a handoff document for another agent session to pick up. Use when the user says "handoff", "hand off", "save context", "write a handoff", "summarize for next session", or wants to capture the current session state so a fresh agent can continue the work.
argument-hint	What will the next session be used for?
metadata	{"version":"1.0"}
allowed-tools	Bash(mktemp:*) Read Write

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to a path produced by mktemp -t handoff-XXXXXX.md (read the file before you write to it).

Suggest the skills to be used, if any, by the next session.

Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

More from this repository

same repository

slack-dm-sender

rafalschmidt97/opencode-skills

Send Slack direct messages through the web UI using headed agent-browser, with the human logged in interactively. Supports a single person or batching the same message to many people one by one without creating a group chat. USE FOR: send a Slack DM, send a message to X on DM, message these people on Slack, DM this update to a list of people, send the same Slack message to multiple recipients, batch Slack DMs, team communication update, stakeholder update, notify people individually on Slack. DO NOT USE FOR: Slack API, Slack bots, webhooks, desktop Slack automation, channel announcements, group chats, emails, calendar invites.

2026-06-052

debrief

rafalschmidt97/opencode-skills

Generates a personalized 1:1 prep/debrief by reading a person's vault profile, recent call notes, GitHub activity (PRs, commits, issues), and project board status. Produces an agenda with context, talking points, and follow-ups. Use when the user says 'prepare my 1:1', 'debrief for [name]', '1:1 prep', 'what should I discuss with [name]', 'catch me up on [name]', 'prep for my meeting with [name]', or mentions preparing for a direct report conversation. Do NOT use for delivering feedback (use feedback skill) or processing meeting transcripts (use read-meeting-notes).

2026-05-272

read-meeting-notes

rafalschmidt97/opencode-skills

Processes meeting transcripts from configured sources (Zoom, Teams, local files, calendar recordings). Extracts action items, decisions, and key topics, then creates structured call notes in the vault routed to the relevant person or meeting folder. Use when the user says 'process meeting notes', 'read my transcripts', 'import meeting recording', 'download zoom transcript', 'process today's meetings', 'what happened in my meetings', 'create notes from transcript', or mentions meeting recordings or transcripts. Do NOT use for 1:1 prep (use debrief) or manual note-taking.

2026-05-272

searxng-search

rafalschmidt97/opencode-skills

Search the web using a local SearXNG metasearch engine via MCP. Use this skill when the user asks to search the web, look something up online, find information on the internet, research a topic, check recent news, or when you need up-to-date information that is not in your training data. USE FOR: web search, internet lookup, finding recent information, researching topics, checking news, discovering URLs, finding documentation online, verifying facts against current sources. DO NOT USE FOR: searching the local codebase (use Grep/Glob instead), reading known URLs (use WebFetch instead), or querying internal databases.

2026-05-242

markdown-to-gdocs

rafalschmidt97/opencode-skills

Upload Markdown files as Google Docs. Use when the user asks to create, upload, publish, or push a markdown file to Google Docs/Drive. Supports creating new docs and updating existing ones. Converts Markdown to HTML then uploads with Google Drive mimeType conversion to native Google Docs. Authenticates via gcloud CLI. Supports both user credentials and ADC.

2026-05-192

crawl4ai

rafalschmidt97/opencode-skills

Crawl and extract content from web pages using Crawl4AI via MCP. Use when the user asks to crawl a website, extract content from a URL, scrape a page, get a screenshot of a site, generate a PDF from a URL, convert a webpage to markdown, extract structured data from a page, or run JavaScript on a remote page. USE FOR: web crawling, page scraping, content extraction, webpage screenshots, PDF generation, JavaScript execution on pages, converting URLs to markdown, deep crawling multiple pages. DO NOT USE FOR: web search (use searxng-search), reading a known URL when simple fetch suffices (use WebFetch), local file operations.

2026-05-152

name	handoff
description	Compact the current conversation into a handoff document for another agent session to pick up. Use when the user says "handoff", "hand off", "save context", "write a handoff", "summarize for next session", or wants to capture the current session state so a fresh agent can continue the work.
argument-hint	What will the next session be used for?
metadata	{"version":"1.0"}
allowed-tools	Bash(mktemp:*) Read Write

Suggest the skills to be used, if any, by the next session.

Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.