[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EC59F2XK6DP0X8ZBJ7WAS3":3,"skill-same:01M7EC59F2XK6DP0X8ZBJ7WAS3":54},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":49},"01M7EC59F2XK6DP0X8ZBJ7WAS3","handoff",null,"Compact the current conversation into a handoff document for another agent to pick up.","syedmehedihussain\u002Fcherry","syedmehedihussain","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183754033?v=4","01M7EC34EA312J2XV37SD5C840","Syed Mehedi Hussain","01M7EC34EZR59ARY7C75C41EKJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fhandoff\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fhandoff\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: handoff\ndescription: Compact the current conversation into a handoff document for another agent to pick up.\nargument-hint: \"What will the next session be used for?\"\ndisable-model-invocation: true\n---\n\nWrite a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS (`$TMPDIR`, else `\u002Ftmp`; `%TEMP%` on Windows) - not the current workspace.\n\nInclude a \"suggested skills\" section in the document, naming which skills the next agent should call the Skill tool for.\n\nDo not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.\n\nRedact any sensitive information, such as API keys, passwords, or personally identifiable information.\n\nIf the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.\n","Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS (`$TMPDIR`, else `\u002Ftmp`; `%TEMP%` on Windows) - not the current workspace.\n\nInclude a \"suggested skills\" section in the document, naming which skills the next agent should call the Skill tool for.\n\nDo not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.\n\nRedact any sensitive information, such as API keys, passwords, or personally identifiable information.\n\nIf the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.\n",{"name":5,"description":7,"argument-hint":25,"disable-model-invocation":26},"What will the next session be used for?",true,"main","adb38ff1e06b1bb57c84131717dd3d9c01292a8b","packages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fhandoff",0,"https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry","https:\u002F\u002Fsyedmehedihussain.github.io\u002Fcherry\u002F","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain","https:\u002F\u002Fsyedmehedihussain.codes\u002F","What should I say?","2026-11-10 02:42:31",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":26},[39,42,45],{"tool":40,"command":41},"npx","npx skills add syedmehedihussain\u002Fcherry --skill handoff",{"tool":43,"command":44},"bunx","bunx skills add syedmehedihussain\u002Fcherry --skill handoff",{"tool":46,"command":47},"pnpm","pnpm dlx skills add syedmehedihussain\u002Fcherry --skill handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fhandoff\u002FSKILL.md",[50],{"path":51,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":16},"LICENSE","许可证",1068,[55,63,71,79,87,95],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":20},"01M7ECBMEN6N02N2NGHMYTJTY1","verification-loop","Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fverification-loop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":20},"01M7ECBFBZ3GJEWJJHKRPCYX8J","e2e-testing","Playwright E2E testing patterns, Page Object Model, configuration, CI\u002FCD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fe2e-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fe2e-testing\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":20},"01M7ECB8WD04GN1SF0J7XM0252","browser-qa","Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP \u002F DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fbrowser-qa\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fbrowser-qa\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":20},"01M7ECB2QHYKHYT9EJV089FVT4","ai-regression-testing","Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fai-regression-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fai-regression-testing\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":20},"01M7ECAXS1W69TNH9MV1J1WHM2","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fstory-lifecycle\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fstory-lifecycle\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M7ECAQVHTTS6M1T62XYAP9NP","intent-driven-development","Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security\u002Fdata\u002Fmigration\u002Fintegration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fintent-driven-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fintent-driven-development\u002FSKILL.md",[],[]]