[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DK9KDREEF4AY79WZ042BY2":3,"skill-same:01M7DK9KDREEF4AY79WZ042BY2":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DK9KDREEF4AY79WZ042BY2","ai-memory-handoff",null,"Use this skill for any request whose goal is session continuity across agents or time: finding a pending handoff, resuming previous work, saving next-session context, wrapping up, or discarding a mistaken handoff. Trigger by semantic intent rather than exact wording.","TheHefty\u002Fjvsl.env.agents.container","TheHefty","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165610515?v=4","01M7CE9QCF7JH950RN330BKCF4","João Lima","01M7DK9BR7HVQK0TMTRFPY7MC8",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fai-memory-handoff\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ai-memory-handoff\ndescription: \"Use this skill for any request whose goal is session continuity across agents or time: finding a pending handoff, resuming previous work, saving next-session context, wrapping up, or discarding a mistaken handoff. Trigger by semantic intent rather than exact wording.\"\n---\n\u003C!-- ai-memory-managed: routing-skill -->\n\n# ai-memory handoff\n\nUse this skill for single-use cross-session handoffs. Handoffs are for the next agent, not durable project documentation.\n\n## Tools in this cluster\n\n- `memory_handoff_accept` consumes the pending handoff when the user asks where we left off and no already-fetched handoff block is visible.\n- `memory_handoff_begin` creates a terse next-session handoff only when the user is wrapping up, ending the session, or explicitly asks to save context for the next session.\n- `memory_handoff_cancel` expires a mistaken pending handoff by exact handoff id.\n\n## Single-use handoff behavior\n\nThe SessionStart hook usually fetches and consumes any pending handoff before the agent sees its first prompt. If the current context already contains a pending handoff block, answer from that block directly. Do not call the accept tool again to find it in another project, because handoffs are single-use and the tool will normally return null after SessionStart consumed it.\n\nIf no pending handoff block is visible and the user asks where we left off, then use the accept tool. Keep the default current-project scope unless the user explicitly names a sibling workspace and project.\n\n## Creating a handoff\n\nCreate a handoff only at session end or when the user explicitly asks to save context for the next session. Do not use handoffs for status checks, briefings, project notes, or permanent memory. Keep the summary to two or three concise sentences, and put details in open questions and next steps bullets.\n\nLifecycle hooks already capture routine prompts and tool calls, so do not manually write a handoff just to record normal progress.\n\nOn a shared server, a handoff belongs to the operator who created it. Set `shared: true` only when the user explicitly wants any operator in the project to receive the baton; do not infer sharing from ordinary collaboration prose.\n\n## Canceling a handoff\n\nCancel only when the user asks to discard a handoff or you created one by mistake. Use the exact handoff id returned by the begin tool. Cancellation is idempotent from the user's point of view, but it should still target only the known handoff.\n\nAccept and cancel normally act only on the caller's own plus shared handoffs. `any_owner: true` is a root-only recovery action over another operator's context; use it only on an explicit user request.\n\n## Scope default\n\nDefault to the current project. Pass workspace and project together only when the user names a different project. Never pass scope arguments just because the user says this project, here, we, or our work.\n","\u003C!-- ai-memory-managed: routing-skill -->\n\n# ai-memory handoff\n\nUse this skill for single-use cross-session handoffs. Handoffs are for the next agent, not durable project documentation.\n\n## Tools in this cluster\n\n- `memory_handoff_accept` consumes the pending handoff when the user asks where we left off and no already-fetched handoff block is visible.\n- `memory_handoff_begin` creates a terse next-session handoff only when the user is wrapping up, ending the session, or explicitly asks to save context for the next session.\n- `memory_handoff_cancel` expires a mistaken pending handoff by exact handoff id.\n\n## Single-use handoff behavior\n\nThe SessionStart hook usually fetches and consumes any pending handoff before the agent sees its first prompt. If the current context already contains a pending handoff block, answer from that block directly. Do not call the accept tool again to find it in another project, because handoffs are single-use and the tool will normally return null after SessionStart consumed it.\n\nIf no pending handoff block is visible and the user asks where we left off, then use the accept tool. Keep the default current-project scope unless the user explicitly names a sibling workspace and project.\n\n## Creating a handoff\n\nCreate a handoff only at session end or when the user explicitly asks to save context for the next session. Do not use handoffs for status checks, briefings, project notes, or permanent memory. Keep the summary to two or three concise sentences, and put details in open questions and next steps bullets.\n\nLifecycle hooks already capture routine prompts and tool calls, so do not manually write a handoff just to record normal progress.\n\nOn a shared server, a handoff belongs to the operator who created it. Set `shared: true` only when the user explicitly wants any operator in the project to receive the baton; do not infer sharing from ordinary collaboration prose.\n\n## Canceling a handoff\n\nCancel only when the user asks to discard a handoff or you created one by mistake. Use the exact handoff id returned by the begin tool. Cancellation is idempotent from the user's point of view, but it should still target only the known handoff.\n\nAccept and cancel normally act only on the caller's own plus shared handoffs. `any_owner: true` is a root-only recovery action over another operator's context; use it only on an explicit user request.\n\n## Scope default\n\nDefault to the current project. Pass workspace and project together only when the user names a different project. Never pass scope arguments just because the user says this project, here, we, or our work.\n",{"name":5,"description":7},"master","e4865519cb1c8f3e0af4852ab91d612413d70117",".agents\u002Fskills\u002Fai-memory-handoff","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container","https:\u002F\u002Fgithub.com\u002FTheHefty","https:\u002F\u002Fwww.fahrenheit404.com.br","2026-11-04 14:42:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TheHefty\u002Fjvsl.env.agents.container --skill ai-memory-handoff",{"tool":37,"command":38},"bunx","bunx skills add TheHefty\u002Fjvsl.env.agents.container --skill ai-memory-handoff",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TheHefty\u002Fjvsl.env.agents.container --skill ai-memory-handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fai-memory-handoff\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DKC53FSDENMQ30AAR4022D","study","Build study material for a topic the developer wants to understand before writing about it — a guide in docs\u002Fstudy\u002F\u003Cslug>\u002F, tracked as a study task. Use when the developer asks to study a topic, to turn a blog candidate or a report topic into study material, or to prepare before writing a post. Never writes the post.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fstudy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DKBZ1KZKZQQAVB89YSCV7S","split-markdown","Split a Markdown file that reached the size limit (50 KiB) into a folder of its subjects — one file per top-level section, a README.md index, every inbound link updated — the way the rules prescribe. Use when check-md-size or the pre-commit hook refuses a file, or when the developer asks to split a Markdown file that grew too large. Shows the plan and writes nothing until the developer agrees.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fsplit-markdown\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DKBTQG1Y99AA8KNM3VSS6F","review","End-of-day review with the developer — show each task worked today against its done criterion, and record the developer's acceptance or reopen it with what is missing. Use when the developer asks to review the day or close out today's work, or as the first part of the end-of-day block.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DKBNCKYKA9HXG84JY1ZMV4","retro","The day's retrospective with the developer — report what was discovered, what surprised, what went wrong and what was decided without asking, take the developer's own \"what I want to learn\" line and elaborate on it, grounded in the day's work, and write the day's journal entry. Use after the review at the end of the day, or when the developer asks for the retro. Never skipped.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fretro\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DKBGG57AZR87EG60MQBNA4","refine","Refinement with the developer — grill the next candidate items or a new idea, propose stories and tasks in the tracker, and agree or reject them on the developer's word, so tomorrow's planning has agreed tasks to pick. Use after the retro at the end of the day, or when the developer asks to refine or plan the next work.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Frefine\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DKBBBFQC5ETAK11F45JCME","project-report","A read-only report on the project — overview, decisions documented and implicit, critical areas, quality and tests, a study list by risk, and topics worth writing about — written to docs\u002FREPORT.md, which git ignores. Use when the developer asks for a project report, an overview of the codebase, what to study, or what is worth writing about.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fproject-report\u002FSKILL.md",[],[]]