[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWM7Y03TWCFSRV8ZNWYNE8":3,"skill-same:01M7CWM7Y03TWCFSRV8ZNWYNE8":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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CWM7Y03TWCFSRV8ZNWYNE8","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.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Femail-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\nmetadata:\n  origin: 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,"metadata":24,"description":7},{"origin":25},"ECC","main","a73152352c0612252131e5cf84e91312a6cf17dc","utilities\u002Femail-ops","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill email-ops",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill email-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill email-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Femail-ops\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"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},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"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},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\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":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\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":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","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\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]