[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73D5GF4161KA3NDZ4SS8J7N":3,"skill-same:01M73D5GF4161KA3NDZ4SS8J7N":59},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73D5GF4161KA3NDZ4SS8J7N","write-continue-here",null,"Write a CONTINUE_HERE.md file capturing current session state so a fresh Claude Code session can pick up where this one left off. Covers assessing recent work, structuring the continuation file with objective, completed, in-progress, next-steps, and context sections, and verifying the file is actionable. Use when ending a session with unfinished work, handing off context between sessions, or preserving task state that git alone cannot capture.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-continue-here\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: write-continue-here\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-05-03\"\ndescription: >\n  Write a CONTINUE_HERE.md file capturing current session state so a fresh\n  Claude Code session can pick up where this one left off. Covers assessing\n  recent work, structuring the continuation file with objective, completed,\n  in-progress, next-steps, and context sections, and verifying the file is\n  actionable. Use when ending a session with unfinished work, handing off\n  context between sessions, or preserving task state that git alone cannot\n  capture.\nlicense: MIT\nallowed-tools: Read Write Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: general\n  complexity: basic\n  language: multi\n  tags: session, continuity, handoff, context, workflow, write\n---\n\n# Write Continue Here\n\nWrite a structured continuation file so the next session starts with full context.\n\n## When to Use\n\n- Ending a session with work still in progress\n- Handing off a complex task between sessions\n- Preserving intent, failed approaches, and next steps that git cannot capture\n- Before closing Claude Code when mid-task\n\n## Inputs\n\n- **Required**: An active session with recent work to summarize\n- **Optional**: Specific instructions about what to emphasize in the handoff\n\n## Procedure\n\n### Step 1: Assess Session State\n\nGather facts about recent work:\n\n```bash\ngit log --oneline -5\ngit status\ngit diff --stat\n```\n\nReview the conversation context: what was the objective, what was completed, what is partially done, what was tried and failed, what decisions were made.\n\n**Got:** Clear understanding of current task state — completed items, in-progress items, and planned next steps.\n\n**If fail:** If not in a git repository, skip git commands. The continuation file can still capture conversational context and task state.\n\n### Step 2: Write CONTINUE_HERE.md\n\nWrite the file to the project root using the structure below. Every section must contain actionable content, not placeholders.\n\n```markdown\n# Continue Here\n\n> Last updated: YYYY-MM-DDTHH:MM:SSZ | Branch: current-branch-name\n\n## Objective\nOne-paragraph description of what we are trying to accomplish and why.\n\n## Completed\n- [x] Finished item with key file paths (e.g., `src\u002Ffeature.R`)\n- [x] Decisions made and their rationale\n\n## In Progress\n- [ ] Partially complete work — describe current state (branch, file:line)\n- [ ] Known issues with partial work\n\n## Next Steps\n1. Immediate next action (most important)\n2. Subsequent actions in priority order\n3. **[USER]** Items needing user input or decision\n\n## Context\n- Failed approaches and why they did not work\n- Key constraints or trade-offs discovered\n- Relevant issue\u002FPR links\n```\n\nGuidelines:\n- **Objective**: Capture the WHY — git log shows what changed, not why\n- **Completed**: Mark items clearly done to prevent re-work\n- **In Progress**: This is the highest-value section — partial state is hardest to reconstruct\n- **Next Steps**: Number by priority. Prefix user-dependent items with `**[USER]**`\n- **Context**: Record negative space — what was tried and rejected, and why\n\n**Got:** A CONTINUE_HERE.md file at the project root with all 5 sections populated with real content from the current session. The timestamp and branch are accurate.\n\n**If fail:** If Write fails, check file permissions. The file should be created in the project root (same directory as `.git\u002F`). Verify `.gitignore` contains `CONTINUE_HERE.md` — if not, add it.\n\n### Step 3: Verify the File\n\nRead back CONTINUE_HERE.md and confirm:\n- Timestamp is current (within the last few minutes)\n- Branch name matches `git branch --show-current`\n- All 5 sections contain real content (no template placeholders)\n- Next Steps are numbered and actionable\n- In Progress items describe current state specifically enough to resume\n\n**Got:** The file reads as a clear, actionable handoff that a fresh session could use to immediately resume work.\n\n**If fail:** Edit sections that contain placeholder text or are too vague. Each section should pass the test: \"Could a fresh session act on this without asking clarifying questions?\"\n\n## Validation\n\n- [ ] CONTINUE_HERE.md exists at the project root\n- [ ] File contains all 5 sections with real content (not placeholders)\n- [ ] Timestamp and branch are accurate\n- [ ] `.gitignore` includes `CONTINUE_HERE.md`\n- [ ] Next Steps are numbered and actionable\n- [ ] In Progress items specify enough detail to resume without questions\n\n## Pitfalls\n\n- **Writing placeholders instead of content**: \"TODO: fill in later\" defeats the purpose. Every section must contain real information from the current session.\n- **Duplicating git state**: Do not list every file changed — git already tracks that. Focus on intent, partial state, and next steps.\n- **Forgetting the Context section**: Failed approaches are the most valuable thing to record. Without them, the next session will retry the same dead ends.\n- **Overwriting without reading**: If CONTINUE_HERE.md already exists from a prior session, read it first — it may contain unfinished work from an earlier handoff.\n- **Leaving stale files**: CONTINUE_HERE.md is ephemeral. After the next session consumes it, delete it. Stale files cause confusion.\n\n## Related Skills\n\n- `read-continue-here` — the complement: reading and acting on the continuation file at session start\n- `bootstrap-agent-identity` — cold-start identity reconstruction that consumes the continuation file this skill produces\n- `manage-memory` — durable cross-session knowledge (complements this ephemeral handoff)\n- `commit-changes` — save work to git before writing the continuation file\n- `write-claude-md` — project instructions where optional continuity guidance lives\n","# Write Continue Here\n\nWrite a structured continuation file so the next session starts with full context.\n\n## When to Use\n\n- Ending a session with work still in progress\n- Handing off a complex task between sessions\n- Preserving intent, failed approaches, and next steps that git cannot capture\n- Before closing Claude Code when mid-task\n\n## Inputs\n\n- **Required**: An active session with recent work to summarize\n- **Optional**: Specific instructions about what to emphasize in the handoff\n\n## Procedure\n\n### Step 1: Assess Session State\n\nGather facts about recent work:\n\n```bash\ngit log --oneline -5\ngit status\ngit diff --stat\n```\n\nReview the conversation context: what was the objective, what was completed, what is partially done, what was tried and failed, what decisions were made.\n\n**Got:** Clear understanding of current task state — completed items, in-progress items, and planned next steps.\n\n**If fail:** If not in a git repository, skip git commands. The continuation file can still capture conversational context and task state.\n\n### Step 2: Write CONTINUE_HERE.md\n\nWrite the file to the project root using the structure below. Every section must contain actionable content, not placeholders.\n\n```markdown\n# Continue Here\n\n> Last updated: YYYY-MM-DDTHH:MM:SSZ | Branch: current-branch-name\n\n## Objective\nOne-paragraph description of what we are trying to accomplish and why.\n\n## Completed\n- [x] Finished item with key file paths (e.g., `src\u002Ffeature.R`)\n- [x] Decisions made and their rationale\n\n## In Progress\n- [ ] Partially complete work — describe current state (branch, file:line)\n- [ ] Known issues with partial work\n\n## Next Steps\n1. Immediate next action (most important)\n2. Subsequent actions in priority order\n3. **[USER]** Items needing user input or decision\n\n## Context\n- Failed approaches and why they did not work\n- Key constraints or trade-offs discovered\n- Relevant issue\u002FPR links\n```\n\nGuidelines:\n- **Objective**: Capture the WHY — git log shows what changed, not why\n- **Completed**: Mark items clearly done to prevent re-work\n- **In Progress**: This is the highest-value section — partial state is hardest to reconstruct\n- **Next Steps**: Number by priority. Prefix user-dependent items with `**[USER]**`\n- **Context**: Record negative space — what was tried and rejected, and why\n\n**Got:** A CONTINUE_HERE.md file at the project root with all 5 sections populated with real content from the current session. The timestamp and branch are accurate.\n\n**If fail:** If Write fails, check file permissions. The file should be created in the project root (same directory as `.git\u002F`). Verify `.gitignore` contains `CONTINUE_HERE.md` — if not, add it.\n\n### Step 3: Verify the File\n\nRead back CONTINUE_HERE.md and confirm:\n- Timestamp is current (within the last few minutes)\n- Branch name matches `git branch --show-current`\n- All 5 sections contain real content (no template placeholders)\n- Next Steps are numbered and actionable\n- In Progress items describe current state specifically enough to resume\n\n**Got:** The file reads as a clear, actionable handoff that a fresh session could use to immediately resume work.\n\n**If fail:** Edit sections that contain placeholder text or are too vague. Each section should pass the test: \"Could a fresh session act on this without asking clarifying questions?\"\n\n## Validation\n\n- [ ] CONTINUE_HERE.md exists at the project root\n- [ ] File contains all 5 sections with real content (not placeholders)\n- [ ] Timestamp and branch are accurate\n- [ ] `.gitignore` includes `CONTINUE_HERE.md`\n- [ ] Next Steps are numbered and actionable\n- [ ] In Progress items specify enough detail to resume without questions\n\n## Pitfalls\n\n- **Writing placeholders instead of content**: \"TODO: fill in later\" defeats the purpose. Every section must contain real information from the current session.\n- **Duplicating git state**: Do not list every file changed — git already tracks that. Focus on intent, partial state, and next steps.\n- **Forgetting the Context section**: Failed approaches are the most valuable thing to record. Without them, the next session will retry the same dead ends.\n- **Overwriting without reading**: If CONTINUE_HERE.md already exists from a prior session, read it first — it may contain unfinished work from an earlier handoff.\n- **Leaving stale files**: CONTINUE_HERE.md is ephemeral. After the next session consumes it, delete it. Stale files cause confusion.\n\n## Related Skills\n\n- `read-continue-here` — the complement: reading and acting on the continuation file at session start\n- `bootstrap-agent-identity` — cold-start identity reconstruction that consumes the continuation file this skill produces\n- `manage-memory` — durable cross-session knowledge (complements this ephemeral handoff)\n- `commit-changes` — save work to git before writing the continuation file\n- `write-claude-md` — project instructions where optional continuity guidance lives\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"session, continuity, handoff, context, workflow, write","Philipp Thoss","general","1.0","multi","basic","Julius Brussee homage — caveman","Write a CONTINUE_HERE.md file capturing current session state so a fresh Claude Code session can pick up where this one left off. Covers assessing recent work, structuring the continuation file with objective, completed, in-progress, next-steps, and context sections, and verifying the file is actionable. Use when ending a session with unfinished work, handing off context between sessions, or preserving task state that git alone cannot capture.\n","Read Write Bash Grep Glob","82c77053","en","2026-05-03","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fwrite-continue-here",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill write-continue-here",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill write-continue-here",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill write-continue-here","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-continue-here\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]