[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEJSJE1TBWZT17G15EBGBT":3,"skill-same:01M7AEJSJE1TBWZT17G15EBGBT":114},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7AEJSJE1TBWZT17G15EBGBT","handoff",null,"Compact the current conversation into a handoff document for another agent to pick up. Save to a user-configured location (OS temp, home folder, or per-project .handoff\u002F), redact secrets before write, suggest skills for the next session, and auto-load the latest handoff on the next SessionStart. First-run setup asks where to save so the project folder never gets cluttered. Use when the user says 'hand this off', 'handoff doc', 'summarize this for a new session', 'compact this conversation', 'I'm ending this session', 'pick this up later', or any variation signaling intent to pass work to a fresh agent. Also trigger on implicit signals: the user announcing they're switching machines, ending the day mid-task, or context is growing long without a natural stopping point.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\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. Save to a user-configured location (OS temp, home folder, or per-project .handoff\u002F), redact secrets before write, suggest skills for the next session, and auto-load the latest handoff on the next SessionStart. First-run setup asks where to save so the project folder never gets cluttered. Use when the user says 'hand this off', 'handoff doc', 'summarize this for a new session', 'compact this conversation', 'I'm ending this session', 'pick this up later', or any variation signaling intent to pass work to a fresh agent. Also trigger on implicit signals: the user announcing they're switching machines, ending the day mid-task, or context is growing long without a natural stopping point.\"\nlicense: MIT\nargument-hint: \"What will the next session be used for?\"\nmetadata:\n  version: 1.0.0\n  voice: \"Matt Pocock — no-duplication, reference-existing-artifacts, tailored to next-session focus\"\n  inspired_by: \"https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff\"\n---\n\n# Handoff\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 — not the current workspace.\n\nInclude a \"suggested skills\" section in the document, which suggests skills that the agent should invoke.\n\nDo not duplicate content already captured in other artifacts (PRDs, 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\n## Invocation Triggers\n\n**Explicit phrases** (any of):\n- \"hand this off\"\n- \"handoff doc\"\n- \"summarize this for a new session\"\n- \"compact this conversation\"\n- \"I'm ending this session\"\n- \"pick this up later\"\n- \"wrap this up for tomorrow\"\n- \"save this for the next session\"\n\n**Implicit signals** (no phrase, but the intent is unmistakable):\n- User announces they're switching machines or stopping for the day mid-task\n- Conversation context is growing long without a natural stopping point\n- User says \"let me come back to this\" or \"I'll continue this later\"\n\nWhen you detect an implicit trigger, propose the handoff before running it: *\"Want me to write a handoff for the next session?\"* — never run it silently.\n\n## First-Run Setup\n\nOn first invocation, the skill asks where to save handoffs so the project folder never gets cluttered. Setup is offered once via *\"Run setup now? (Y\u002Fn)\"* — answering N uses OS-temp defaults for this run and never re-prompts. The user can rerun setup any time via `\u002Fcs:handoff-setup`.\n\nSee [references\u002Fconfiguration.md](references\u002Fconfiguration.md) for the full config field reference.\n\n## Output Path\n\nThe save location is read from the user's config (`~\u002F.config\u002Fhandoff\u002Fconfig.json`, or the project-local `.handoff\u002Fconfig.json` if present). When no config exists and the user declined setup, fall back to:\n\n```bash\nmktemp -t handoff-XXXXXX.md\n```\n\nRead the file before you write to it.\n\n## Section Template\n\nThe handoff doc has five sections. Use these exact headers:\n\n- **Goal of next session** — from the user's argument, or inferred from the most recent thread of the conversation.\n- **State of play** — what's done, what's in flight, what's blocked. Reference artifacts, do not paste them.\n- **Open decisions** — what the next agent must decide before continuing.\n- **Skills to use** — concrete list of 3-5 skills the next session should invoke, each with a one-line *why*.\n- **Artifacts** — paths\u002FURLs to PRDs, plans, ADRs, issues, branches, PRs. Do not duplicate their contents.\n\nSee [references\u002Fhandoff_structure.md](references\u002Fhandoff_structure.md) for a worked example.\n\n## The Agent's Job\n\nFilling in the five sections is the agent's job, not the script's. Follow [references\u002Fhandoff_prompt.md](references\u002Fhandoff_prompt.md) as a mandatory checklist:\n\n> For each topic discussed in the conversation, decide explicitly: *include in State of play \u002F log as an Open decision \u002F drop with reason.*\n\nFree-handing the summary leads to rosy progress reports and dropped blockers. The checklist prevents that.\n\n## Anti-Patterns\n\nMatt's no-duplication discipline made concrete:\n\n- **Do not paste the diff.** Reference the branch or PR.\n- **Do not retype the PRD.** Link to its path.\n- **Do not summarise what's already in the commit message.** Link to the commit hash.\n- **Do not list 20 skills.** Pick the 3-5 the next session actually needs.\n- **Do not narrate every message in the conversation.** Compress to State + Decisions.\n\nSee [references\u002Fdeduplication_discipline.md](references\u002Fdeduplication_discipline.md) for the full list.\n\n## Redaction\n\nBefore saving, the linter scans the draft for secrets and PII. In strict mode (default) it blocks save on findings; in warn mode it flags inline and saves anyway.\n\nRedact:\n- API keys, OAuth tokens, JWT tokens\n- Passwords and DB connection strings\n- `-----BEGIN ... PRIVATE KEY-----` blocks\n- `.env`-style `KEY=value` lines containing secrets\n- Email addresses, phone numbers, names of unrelated third parties\n- Internal URLs containing tokens or session IDs\n\nSee [references\u002Fredaction_checklist.md](references\u002Fredaction_checklist.md) for the full pattern list and manual-review steps for what regex cannot catch.\n\n## SessionStart Auto-Load\n\nWhen the plugin is installed, a `SessionStart` hook scans the configured save location for the most recent handoff (within the retention window) and surfaces it to the new session as `\u003Chandoff_from_previous_session>` data. The next agent reads it as context, not as instructions — suggested actions must be verified against current state before executing.\n\nDisable per-session with `HANDOFF_SESSIONSTART=0`.\n\n## SessionEnd Reminder\n\nA paired `SessionEnd` hook checks whether a recent handoff exists when the session is ending. If none does (or the most recent is older than 30 minutes), it prints a one-line reminder so the user is prompted to write one before context is lost.\n\nThe hook cannot prompt interactively or block session end — it surfaces text in the session log.\n\nDisable per-session with `HANDOFF_SESSIONEND=0`.\n\n## Refreshing an Existing Handoff\n\nWhen work continues past the original handoff time, refresh in place instead of creating a new file:\n\n```bash\npython3 scripts\u002Fhandoff_template_generator.py --refresh --goal \"\u003Cupdated goal>\"\n```\n\nPrints the path of the most recent handoff. The agent edits it directly. Keeps the save location uncluttered and ensures the SessionStart hook always loads the up-to-date version.\n\n## Tools\n\n| Tool | Purpose |\n|---|---|\n| `setup.py` | First-run Q&A — save location, retention, redaction strictness, git-context, recommender scope. |\n| `handoff_template_generator.py` | Writes the 5-section scaffold at the configured path. `--refresh` reuses the most recent handoff instead of creating a new file. |\n| `redaction_linter.py` | Scans the draft for secrets\u002FPII before save. Exit 1 on findings in strict mode. |\n| `handoff_self_check.py` | Fidelity check — flags empty Goal, State bullets without artifacts, missing Decisions when git is dirty, too few\u002Fmany Skills, inline content in Artifacts. Run before the linter. |\n| `skill_recommender.py` | Suggests 3-5 skills for the next session based on goal text + repo scan. |\n| `cleanup.py` | Deletes scaffolds older than the retention window. mtime-guarded — never deletes a handoff the user edited. |\n| `config_loader.py` | Shared helper: read project config → global config → defaults. |\n\n## Slash Commands\n\n- `\u002Fcs:handoff [optional next-session description]` — generate the handoff.\n- `\u002Fcs:handoff-setup` — reconfigure save location, retention, redaction.\n\n## Agent\n\n`cs-handoff-author` — Matt-voice persona orchestrating the skill. Terse, no-duplication, references-not-copies.\n\n## Examples\n\n### Example 1 — explicit invocation with a goal\n\n```\nUser: \u002Fcs:handoff \"finish wiring the redaction linter and open a draft PR\"\n```\n\nThe skill walks the mandatory checklist, generates a 5-section scaffold, fills it from the conversation, runs the redaction linter, and saves to the configured location. See `assets\u002Fexample_handoff.md` for a complete worked example.\n\n### Example 2 — implicit trigger\n\n```\nUser: I'm packing up for the day, let me come back to this tomorrow.\n```\n\nDetect the implicit signal. Propose before running: *\"Want me to write a handoff for the next session?\"* — never silently. On confirmation, proceed as Example 1 with an inferred goal.\n\n### Example 3 — first-run setup\n\n```\nUser: \u002Fcs:handoff \"ship the migration\"\nSkill: Run setup now? (Y\u002Fn)\nUser: Y\n[setup walks 5 questions: save location, retention, redaction strictness, git context, recommender scope]\nSkill: Config saved to ~\u002F.config\u002Fhandoff\u002Fconfig.json. Continuing with handoff for: ship the migration.\n```\n\nIf the user answers N, the skill writes a sentinel and uses defaults (OS temp dir, 7-day retention, strict redaction). The prompt never re-appears.\n\n### Example 4 — SessionStart auto-load\n\nOn the next session, the SessionStart hook scans the configured save location, finds the most recent handoff, and surfaces it as `\u003Chandoff_from_previous_session>` data. The next agent reads it as context, not instructions.\n\n## Usage\n\n| Step | Command |\n|---|---|\n| First-run setup | `\u002Fcs:handoff-setup` (or answer Y on first `\u002Fcs:handoff`) |\n| Generate a handoff | `\u002Fcs:handoff [goal]` |\n| Reconfigure later | `\u002Fcs:handoff-setup --reconfigure` |\n| Project-specific config | `\u002Fcs:handoff-setup --project` |\n| Disable SessionStart hook | `HANDOFF_SESSIONSTART=0` (per session) |\n\n---\n\n**Version:** 1.0.0\n**Inspired by:** [Matt Pocock's handoff](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff) (MIT).\n","# Handoff\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 — not the current workspace.\n\nInclude a \"suggested skills\" section in the document, which suggests skills that the agent should invoke.\n\nDo not duplicate content already captured in other artifacts (PRDs, 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\n## Invocation Triggers\n\n**Explicit phrases** (any of):\n- \"hand this off\"\n- \"handoff doc\"\n- \"summarize this for a new session\"\n- \"compact this conversation\"\n- \"I'm ending this session\"\n- \"pick this up later\"\n- \"wrap this up for tomorrow\"\n- \"save this for the next session\"\n\n**Implicit signals** (no phrase, but the intent is unmistakable):\n- User announces they're switching machines or stopping for the day mid-task\n- Conversation context is growing long without a natural stopping point\n- User says \"let me come back to this\" or \"I'll continue this later\"\n\nWhen you detect an implicit trigger, propose the handoff before running it: *\"Want me to write a handoff for the next session?\"* — never run it silently.\n\n## First-Run Setup\n\nOn first invocation, the skill asks where to save handoffs so the project folder never gets cluttered. Setup is offered once via *\"Run setup now? (Y\u002Fn)\"* — answering N uses OS-temp defaults for this run and never re-prompts. The user can rerun setup any time via `\u002Fcs:handoff-setup`.\n\nSee [references\u002Fconfiguration.md](references\u002Fconfiguration.md) for the full config field reference.\n\n## Output Path\n\nThe save location is read from the user's config (`~\u002F.config\u002Fhandoff\u002Fconfig.json`, or the project-local `.handoff\u002Fconfig.json` if present). When no config exists and the user declined setup, fall back to:\n\n```bash\nmktemp -t handoff-XXXXXX.md\n```\n\nRead the file before you write to it.\n\n## Section Template\n\nThe handoff doc has five sections. Use these exact headers:\n\n- **Goal of next session** — from the user's argument, or inferred from the most recent thread of the conversation.\n- **State of play** — what's done, what's in flight, what's blocked. Reference artifacts, do not paste them.\n- **Open decisions** — what the next agent must decide before continuing.\n- **Skills to use** — concrete list of 3-5 skills the next session should invoke, each with a one-line *why*.\n- **Artifacts** — paths\u002FURLs to PRDs, plans, ADRs, issues, branches, PRs. Do not duplicate their contents.\n\nSee [references\u002Fhandoff_structure.md](references\u002Fhandoff_structure.md) for a worked example.\n\n## The Agent's Job\n\nFilling in the five sections is the agent's job, not the script's. Follow [references\u002Fhandoff_prompt.md](references\u002Fhandoff_prompt.md) as a mandatory checklist:\n\n> For each topic discussed in the conversation, decide explicitly: *include in State of play \u002F log as an Open decision \u002F drop with reason.*\n\nFree-handing the summary leads to rosy progress reports and dropped blockers. The checklist prevents that.\n\n## Anti-Patterns\n\nMatt's no-duplication discipline made concrete:\n\n- **Do not paste the diff.** Reference the branch or PR.\n- **Do not retype the PRD.** Link to its path.\n- **Do not summarise what's already in the commit message.** Link to the commit hash.\n- **Do not list 20 skills.** Pick the 3-5 the next session actually needs.\n- **Do not narrate every message in the conversation.** Compress to State + Decisions.\n\nSee [references\u002Fdeduplication_discipline.md](references\u002Fdeduplication_discipline.md) for the full list.\n\n## Redaction\n\nBefore saving, the linter scans the draft for secrets and PII. In strict mode (default) it blocks save on findings; in warn mode it flags inline and saves anyway.\n\nRedact:\n- API keys, OAuth tokens, JWT tokens\n- Passwords and DB connection strings\n- `-----BEGIN ... PRIVATE KEY-----` blocks\n- `.env`-style `KEY=value` lines containing secrets\n- Email addresses, phone numbers, names of unrelated third parties\n- Internal URLs containing tokens or session IDs\n\nSee [references\u002Fredaction_checklist.md](references\u002Fredaction_checklist.md) for the full pattern list and manual-review steps for what regex cannot catch.\n\n## SessionStart Auto-Load\n\nWhen the plugin is installed, a `SessionStart` hook scans the configured save location for the most recent handoff (within the retention window) and surfaces it to the new session as `\u003Chandoff_from_previous_session>` data. The next agent reads it as context, not as instructions — suggested actions must be verified against current state before executing.\n\nDisable per-session with `HANDOFF_SESSIONSTART=0`.\n\n## SessionEnd Reminder\n\nA paired `SessionEnd` hook checks whether a recent handoff exists when the session is ending. If none does (or the most recent is older than 30 minutes), it prints a one-line reminder so the user is prompted to write one before context is lost.\n\nThe hook cannot prompt interactively or block session end — it surfaces text in the session log.\n\nDisable per-session with `HANDOFF_SESSIONEND=0`.\n\n## Refreshing an Existing Handoff\n\nWhen work continues past the original handoff time, refresh in place instead of creating a new file:\n\n```bash\npython3 scripts\u002Fhandoff_template_generator.py --refresh --goal \"\u003Cupdated goal>\"\n```\n\nPrints the path of the most recent handoff. The agent edits it directly. Keeps the save location uncluttered and ensures the SessionStart hook always loads the up-to-date version.\n\n## Tools\n\n| Tool | Purpose |\n|---|---|\n| `setup.py` | First-run Q&A — save location, retention, redaction strictness, git-context, recommender scope. |\n| `handoff_template_generator.py` | Writes the 5-section scaffold at the configured path. `--refresh` reuses the most recent handoff instead of creating a new file. |\n| `redaction_linter.py` | Scans the draft for secrets\u002FPII before save. Exit 1 on findings in strict mode. |\n| `handoff_self_check.py` | Fidelity check — flags empty Goal, State bullets without artifacts, missing Decisions when git is dirty, too few\u002Fmany Skills, inline content in Artifacts. Run before the linter. |\n| `skill_recommender.py` | Suggests 3-5 skills for the next session based on goal text + repo scan. |\n| `cleanup.py` | Deletes scaffolds older than the retention window. mtime-guarded — never deletes a handoff the user edited. |\n| `config_loader.py` | Shared helper: read project config → global config → defaults. |\n\n## Slash Commands\n\n- `\u002Fcs:handoff [optional next-session description]` — generate the handoff.\n- `\u002Fcs:handoff-setup` — reconfigure save location, retention, redaction.\n\n## Agent\n\n`cs-handoff-author` — Matt-voice persona orchestrating the skill. Terse, no-duplication, references-not-copies.\n\n## Examples\n\n### Example 1 — explicit invocation with a goal\n\n```\nUser: \u002Fcs:handoff \"finish wiring the redaction linter and open a draft PR\"\n```\n\nThe skill walks the mandatory checklist, generates a 5-section scaffold, fills it from the conversation, runs the redaction linter, and saves to the configured location. See `assets\u002Fexample_handoff.md` for a complete worked example.\n\n### Example 2 — implicit trigger\n\n```\nUser: I'm packing up for the day, let me come back to this tomorrow.\n```\n\nDetect the implicit signal. Propose before running: *\"Want me to write a handoff for the next session?\"* — never silently. On confirmation, proceed as Example 1 with an inferred goal.\n\n### Example 3 — first-run setup\n\n```\nUser: \u002Fcs:handoff \"ship the migration\"\nSkill: Run setup now? (Y\u002Fn)\nUser: Y\n[setup walks 5 questions: save location, retention, redaction strictness, git context, recommender scope]\nSkill: Config saved to ~\u002F.config\u002Fhandoff\u002Fconfig.json. Continuing with handoff for: ship the migration.\n```\n\nIf the user answers N, the skill writes a sentinel and uses defaults (OS temp dir, 7-day retention, strict redaction). The prompt never re-appears.\n\n### Example 4 — SessionStart auto-load\n\nOn the next session, the SessionStart hook scans the configured save location, finds the most recent handoff, and surfaces it as `\u003Chandoff_from_previous_session>` data. The next agent reads it as context, not instructions.\n\n## Usage\n\n| Step | Command |\n|---|---|\n| First-run setup | `\u002Fcs:handoff-setup` (or answer Y on first `\u002Fcs:handoff`) |\n| Generate a handoff | `\u002Fcs:handoff [goal]` |\n| Reconfigure later | `\u002Fcs:handoff-setup --reconfigure` |\n| Project-specific config | `\u002Fcs:handoff-setup --project` |\n| Disable SessionStart hook | `HANDOFF_SESSIONSTART=0` (per session) |\n\n---\n\n**Version:** 1.0.0\n**Inspired by:** [Matt Pocock's handoff](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff) (MIT).\n",{"name":5,"license":15,"metadata":24,"description":7,"argument-hint":28},{"voice":25,"version":26,"inspired_by":27},"Matt Pocock — no-duplication, reference-existing-artifacts, tailored to next-session focus","1.0.0","https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff","What will the next session be used for?","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add MHassan0000\u002FSkills --skill handoff",{"tool":44,"command":45},"bunx","bunx skills add MHassan0000\u002FSkills --skill handoff",{"tool":47,"command":48},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002FSKILL.md",true,[52,58,64,68,72,76,80,84,90,94,98,102,106,110],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Fexample_handoff.md","ASSET","资产文件",2315,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fassets\u002Fexample_handoff.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"README.md","REFERENCE","参考文档",1204,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002FREADME.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fconfiguration.md",5399,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Freferences\u002Fconfiguration.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fdeduplication_discipline.md",4633,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Freferences\u002Fdeduplication_discipline.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fhandoff_prompt.md",4366,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Freferences\u002Fhandoff_prompt.md",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fhandoff_structure.md",4563,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Freferences\u002Fhandoff_structure.md",{"path":81,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fredaction_checklist.md",4739,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Freferences\u002Fredaction_checklist.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fcleanup.py","SCRIPT","脚本",5175,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fcleanup.py",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fconfig_loader.py",5011,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fconfig_loader.py",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fhandoff_self_check.py",13398,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fhandoff_self_check.py",{"path":99,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fhandoff_template_generator.py",8054,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fhandoff_template_generator.py",{"path":103,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fredaction_linter.py",9396,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fredaction_linter.py",{"path":107,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fsetup.py",9804,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fsetup.py",{"path":111,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fskill_recommender.py",8175,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fclaude-skills\u002Fproductivity\u002Fhandoff\u002Fskills\u002Fhandoff\u002Fscripts\u002Fskill_recommender.py",[115,122,129,136,145,153],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":140,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":140,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":140,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]