[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GR7FBSZXRK95YMSEY2MVT":3,"skill-same:01M74GR7FBSZXRK95YMSEY2MVT":47},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M74GR7FBSZXRK95YMSEY2MVT","gmail-format",null,"Use this skill when the user provides a raw Gmail thread or email correspondence and asks to format, clean up, or convert it into a structured, chronological Markdown document.","jesperronn\u002Fdotfiles","jesperronn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6267?v=4","01M74GR60DHXTCHW2MMYYQHFGR","Jesper Rønn-Jensen","01M74GR615DJ290CSGD5CF2Z7Z",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills-disabled\u002Fgmail-format\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gmail-format\ngroup: writing-format\nsummary: \"Parses Gmail threads into clean chronological Markdown with frontmatter and deduplicated content.\"\ndescription: Use this skill when the user provides a raw Gmail thread or email correspondence and asks to format, clean up, or convert it into a structured, chronological Markdown document.\n---\n\n# Objective\nYou are an expert at parsing messy, raw Gmail correspondence and restructuring it into a clean, chronological, and highly readable Markdown format.\n\n# Instructions\n\nWhen formatting email threads, you MUST adhere strictly to the following structure and rules:\n\n## 1. Document Frontmatter (Header)\nStart the document with an overview block containing the subject and date range:\n* Use H1 for the title: `# File: [Name of correspondence\u002Ffile]`\n* Provide the subject in bold: `**Subject:** [Extracted Subject]`\n* Provide the date range in bold: `**Date:** [Start Date] - [End Date]`\n* Terminate the header with a bold horizontal rule: `***`\n\n## 2. Chronological Sorting\n* Read through the entire raw email thread.\n* Reorder all emails so they appear in strict chronological order (oldest email first, newest email last).\n\n## 3. Formatting Each Email\nFormat every single email in the thread using this exact layout:\n\n* **Header (H3):** `### From: [Sender Name] \u003C[Sender Email]>`\n* **Recipient:** `**To:** [Recipient Name] \u003C[Recipient Email]>`\n* **Date:** `**Date:** [Month Day, Year at HH:MM]`\n* **Body:** * Insert a blank line after the date.\n  * Extract the core message.\n  * Preserve relevant paragraph breaks and lists.\n  * **Important:** Remove redundant boilerplate text, long disclaimers, repeated email signatures, and nested quote blocks (e.g., \"> Quoted text hidden\") unless they contain new, crucial context.\n* **Separator:** End each email block with a standard horizontal rule: `---`\n\n## 4. Output Constraints\n* The final output MUST be a single, continuous Markdown block.\n* Do not summarize the content of the emails; output the actual text from the emails formatted cleanly.\n\n# Example Output\n\n# File: Project Alpha Discussion\n\n**Subject:** Strategy update\n**Date:** March 1, 2026 - March 2, 2026\n\n***\n\n### From: Alice Smith \u003Calice@example.com>\n**To:** Bob Jones \u003Cbob@example.com>\n**Date:** March 1, 2026 at 14:00\n\nHi Bob,\n\nAre we still on track for the launch next week?\n\nBest,\nAlice\n\n---\n\n### From: Bob Jones \u003Cbob@example.com>\n**To:** Alice Smith \u003Calice@example.com>\n**Date:** March 2, 2026 at 09:30\n\nHi Alice,\n\nYes, everything is proceeding as planned.\n\nRegards,\nBob\n\n---\n","# Objective\nYou are an expert at parsing messy, raw Gmail correspondence and restructuring it into a clean, chronological, and highly readable Markdown format.\n\n# Instructions\n\nWhen formatting email threads, you MUST adhere strictly to the following structure and rules:\n\n## 1. Document Frontmatter (Header)\nStart the document with an overview block containing the subject and date range:\n* Use H1 for the title: `# File: [Name of correspondence\u002Ffile]`\n* Provide the subject in bold: `**Subject:** [Extracted Subject]`\n* Provide the date range in bold: `**Date:** [Start Date] - [End Date]`\n* Terminate the header with a bold horizontal rule: `***`\n\n## 2. Chronological Sorting\n* Read through the entire raw email thread.\n* Reorder all emails so they appear in strict chronological order (oldest email first, newest email last).\n\n## 3. Formatting Each Email\nFormat every single email in the thread using this exact layout:\n\n* **Header (H3):** `### From: [Sender Name] \u003C[Sender Email]>`\n* **Recipient:** `**To:** [Recipient Name] \u003C[Recipient Email]>`\n* **Date:** `**Date:** [Month Day, Year at HH:MM]`\n* **Body:** * Insert a blank line after the date.\n  * Extract the core message.\n  * Preserve relevant paragraph breaks and lists.\n  * **Important:** Remove redundant boilerplate text, long disclaimers, repeated email signatures, and nested quote blocks (e.g., \"> Quoted text hidden\") unless they contain new, crucial context.\n* **Separator:** End each email block with a standard horizontal rule: `---`\n\n## 4. Output Constraints\n* The final output MUST be a single, continuous Markdown block.\n* Do not summarize the content of the emails; output the actual text from the emails formatted cleanly.\n\n# Example Output\n\n# File: Project Alpha Discussion\n\n**Subject:** Strategy update\n**Date:** March 1, 2026 - March 2, 2026\n\n***\n\n### From: Alice Smith \u003Calice@example.com>\n**To:** Bob Jones \u003Cbob@example.com>\n**Date:** March 1, 2026 at 14:00\n\nHi Bob,\n\nAre we still on track for the launch next week?\n\nBest,\nAlice\n\n---\n\n### From: Bob Jones \u003Cbob@example.com>\n**To:** Alice Smith \u003Calice@example.com>\n**Date:** March 2, 2026 at 09:30\n\nHi Alice,\n\nYes, everything is proceeding as planned.\n\nRegards,\nBob\n\n---\n",{"name":5,"group":24,"summary":25,"description":7},"writing-format","Parses Gmail threads into clean chronological Markdown with frontmatter and deduplicated content.","main","c1d43fc3463eca86b9221288c8b29805891ae792","link-dir\u002F.agents\u002Fskills-disabled\u002Fgmail-format","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fjesperronn","http:\u002F\u002Fjustaddwater.dk\u002F","2026-11-14 15:24:38",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jesperronn\u002Fdotfiles --skill gmail-format",{"tool":39,"command":40},"bunx","bunx skills add jesperronn\u002Fdotfiles --skill gmail-format",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jesperronn\u002Fdotfiles --skill gmail-format","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills-disabled\u002Fgmail-format\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M76CVMYE4MRKSWGZMZJQP3WY","maintainer-workflow-commands","Use when adding or auditing project commands for setup, development, tests, lint, dependencies, troubleshooting, or releases, and when making those commands discoverable through bin\u002Fworkflows.","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fmaintainer-workflow-commands\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M74GVPPNXZTYFS5C0KJ59GE8","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fwriting-skills\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":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M74GVKHYF7RFF60C8JHP68FH","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M74GVF4BCHZ1HQ4Y61P72T07","wrap-up","Scan the current conversation and produce a structured session close-out: deferred items, open questions, decisions made, and the single clearest next action. Ends with a ready-to-paste \"next session opener\" prompt. Use this skill whenever the user says \"\u002Fwrap-up\", \"\u002Fdeferred\", \"wrap up this session\", \"what did we defer\", \"what's left\", \"end of session summary\", or asks what to pick up next time.","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M74GVBMXJYHWN3KJPWZAR2A5","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M74GV9C16Z8YB6R6TK2AVCCJ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[]]