hoavdc/CodexKit / skills/codexkit-email-composer
codexkit-email-composer
VerifiedDraft clear, professional business emails from rough notes, context, or instructions. Handles cold outreach, internal updates, client responses, and escalation drafts. Use when the work is routine email writing with known context and audience. Do not use for sensitive legal notices, formal regulatory correspondence, or board-level communication without review.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| agents/openai.yaml | config | 168 B |
| examples/common-mistakes.md | markdown | 846 B |
| examples/good-output.md | markdown | 1019 B |
| verification/checklist.md | markdown | 1.5 KB |
examples/common-mistakes.md
View on GitHub# Common Mistakes - Email Composer
## 1. Hiding the ask
**What goes wrong:** The email is polite but the reader cannot tell what action is needed.
**Fix:** Put the ask in one direct sentence and include timing when needed.
## 2. Over-escalating tone
**What goes wrong:** A routine follow-up sounds like a complaint or threat.
**Fix:** State the business consequence calmly before escalating.
## 3. Inventing commitments
**What goes wrong:** The draft says "as agreed" or "you promised" when the user did not provide that evidence.
**Fix:** Use source-backed wording such as "we discussed" only when the source supports it.
## 4. Using the wrong channel length
**What goes wrong:** A short Slack update becomes a long formal email, or an executive email is too casual.
**Fix:** Match length and tone to channel, recipient, and stakes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |