[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C4AMAVP10HGG0MDXSFWXER":3,"skill-same:01M7C4AMAVP10HGG0MDXSFWXER":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7C4AMAVP10HGG0MDXSFWXER","handoff",null,"Pause-and-resume system for cross-conversation continuity. Use when your AI needs the user's input to continue a task but the current conversation must end. Checked on every boot to detect pending handoffs. Triggers on conversation start (boot check) and when the AI explicitly needs to pause for input.","SillyHippy\u002Fzo-skills","SillyHippy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159052837?v=4","01M7C43A8PDYMCDPTNFYF2RSC1","01M7C43A9CBS76QPH4PPTKXX54",0,"MIT","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fhandoff\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: handoff\ndescription: >\n  Pause-and-resume system for cross-conversation continuity. Use when your AI\n  needs the user's input to continue a task but the current conversation must end.\n  Checked on every boot to detect pending handoffs. Triggers on conversation start\n  (boot check) and when the AI explicitly needs to pause for input.\ncompatibility: Created for Zo Computer\nmetadata:\n  author: skeletorjs\n  category: Community\n---\n\n# Handoff\n\nEnables your AI to pause work, ask you a question, and resume in a future conversation with your answer, regardless of which channel you respond through (SMS, email, new chat thread).\n\n## Setup\n\n1. Install this skill to `Skills\u002Fhandoff\u002F`\n2. Add to your boot sequence (in rules or AGENTS.md): run `python3 Skills\u002Fhandoff\u002Fscripts\u002Fhandoff.py check` at the start of every conversation\n3. Ensure `Data\u002F` directory exists in your workspace\n\n## State File\n\nSingle file: `\u002Fhome\u002Fworkspace\u002FData\u002Fhandoff.json`\n\nOnly one handoff exists at a time. If a handoff file exists, there is unfinished business.\n\n## Boot Check (Every Conversation)\n\nAt the start of every conversation, after loading your persona\u002Fprofile context:\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py check\n```\n\n**If no handoff exists**: Output says \"No pending handoff.\" Continue normally.\n\n**If a handoff exists**: Output includes the full handoff context. Do the following:\n\n1. Read the handoff context carefully\n2. Tell the user: \"I have a pending handoff from a previous session\" and summarize what was in progress and what was asked\n3. If the current message appears to be a response to the handoff question, resume the work using their input, then clear the handoff\n4. If the current message is about something else entirely, mention the pending handoff briefly and ask if they want to address it or shelve it\n5. After the handoff is resolved, clear it:\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py clear\n```\n\n## Creating a Handoff (When Pausing)\n\nWhen you need the user's input to continue and the current session needs to end:\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py save \\\n  --task \"Brief description of what you're working on\" \\\n  --context \"Detailed context: what's been done, where files are, what state things are in\" \\\n  --question \"The specific question or decision you need from the user\" \\\n  --resume \"Instructions for your future self on how to resume once you have the answer\"\n```\n\nAfter saving, notify the user. Choose based on urgency:\n\n- **SMS** (default, most likely to be seen quickly): `send_sms_to_user`\n- **Email** (for longer context): `send_email_to_user`\n- **Both** (urgent + detailed): send both\n\nThe notification should include:\n- What you were working on (1 line)\n- What you need from the user (the question)\n- \"Reply anywhere and I'll pick it up next conversation\"\n\n## CLI Reference\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py \u003Ccommand> [options]\n```\n\n| Command | Purpose |\n|---------|---------|\n| check | Check for pending handoff. Returns handoff context or \"no pending handoff\" |\n| save | Create a new handoff (--task, --context, --question, --resume) |\n| clear | Remove the pending handoff after it's been resolved |\n| show | Display the full handoff file contents (same as check but always verbose) |\n\n## Rules\n\n- Never create a handoff for something you can figure out yourself. Search first, check memory, read files.\n- Never have more than one handoff at a time. If one exists and you need to create another, resolve or replace the existing one.\n- Always notify the user after creating a handoff. Don't just silently save it.\n- Always clear the handoff after resolving it. Don't leave stale handoffs.\n- The handoff file is your continuity mechanism. Write it like you're briefing a colleague who has zero context.\n","# Handoff\n\nEnables your AI to pause work, ask you a question, and resume in a future conversation with your answer, regardless of which channel you respond through (SMS, email, new chat thread).\n\n## Setup\n\n1. Install this skill to `Skills\u002Fhandoff\u002F`\n2. Add to your boot sequence (in rules or AGENTS.md): run `python3 Skills\u002Fhandoff\u002Fscripts\u002Fhandoff.py check` at the start of every conversation\n3. Ensure `Data\u002F` directory exists in your workspace\n\n## State File\n\nSingle file: `\u002Fhome\u002Fworkspace\u002FData\u002Fhandoff.json`\n\nOnly one handoff exists at a time. If a handoff file exists, there is unfinished business.\n\n## Boot Check (Every Conversation)\n\nAt the start of every conversation, after loading your persona\u002Fprofile context:\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py check\n```\n\n**If no handoff exists**: Output says \"No pending handoff.\" Continue normally.\n\n**If a handoff exists**: Output includes the full handoff context. Do the following:\n\n1. Read the handoff context carefully\n2. Tell the user: \"I have a pending handoff from a previous session\" and summarize what was in progress and what was asked\n3. If the current message appears to be a response to the handoff question, resume the work using their input, then clear the handoff\n4. If the current message is about something else entirely, mention the pending handoff briefly and ask if they want to address it or shelve it\n5. After the handoff is resolved, clear it:\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py clear\n```\n\n## Creating a Handoff (When Pausing)\n\nWhen you need the user's input to continue and the current session needs to end:\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py save \\\n  --task \"Brief description of what you're working on\" \\\n  --context \"Detailed context: what's been done, where files are, what state things are in\" \\\n  --question \"The specific question or decision you need from the user\" \\\n  --resume \"Instructions for your future self on how to resume once you have the answer\"\n```\n\nAfter saving, notify the user. Choose based on urgency:\n\n- **SMS** (default, most likely to be seen quickly): `send_sms_to_user`\n- **Email** (for longer context): `send_email_to_user`\n- **Both** (urgent + detailed): send both\n\nThe notification should include:\n- What you were working on (1 line)\n- What you need from the user (the question)\n- \"Reply anywhere and I'll pick it up next conversation\"\n\n## CLI Reference\n\n```bash\npython3 \u002Fhome\u002Fworkspace\u002FSkills\u002Fhandoff\u002Fscripts\u002Fhandoff.py \u003Ccommand> [options]\n```\n\n| Command | Purpose |\n|---------|---------|\n| check | Check for pending handoff. Returns handoff context or \"no pending handoff\" |\n| save | Create a new handoff (--task, --context, --question, --resume) |\n| clear | Remove the pending handoff after it's been resolved |\n| show | Display the full handoff file contents (same as check but always verbose) |\n\n## Rules\n\n- Never create a handoff for something you can figure out yourself. Search first, check memory, read files.\n- Never have more than one handoff at a time. If one exists and you need to create another, resolve or replace the existing one.\n- Always notify the user after creating a handoff. Don't just silently save it.\n- Always clear the handoff after resolving it. Don't leave stale handoffs.\n- The handoff file is your continuity mechanism. Write it like you're briefing a colleague who has zero context.\n",{"name":5,"metadata":23,"description":26,"compatibility":27},{"author":24,"category":25},"skeletorjs","Community","Pause-and-resume system for cross-conversation continuity. Use when your AI needs the user's input to continue a task but the current conversation must end. Checked on every boot to detect pending handoffs. Triggers on conversation start (boot check) and when the AI explicitly needs to pause for input.\n","Created for Zo Computer","main","3641543f81ae80504027d6b012e0dadce4e2de40","skills\u002Fhandoff","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills","https:\u002F\u002Fgithub.com\u002FSillyHippy","2026-09-18 11:42:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SillyHippy\u002Fzo-skills --skill handoff",{"tool":40,"command":41},"bunx","bunx skills add SillyHippy\u002Fzo-skills --skill handoff",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SillyHippy\u002Fzo-skills --skill handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fhandoff\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"DISPLAY.json","REFERENCE","参考文档",97,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fhandoff\u002FDISPLAY.json",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"scripts\u002Fhandoff.py","SCRIPT","脚本",4122,"https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fhandoff\u002Fscripts\u002Fhandoff.py",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7C4RK2ZCHPKQT393RVSC6ER","zopack","Export and import zo.space route setups as shareable .zopack.md files. Use when the user wants to package their zo.space routes for sharing, or when they receive a .zopack.md file to deploy. Triggers on \"export my zo.space\", \"create a zopack\", \"import this zopack\", or any mention of .zopack.md files.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzopack\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7C4REH5EJ22X3C1SF88X6KQ","zoho-mail-inbox","Full inbox management for Zoho Mail (info@justlegalsolutions.org) — list unread, mark all as read, delete by sender\u002Fkeyword, search, send from aliases, list folders. Fully self-contained — zero setup needed.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-mail-inbox\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7C4RAJF1N9R8ZRT25GMHFBF","weekly-meeting-reminder","Get an email every Sunday evening listing your meetings for the coming week.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-weekly-meeting-reminder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7C4R65Q9T6TPBRFQPWJSW4Z","twitter","Let Zo use your X (Twitter) account","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-twitter\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7C4R358YM59EZRM3SW763VK","zo-tools","Internal process tools for Zo and Hermes — local search, document processing, OCR, and embeddings. All services run on localhost, zero HTTP slots consumed.","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-tools\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7C4R0J4C3RQWKZ5W5W3CZ3X","ssh-setup","Sets up secure remote access to your Zo Computer so you can connect from anywhere","https:\u002F\u002Fgithub.com\u002FSillyHippy\u002Fzo-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzo-ssh-setup\u002FSKILL.md",[],[]]