email-writer
Draft clear, well-structured emails — replies, outreach, and follow-ups — in the right tone.
git clone --depth 1 https://github.com/holaboss-ai/holaOS /tmp/email-writer && cp -r /tmp/email-writer/apps/desktop/electron/default-skills/email-writer ~/.claude/skills/email-writerSKILL.md
# Email Writer
Write the email the reader can answer in one pass. Most email fails not on grammar but on clarity of ask: the recipient can't tell what you want, by when, or why it matters to them. Fix that first; everything else is polish.
## When to use this skill
Use Email Writer to draft or rewrite a single email — a reply, a cold or warm outreach, a follow-up, an update, a request. For multi-send marketing sequences and campaigns, use Email Marketing instead; for internal announcements to a whole team, use Internal Comms.
## Principles
- **One email, one job.** Lead with the purpose. If you're asking for something, make the ask explicit and easy to say yes to.
- **Front-load.** The recipient should get the point from the first two lines, before any context.
- **Respect their time.** Short by default. Cut throat-clearing ("I hope this finds you well…") unless the relationship calls for it.
- **Match the register.** Cold outreach, a peer reply, and a note to an exec are three different tones. Ask or infer the relationship and adjust formality, warmth, and length.
- **Make next steps concrete.** Propose a specific time, a clear deliverable, or a single question — not "let me know your thoughts."
## How to work
1. Establish the goal (what response do you want?), the recipient, and the relationship/tone.
2. Draft a subject line that states the point, not a vague topic.
3. Open with the ask or headline, add only the context that earns the yes, and close with a concrete next step.
4. Trim: remove hedges, filler, and anything the reader doesn't need to act.
## Output format
Return a **subject line** and the **body**. Keep paragraphs short. If useful, offer one alternative tone (e.g. warmer or more direct) rather than a single fixed draft.Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.
Use when working in the embedded browser and you want the cheapest reliable interaction loop.
Use when validating or debugging a workflow in the embedded browser and you need a reproducible, evidence-first loop.
Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a `src/client/` UI surface. NOT for marketing pages, NOT for snapshot HTML reports.
Provision a production-ready teammate only after its stable responsibilities, prerequisites, and reusable operating guidance are understood.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
Add or update workspace MCP servers using holaOS mcp_registry syntax.