[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZEGQPFXEGTTC2TVSXRBF9":3,"skill-same:01M72ZEGQPFXEGTTC2TVSXRBF9":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72ZEGQPFXEGTTC2TVSXRBF9","email-ops",null,"Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Femail-ops\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: email-ops\ndescription: Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.\norigin: ECC\n---\n\n# Email Ops\n\nUse this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.\n\nThis is not a generic writing skill. It is an operator workflow around the actual mail surface.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `brand-voice` before drafting anything user-facing\n- `investor-outreach` for investor, partner, or sponsor-facing mail\n- `customer-billing-ops` when the thread is a billing\u002Fsupport incident rather than generic correspondence\n- `knowledge-ops` when the message or thread should be captured into durable context afterward\n- `research-ops` when a reply depends on fresh external facts\n\n## When to Use\n\n- user asks to triage inbox or archive low-signal mail\n- user wants a draft, reply, or new outbound email\n- user wants to know whether a mail was already sent\n- the user wants proof of which account, thread, or Sent entry was used\n\n## Guardrails\n\n- draft first unless the user clearly asked for a live send\n- never claim a message was sent without a real Sent-folder or client-side confirmation\n- do not switch sender accounts casually; choose the account that matches the project and recipient\n- do not delete uncertain business mail during cleanup\n- if the task is really DM or iMessage work, hand off to `messages-ops`\n\n## Workflow\n\n### 1. Resolve the exact surface\n\nBefore acting, settle:\n\n- which mailbox account\n- which thread or recipient\n- whether the task is triage, draft, reply, or send\n- whether the user wants draft-only or live send\n\n### 2. Read the thread before composing\n\nIf replying:\n\n- read the existing thread\n- identify the last outbound touch\n- identify any commitments, deadlines, or unanswered questions\n\nIf creating a new outbound:\n\n- identify warmth level\n- select the correct channel and sender account\n- pull `brand-voice` before drafting\n\n### 3. Draft, then verify\n\nFor draft-only work:\n\n- produce the final copy\n- state sender, recipient, subject, and purpose\n\nFor live-send work:\n\n- verify the exact final body first\n- send through the chosen mail surface\n- confirm the message landed in Sent or the equivalent sent-copy store\n\n### 4. Report exact state\n\nUse exact status words:\n\n- drafted\n- approval-pending\n- sent\n- blocked\n- awaiting verification\n\nIf the send surface is blocked, preserve the draft and report the exact blocker instead of improvising a second transport without saying so.\n\n## Output Format\n\n```text\nMAIL SURFACE\n- account\n- thread \u002F recipient\n- requested action\n\nDRAFT\n- subject\n- body\n\nSTATUS\n- drafted \u002F sent \u002F blocked\n- proof of Sent when applicable\n\nNEXT STEP\n- send\n- follow up\n- archive \u002F move\n```\n\n## Pitfalls\n\n- do not claim send success without a sent-copy check\n- do not ignore the thread history and write a contextless reply\n- do not mix mailbox work with DM or text-message workflows\n- do not expose secrets, auth details, or unnecessary message metadata\n\n## Verification\n\n- the response names the account and thread or recipient\n- any send claim includes Sent proof or an explicit client-side confirmation\n- the final state is one of drafted \u002F sent \u002F blocked \u002F awaiting verification\n","# Email Ops\n\nUse this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.\n\nThis is not a generic writing skill. It is an operator workflow around the actual mail surface.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `brand-voice` before drafting anything user-facing\n- `investor-outreach` for investor, partner, or sponsor-facing mail\n- `customer-billing-ops` when the thread is a billing\u002Fsupport incident rather than generic correspondence\n- `knowledge-ops` when the message or thread should be captured into durable context afterward\n- `research-ops` when a reply depends on fresh external facts\n\n## When to Use\n\n- user asks to triage inbox or archive low-signal mail\n- user wants a draft, reply, or new outbound email\n- user wants to know whether a mail was already sent\n- the user wants proof of which account, thread, or Sent entry was used\n\n## Guardrails\n\n- draft first unless the user clearly asked for a live send\n- never claim a message was sent without a real Sent-folder or client-side confirmation\n- do not switch sender accounts casually; choose the account that matches the project and recipient\n- do not delete uncertain business mail during cleanup\n- if the task is really DM or iMessage work, hand off to `messages-ops`\n\n## Workflow\n\n### 1. Resolve the exact surface\n\nBefore acting, settle:\n\n- which mailbox account\n- which thread or recipient\n- whether the task is triage, draft, reply, or send\n- whether the user wants draft-only or live send\n\n### 2. Read the thread before composing\n\nIf replying:\n\n- read the existing thread\n- identify the last outbound touch\n- identify any commitments, deadlines, or unanswered questions\n\nIf creating a new outbound:\n\n- identify warmth level\n- select the correct channel and sender account\n- pull `brand-voice` before drafting\n\n### 3. Draft, then verify\n\nFor draft-only work:\n\n- produce the final copy\n- state sender, recipient, subject, and purpose\n\nFor live-send work:\n\n- verify the exact final body first\n- send through the chosen mail surface\n- confirm the message landed in Sent or the equivalent sent-copy store\n\n### 4. Report exact state\n\nUse exact status words:\n\n- drafted\n- approval-pending\n- sent\n- blocked\n- awaiting verification\n\nIf the send surface is blocked, preserve the draft and report the exact blocker instead of improvising a second transport without saying so.\n\n## Output Format\n\n```text\nMAIL SURFACE\n- account\n- thread \u002F recipient\n- requested action\n\nDRAFT\n- subject\n- body\n\nSTATUS\n- drafted \u002F sent \u002F blocked\n- proof of Sent when applicable\n\nNEXT STEP\n- send\n- follow up\n- archive \u002F move\n```\n\n## Pitfalls\n\n- do not claim send success without a sent-copy check\n- do not ignore the thread history and write a contextless reply\n- do not mix mailbox work with DM or text-message workflows\n- do not expose secrets, auth details, or unnecessary message metadata\n\n## Verification\n\n- the response names the account and thread or recipient\n- any send claim includes Sent proof or an explicit client-side confirmation\n- the final state is one of drafted \u002F sent \u002F blocked \u002F awaiting verification\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Femail-ops",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill email-ops",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill email-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill email-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Femail-ops\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"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},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\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},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\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},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\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},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]