{
  "schemaVersion": "1.0",
  "item": {
    "slug": "email-management",
    "name": "Email Management",
    "source": "tencent",
    "type": "skill",
    "category": "通讯协作",
    "sourceUrl": "https://clawhub.ai/ivangdavila/email-management",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/email-management",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/email-management",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=email-management",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "automation.md",
      "feedback.md",
      "memory-template.md",
      "profiles.md",
      "setup.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/email-management"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/email-management",
    "agentPageUrl": "https://openagent3.xyz/skills/email-management/agent",
    "manifestUrl": "https://openagent3.xyz/skills/email-management/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/email-management/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Setup",
        "body": "On first use, read setup.md for integration guidelines and memory initialization."
      },
      {
        "title": "When to Use",
        "body": "User needs help processing inbox load, preparing replies, or keeping response commitments on track.\nAgent triages messages by urgency, drafts context-aware responses, and tracks pending follow-ups until closure.\n\nThis skill is workflow-focused and local by default. It analyzes email text provided by the user in chat or by a separate mail integration skill."
      },
      {
        "title": "Architecture",
        "body": "Memory lives in ~/email-management/. See memory-template.md for structure.\n\n~/email-management/\n├── memory.md          # Status, context, and communication preferences\n├── follow-ups.md      # Open threads with due dates and owners\n├── templates.md       # Approved reusable response blocks\n├── vip-contacts.md    # Priority senders and escalation notes\n└── digests/           # Weekly inbox summaries"
      },
      {
        "title": "Quick Reference",
        "body": "TopicFileSetup flowsetup.mdMemory templatememory-template.mdInbox triage logictriage.mdAutomation boundariesautomation.mdFollow-up workflowtracking.mdResponse templatestemplates.mdProfile presetsprofiles.mdQuality loopfeedback.md"
      },
      {
        "title": "1. Classify Before Responding",
        "body": "Always tag each email as Action, Waiting, FYI, or Noise before drafting anything.\n\nThis prevents urgent requests from being buried under low-value messages."
      },
      {
        "title": "2. Keep Priority Routing Explicit",
        "body": "Urgency must be tied to clear signals: VIP sender, hard deadline, financial or legal risk, or blocked decision.\n\nIf urgency is uncertain, mark as review-needed instead of urgent."
      },
      {
        "title": "3. Draft with Decision Clarity",
        "body": "Every draft reply should make the next step obvious with one of these outcomes:\n\nask a precise question\nprovide a decision\npropose a concrete next action with owner and date"
      },
      {
        "title": "4. Track Commitments as Tasks",
        "body": "Whenever a message includes a promise, request, or deadline, log it in follow-up tracking with:\n\nowner\ndue date or expected response window\ncurrent status"
      },
      {
        "title": "5. Separate Writing Tone from Message Intent",
        "body": "Preserve intent first, then adapt tone by audience.\n\nDo not soften urgent blockers into passive wording."
      },
      {
        "title": "6. Prefer Reusable Snippets for Recurring Scenarios",
        "body": "Use approved template blocks for recurring replies (status update, decline, clarification, follow-up).\n\nCustomize opening and close so replies do not feel robotic."
      },
      {
        "title": "7. Summarize Inbox Health Periodically",
        "body": "Provide concise summaries when workload is high:\n\ntop priorities\noverdue follow-ups\nthreads waiting on others\nmessages safe to archive"
      },
      {
        "title": "Common Traps",
        "body": "Replying before triage -> high-importance messages are delayed.\nTreating every fast request as urgent -> priority inflation reduces focus.\nSending drafts without owner/date clarity -> follow-ups are missed.\nUsing templates without context edits -> responses feel generic and can damage trust.\nClosing threads without explicit confirmation -> hidden commitments remain unresolved."
      },
      {
        "title": "Security & Privacy",
        "body": "Data that leaves your machine:\n\nNone by default.\n\nData that stays local:\n\nEmail management context and workflow notes under ~/email-management/.\n\nThis skill does NOT:\n\nSend emails automatically without explicit user confirmation.\nAccess files outside ~/email-management/ for storage.\nEnable background automations without explicit user approval.\nConnect directly to mailbox APIs or collect credentials on its own."
      },
      {
        "title": "Related Skills",
        "body": "Install with clawhub install <slug> if user confirms:\n\nmail - generic mail workflow support\nemail-marketing - campaign and newsletter execution workflows\ncrm - customer relationship process management\nproductivity - execution and prioritization frameworks\nassistant - general assistant orchestration patterns"
      },
      {
        "title": "Feedback",
        "body": "If useful: clawhub star email-management\nStay updated: clawhub sync"
      }
    ],
    "body": "Setup\n\nOn first use, read setup.md for integration guidelines and memory initialization.\n\nWhen to Use\n\nUser needs help processing inbox load, preparing replies, or keeping response commitments on track. Agent triages messages by urgency, drafts context-aware responses, and tracks pending follow-ups until closure.\n\nThis skill is workflow-focused and local by default. It analyzes email text provided by the user in chat or by a separate mail integration skill.\n\nArchitecture\n\nMemory lives in ~/email-management/. See memory-template.md for structure.\n\n~/email-management/\n├── memory.md          # Status, context, and communication preferences\n├── follow-ups.md      # Open threads with due dates and owners\n├── templates.md       # Approved reusable response blocks\n├── vip-contacts.md    # Priority senders and escalation notes\n└── digests/           # Weekly inbox summaries\n\nQuick Reference\nTopic\tFile\nSetup flow\tsetup.md\nMemory template\tmemory-template.md\nInbox triage logic\ttriage.md\nAutomation boundaries\tautomation.md\nFollow-up workflow\ttracking.md\nResponse templates\ttemplates.md\nProfile presets\tprofiles.md\nQuality loop\tfeedback.md\nCore Rules\n1. Classify Before Responding\n\nAlways tag each email as Action, Waiting, FYI, or Noise before drafting anything.\n\nThis prevents urgent requests from being buried under low-value messages.\n\n2. Keep Priority Routing Explicit\n\nUrgency must be tied to clear signals: VIP sender, hard deadline, financial or legal risk, or blocked decision.\n\nIf urgency is uncertain, mark as review-needed instead of urgent.\n\n3. Draft with Decision Clarity\n\nEvery draft reply should make the next step obvious with one of these outcomes:\n\nask a precise question\nprovide a decision\npropose a concrete next action with owner and date\n4. Track Commitments as Tasks\n\nWhenever a message includes a promise, request, or deadline, log it in follow-up tracking with:\n\nowner\ndue date or expected response window\ncurrent status\n5. Separate Writing Tone from Message Intent\n\nPreserve intent first, then adapt tone by audience.\n\nDo not soften urgent blockers into passive wording.\n\n6. Prefer Reusable Snippets for Recurring Scenarios\n\nUse approved template blocks for recurring replies (status update, decline, clarification, follow-up).\n\nCustomize opening and close so replies do not feel robotic.\n\n7. Summarize Inbox Health Periodically\n\nProvide concise summaries when workload is high:\n\ntop priorities\noverdue follow-ups\nthreads waiting on others\nmessages safe to archive\nCommon Traps\nReplying before triage -> high-importance messages are delayed.\nTreating every fast request as urgent -> priority inflation reduces focus.\nSending drafts without owner/date clarity -> follow-ups are missed.\nUsing templates without context edits -> responses feel generic and can damage trust.\nClosing threads without explicit confirmation -> hidden commitments remain unresolved.\nSecurity & Privacy\n\nData that leaves your machine:\n\nNone by default.\n\nData that stays local:\n\nEmail management context and workflow notes under ~/email-management/.\n\nThis skill does NOT:\n\nSend emails automatically without explicit user confirmation.\nAccess files outside ~/email-management/ for storage.\nEnable background automations without explicit user approval.\nConnect directly to mailbox APIs or collect credentials on its own.\nRelated Skills\n\nInstall with clawhub install <slug> if user confirms:\n\nmail - generic mail workflow support\nemail-marketing - campaign and newsletter execution workflows\ncrm - customer relationship process management\nproductivity - execution and prioritization frameworks\nassistant - general assistant orchestration patterns\nFeedback\nIf useful: clawhub star email-management\nStay updated: clawhub sync"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/email-management",
    "publisherUrl": "https://clawhub.ai/ivangdavila/email-management",
    "owner": "ivangdavila",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/email-management",
    "downloadUrl": "https://openagent3.xyz/downloads/email-management",
    "agentUrl": "https://openagent3.xyz/skills/email-management/agent",
    "manifestUrl": "https://openagent3.xyz/skills/email-management/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/email-management/agent.md"
  }
}