draft

$npx mdskill add alirezarezvani/gaios/draft

Drafts written communications in the user's voice for emails, messages, or posts

  • Solves the need for quick, personalized drafts of internal or external communications
  • Relies on voice guidelines from references/voice.md and user input
  • Analyzes context, audience, and intent to shape the message structure
  • Delivers ready-to-review drafts with clear call-to-action and open questions

SKILL.md

.github/skills/draftView on GitHub ↗
---
name: draft
description: Use when the user needs a written communication drafted in their voice — an email, a Slack/Teams message, a team update, an announcement, a reply to a thread, or a post. Produces a ready-to-review draft matching references/voice.md; never auto-sends external. Trigger on "/draft", "draft an email", "write a reply", "draft the update", "draft the announcement", "respond to this thread in my voice".
---

# Draft

Turn a brief (or a thread) into a ready-to-send-quality draft in the user's voice — fast, on-register, and honest.

## When to run
- The user needs to write something to a person or a group.
- After `/structure` or `/triage` flags an item that needs a reply.

## The output (always this shape)
```
**To / channel:** <who>  ·  **Type:** email | slack | update | post  ·  **Register:** internal | external
**Subject / opening line:** <if email>

<the draft — in the user's voice (references/voice.md)>

—
Send call: [internal → I can send in your voice]  /  [external → draft only, you send]
Open questions: <anything I assumed or couldn't verify>
```

## Process
1. **Get the brief.** If the ask is fuzzy, frame it first (`/structure`): audience, outcome, and the one thing they should do or know.
2. **Match the voice.** Read `references/voice.md`; mirror the register (internal vs external split). Don't fake the voice on external content.
3. **Draft tight.** Lead with the point or ask. Cut filler. One clear CTA. Length to fit the channel.
4. **Verify every claim (Verification Gate).** Any fact, number, name, date, or commitment in the draft → trace it to source (`context/`, `wiki/`, `/graph-query`, the thread). Anything you can't confirm goes under "Open questions" — never assert it.
5. **Set the send call** per guardrails.

## Autonomy
**L2** — drafts; you MAY send **internal-to-team** in the user's voice. **External is always draft-only** — the human sends.

## Guardrails (from CLAUDE.md)
- **Draft, never auto-send external** (customer / partner / investor / public). Internal team comms may go in the user's voice.
- **Cite, don't invent** — no unverified facts or figures in a draft; flag the gap instead.
- No confidential figures, PHI/PII, or secrets in the draft or the repo.

More from alirezarezvani/gaios

SkillDescription
exec-cockpitTemplate skill for a leadership-transition / executive cockpit — when someone steps into or covers a leadership role and needs to not drop anything. Produces a handoff doc + decision-rights map, an "open loops" tracker, a team-comms cadence, and a recurring report/update drafter. Trigger on "/exec-cockpit", "handoff doc", "decision-rights map", "open loops tracker", "cover for <role>", "interim <role>". Customize the placeholders to your situation.
graphUse when the user wants to build, refresh, or visualize the repo's knowledge graph — code structure plus the committed wiki/ — via graphify. Produces an interactive graph + a GRAPH_REPORT.md of God Nodes, surprising connections, and suggested questions. Trigger on "/graph", "build the knowledge graph", "graph the repo", "map the codebase", "refresh the graph", "visualize the second brain".
graph-ingestUse when the user brings an external source worth keeping — a URL, a paper, a tweet/thread, a blog post, a docs page — and wants it pulled into the second brain. Fetches the source into the git-ignored capture inbox, admits it to the committed wiki through the admission policy, then refreshes the knowledge graph so it joins the rest of your thinking. Trigger on "/graph-ingest", "ingest this url", "add this paper to my knowledge", "add this tweet/page to my knowledge", "capture this source".
graph-queryUse when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".
level-upUse weekly to find and ship one new automation. Walks the 3Ms interview — Mindset (find the candidate) → Method (scope one) → Machine (build it). Trigger on "let's level up", "what should I automate next", "find me leverage this week", or as a Friday ritual. One run = one shipped artifact.
prepUse when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
structureUse when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.