Skip to content

hoavdc/CodexKit / skills/codexkit-email-composer

codexkit-email-composer

Verified

Draft 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.

FileKindSize
SKILL.mdskill md3.7 KB
agents/openai.yamlconfig168 B
examples/common-mistakes.mdmarkdown846 B
examples/good-output.mdmarkdown1019 B
verification/checklist.mdmarkdown1.5 KB

verification/checklist.md

View on GitHub
# 4C Verification Checklist - Email Composer

Use this checklist before treating an email draft as ready to send.

## Correctness - Is it right?

- [ ] Names, company names, dates, prices, links, and commitments match the user's input.
- [ ] The subject line accurately previews the email's purpose.
- [ ] Any quoted or summarized prior message is represented faithfully.
- [ ] No legal, HR, pricing, or delivery commitment is invented.

## Completeness - Is it done?

- [ ] The email includes subject, greeting, context, body, next step, and close when appropriate.
- [ ] The primary ask or message is clear within the first few sentences.
- [ ] Required attachments, links, CCs, or references are mentioned if provided.
- [ ] Deadline or response expectation is stated when action is needed.

## Context-fit - Does it match?

- [ ] Tone matches recipient relationship: internal, client, vendor, executive, or peer.
- [ ] Length fits the channel and stakes.
- [ ] The email is direct enough for busy readers and polite enough for the relationship.
- [ ] Optional shorter Slack/chat variant is included when useful.

## Consequence - Is it safe to use?

- [ ] Could this wording escalate conflict unnecessarily?
- [ ] Could the email create an unintended promise, admission, or contractual interpretation?
- [ ] Should a manager, HR, legal, finance, or comms reviewer approve it first?
- [ ] If forwarded outside the intended audience, would it create avoidable risk?

Final check: what is the single sentence most likely to be misread?
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: 468kUpdated Claude CodeCodexVerifiedInstall
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: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 319kUpdated Claude CodeCodexVerifiedInstall