mex-inbox
From the author
Draft and review contributions to existing MEX project knowledge. Use when the user asks to capture a discussion or decision in project knowledge, propose an addition or correction for team review, or explicitly invokes /mex-inbox or $mex-inbox. Also supports existing Spec proposals. Do not activate for brainstorming alone, routine GROW upkeep, email inboxes, session logs, or handoffs.
Install
npx skills add mex-memory/mex --skill mex-inbox -a claude-code
Installs to .claude/skills/mex-inbox/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 89
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- deliverable-intakescdenney/open-science-skillsTurns dictated captures in a deliverable's inbox/ into a proposed planning-wiki diff, classifying and tracing each statement; decisions need the author's assent. Use to intake notes or process the inbox.Planning★ 69
- pm-deep-talkkonglong87/superPMUse when: 用户已有产品想法、方案、计划或待选方案，希望分析利弊、梳理选择标准、补全关键考虑或获得决策建议 用户明确要求“深入聊聊”“分析这个方案”“帮我梳理取舍”“我该怎么选” 用户在 pm-brainstorm 中选定方向后，主动要求进一步讨论其可行性与取舍 Do NOT use when: 用户还没有方向，只想产生多个创意（使用 pm-brainstorm） 用户只需要事实调研、需求验证、市场分析、优先级计算或文档撰写（使用对应 skill）Planning★ 84
- pr-draft-summarysandbaseai/sandbase-skillsPlan, implement, or review pr draft summary work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests pr draft summary work.Productivity★ 203
- vote-draftapache/magpieDraft the `[VOTE]` email body and planning-issue comment for an RC of `<upstream>`. Reads RC metadata from the planning issue and `<project-config>/release-management-config.md`; produces a ready-to-copy `[VOTE]` subject + body and a proposed planning-issue comment. Never sends mail and never posts without explicit RM confirmation.Planning★ 127
- apex-plantonone-ai/tononePlan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.Planning★ 76
- email-draftingseb1n/awesome-ai-agent-skillsDraft a professional, audience-aware email or reply with calibrated tone and a clear call to action. Use when the user needs one message, response, follow-up, support note, or meeting request; use sales-email-sequences for a coordinated multi-touch outbound campaign.Productivity★ 229
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in