End-of-Life Announcement Writer
getcrew44/crew44
Drafts a clear, empathetic end-of-life announcement for a product, feature or plan, covering rationale, customer impact, transition support, timeline and next steps.
Draft professional emails for various contexts including business, technical, and customer communication.
$ npx skills add curiositech/some_claude_skills --skill email-composer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install curiositech/some_claude_skills email-composer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/email-composer .claude/skills/email-composer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "email-composer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composer into .claude/skills/email-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-composer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add curiositech/some_claude_skills --skill email-composer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install curiositech/some_claude_skills email-composer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/email-composer .agents/skills/email-composer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "email-composer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composer into .agents/skills/email-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-composer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill email-composer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install curiositech/some_claude_skills email-composer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/email-composer .cursor/skills/email-composer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "email-composer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composer into .cursor/skills/email-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-composer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/curiositech/some_claude_skills.git --path .claude/skills/email-composer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add curiositech/some_claude_skills --skill email-composer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install curiositech/some_claude_skills email-composer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/email-composer .gemini/skills/email-composer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "email-composer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composer into .gemini/skills/email-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-composer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install curiositech/some_claude_skills email-composerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add curiositech/some_claude_skills --skill email-composer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/email-composer .github/skills/email-composer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "email-composer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composer into .github/skills/email-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-composer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill email-composer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install curiositech/some_claude_skills email-composer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/email-composer .opencode/skills/email-composer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "email-composer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/email-composer into .opencode/skills/email-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-composer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
email-composerDraft professional emails for various contexts including business, technical, and customer communication.
Email Composer is an agent skill from curiositech/some_claude_skills. Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).
It sits in Writing & Content, covering Email writing. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.
Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Email Composer loads about 1.8k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 282 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 282 words, ~1,834 tokens.
.claude/skills/email-composer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Provide context and purpose, and I'll draft an appropriate email.
What I need:
Standard professional email format:
Subject: [Clear, specific subject line]
[Greeting],
[Opening - context/purpose]
[Body - main points]
[Closing - call to action]
[Sign-off]
[Your name]Subject: Question about Q4 project timeline
Hi [Name],
I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.
Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of
This will help us coordinate with the marketing team for the launch materials.
Thanks in advance for your help!
Best regards,
[Your name]Subject: Following up: Proposal for new payment system
Hi [Name],
I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.
To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience
I'd be happy to schedule a brief call to discuss any questions you might have.
Looking forward to hearing from you.
Best,
[Your name]Subject: API Maintenance Window - [Date]
Team,
This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].
During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed
Expected downtime: 2 hours
What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes
If you have any concerns or conflicts with this schedule, please let me know by [Date].
Technical details available in our status page: [link]
Thanks,
[Your name]Subject: Re: Issue with order #12345
Hi [Customer name],
Thank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.
I've looked into your order (#12345) and found the following:
[Explanation of the issue]
To resolve this, I've:
- [Action taken 1]
- [Action taken 2]
You should see [expected outcome] within [timeframe].
If you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].
We appreciate your patience and understanding.
Best regards,
[Your name]
Customer Support TeamSubject: Meeting request: Discuss database migration strategy
Hi [Name],
I'd like to schedule a meeting to discuss our approach for the upcoming database migration.
Agenda items:
- Review migration timeline and milestones
- Discuss rollback strategy
- Identify potential risks and mitigation plans
- Assign team responsibilities
Estimated duration: 45 minutes
I'm available:
- Monday 2-4 PM
- Wednesday 10 AM - 12 PM
- Friday 1-3 PM
Please let me know what works best for you, or feel free to suggest alternative times.
Best,
[Your name]Good subject lines:
Bad subject lines:
DO:
DON'T:
Subject: Re: [Original subject]
Hi [Name],
Thank you for thinking of me for [request/opportunity].
Unfortunately, I won't be able to [participate/help/attend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].
I appreciate your understanding, and I hope we can collaborate on future opportunities.
Best regards,
[Your name]Subject: Apology and correction: [Issue]
Hi [Name],
I'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.
To correct this:
- [Action 1 already taken]
- [Action 2 in progress]
- [Preventive measure for future]
I understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.
If you have any concerns or questions, please don't hesitate to reach out.
Sincerely,
[Your name]Subject: Great news: [Achievement/milestone]
Team,
I'm excited to share that we've [accomplished goal]!
This success is thanks to:
- [Team/person contribution 1]
- [Team/person contribution 2]
Impact:
- [Metric improvement]
- [Business benefit]
Thank you all for your hard work and dedication. Let's keep up the momentum!
Cheers,
[Your name]Formal:
Professional:
Casual:
© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .claude/skills/email-composer of curiositech/some_claude_skills.
Open the folder on GitHubat commit 6713fc7
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in curiositech/some_claude_skills, which our catalogue first saw on October 7, 2026.
Email Composer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Email Composer this skillcuriositech/some_claude_skills | 243 | 4 repos | ~1.8k | Automated safety check: Pass | MIT | |
| End-of-Life Announcement Writergetcrew44/crew44 | 356 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Write Like Me Bootstrapjxnl/personal-monorepo-template | 562 | — | ~1.1k | Automated safety check: Pass | None | |
| Email Voice Profileyc-software/qm | 15k | — | ~856 | Automated safety check: Pass | MIT | |
| Compose Outreachw95/awesome-claude-corporate-skills | 237 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Email Opsaffaan-m/ECC | 275k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
getcrew44/crew44
Drafts a clear, empathetic end-of-life announcement for a product, feature or plan, covering rationale, customer impact, transition support, timeline and next steps.
jxnl/personal-monorepo-template
Bootstrap a durable "write like me" skill from the user's own Slack and email writing.
yc-software/qm
Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail.
w95/awesome-claude-corporate-skills
Generate personalized outreach messages using Common Room signals.
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
yc-software/qm
Draft Gmail in the user's own voice from the voice profile built by email-voice-profile.
curiositech/some_claude_skills
Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.
curiositech/some_claude_skills
End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.
curiositech/some_claude_skills
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.
curiositech/some_claude_skills
Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.
curiositech/some_claude_skills
Build production computer vision pipelines for object detection, tracking, and video analysis.
curiositech/some_claude_skills
Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…
Categories
Draft professional emails for various contexts including business, technical, and customer communication. Email Composer is an agent skill from curiositech/some_claude_skills. Draft professional emails for various contexts including business, technical, and customer communication.
Email Composer fits situations like: the user needs help writing emails; composing professional messages.
Run `npx skills add curiositech/some_claude_skills --skill email-composer -a claude-code`. Or copy the skill folder (.claude/skills/email-composer in curiositech/some_claude_skills) into .claude/skills/email-composer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add curiositech/some_claude_skills --skill email-composer -a codex`. Or copy the skill folder (.claude/skills/email-composer in curiositech/some_claude_skills) into .agents/skills/email-composer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill email-composer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-composer, .gemini/skills/email-composer, .github/skills/email-composer and .opencode/skills/email-composer in your project.
SKILL.md names no scripts, command-line tools or credentials: Email Composer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Email Composer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Email Composer: End-of-Life Announcement Writer (getcrew44/crew44, 356 stars), Write Like Me Bootstrap (jxnl/personal-monorepo-template, 562 stars), Email Voice Profile (yc-software/qm, 15k stars) and Compose Outreach (w95/awesome-claude-corporate-skills, 237 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on September 6, 2026.
Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.