Skip to content
Skills Library
Personal productivity · Writing

draft

/draft

Use when writing text another person will read: a message, an e-mail, a ticket or PR comment, a reply to a client or teammate.

Repository
make-it ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when writing text another person will read: a message, an e-mail, a ticket or PR comment, a reply to a client or teammate.

Original author description

Use when writing text another person will read: a message, an e-mail, a ticket or PR comment, a reply to a client or teammate.

How it works

SKILL.md has no level-two headings · 16 lines, 240 words

SKILL.md preview
---
name: draft
description: "Use when writing text another person will read: a message, an e-mail, a ticket or PR comment, a reply to a client or teammate."
---

# Draft text for a person

The reader is a person, not you. They have not seen the repo, the session or your notes. Write what they need, in their words.

Rules:

- Plain text, ready to paste. Complete: no "...", no [placeholders], no alternatives or variants. If a fact is missing, pick the neutral wording that needs no fact; do not leave a gap.
- The recipient's language: the one of the mail or thread you are answering, not the language the owner wrote to you in.
- The owner's register: direct, plain, factual. Match the thread's tu or vous. No filler apology, no marketing.
- No file paths, function or branch names, code references, Markdown (no bold, headings, bullets, backticks) and no emojis. Say what happened and what it means for the reader (the date, the cause in a sentence, what they can do meanwhile).
- Sign with the owner's name if you know it; otherwise end on the closing line, with no placeholder.
- Use the repo and notes for facts, never as content to quote.

Output: one line "Draft:" that marks where the text begins and is not part of it (the owner copies only what follows), then the text, and nothing after it. Show it once. Do not summarise it, explain your choices or list what you checked. If something must be verified before sending, put it before the "Draft:" line in one short sentence.

Versions

RepositoryScoreLicence
This page · youssefKadaouiAbbassi/make-it86MIT
tony/skills100MIT
eclecticv/skills100MIT
drafthq/draft100MIT
gagoar/foghorn100MIT
anthropics/claude-for-legal100Apache-2.0
tance-mang/chinese-webnovel-skills100MIT
alirezarezvani/gaios100MIT
lawdroidai/legal-aid-plugin100Apache-2.0

Database snapshot: 13.11.2026 · package version c28ca109b2e3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100comment
    Use when posting a comment on a GitHub pull request or issue, including review comments and thread replies.
  • 86draft-with-my-context
    Draft everyday writing that needs the user's own information — emails, replies, bios, LinkedIn or X posts, short statements, intros for a meeting, progress updates, abstracts or talk descriptions. Use when asked to write, reply, draft, introduce, update or summarise something…
  • 100writing-style
    Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.
  • 100pr-comment-reply
    Render the canonical reply text for a PR review comment. Use when drafting, writing, or posting a "PR comment reply", "review comment reply", "reply to this comment", "respond to this review comment", "answer the reviewer", "reply on the PR thread", or any text bound for `gh…
  • 100draft-message
    Draft a message, email, or reply in the user's voice and show it for review before anything is sent. Use for "text Sarah that I'm running late", "draft an email to the team", "reply saying yes", or composing a note to someone. Triggers: text, message, email, reply, draft, tell…
  • 100write-human
    Draft or edit writing a person will send or publish as themselves: texts, WhatsApp and DMs, emails, replies, LinkedIn messages, introductions and first approaches, client updates, cover notes, posts and short professional documents, so it sounds like them, not like an AI. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.