Agent skill

Writing Assistant

Help write, edit, and improve various types of content. An agent skill from CraftOS-dev/CraftBot.

MITAuto-check passed

Install Writing Assistant

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot writing-assistant --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing-assistant .claude/skills/writing-assistant && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "writing-assistant" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant into .claude/skills/writing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-assistant", 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

$skill-installer install https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant

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

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot writing-assistant --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing-assistant .agents/skills/writing-assistant && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "writing-assistant" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant into .agents/skills/writing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-assistant", 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.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot writing-assistant --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing-assistant .cursor/skills/writing-assistant && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "writing-assistant" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant into .cursor/skills/writing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-assistant", 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

$ gemini skills install https://github.com/CraftOS-dev/CraftBot.git --path skills/writing-assistant

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot writing-assistant --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing-assistant .gemini/skills/writing-assistant && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "writing-assistant" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant into .gemini/skills/writing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-assistant", 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.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot writing-assistant

Installs 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).

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing-assistant .github/skills/writing-assistant && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "writing-assistant" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant into .github/skills/writing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-assistant", 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.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot writing-assistant --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing-assistant .opencode/skills/writing-assistant && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "writing-assistant" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/writing-assistant into .opencode/skills/writing-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-assistant", 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.

Facts

Skill name: writing-assistant
GitHub stars: 392
Token cost: ~845 tokens
SKILL.md length: 370 words
Files: 1
Skills in repo: 89
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Help write, edit, and improve various types of content. An agent skill from CraftOS-dev/CraftBot.

Works in 3 steps: Understand the Context → Draft the Content → Refine and Polish
Any text content that needs drafting
SKILL.md covers When to Use, Writing Process, Content Types and Tone Guidelines, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Writing Assistant is an agent skill from CraftOS-dev/CraftBot. Help write, edit, and improve various types of content. Use when writing emails, documents, messages, or any text content that needs drafting or polishing.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: One agent. Every kind of work. The licence is MIT.

When your agent uses it

Any text content that needs drafting

Example prompts

“/writing-assistant”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Understand the Context
Draft the Content
Refine and Polish

What it can do on your machine

Read from SKILL.md and the folder at commit b50970c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Writing Assistant loads about 845 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 370 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~845

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from CraftOS-dev/CraftBot at commit b50970c, republished under its MIT licence (© CraftOS-dev). 370 words, ~845 tokens.

Download SKILL.mdSave it as .claude/skills/writing-assistant/SKILL.md (or your agent's skills folder).

name: writing-assistant
description: Help write, edit, and improve various types of content. Use when writing emails, documents, messages, or any text content that needs drafting or polishing.
user-invocable: true
action-sets: file_operations

Writing Assistant

Help users create, edit, and refine written content for various purposes.

When to Use

Drafting emails (professional, personal, follow-ups)
Writing messages (formal or casual)
Creating documents (reports, proposals, summaries)
Editing existing text for clarity or tone
Translating content between styles

Writing Process

Step 1: Understand the Context

Before writing, clarify:

Purpose: What should this accomplish?
Audience: Who will read this?
Tone: Formal, casual, friendly, urgent?
Length: Brief or detailed?
Key points: What must be included?

Step 2: Draft the Content

Create an initial draft that:

Opens with the main point or purpose
Organizes information logically
Includes all necessary details
Ends with clear next steps or call-to-action

Step 3: Refine and Polish

Check for clarity and conciseness
Adjust tone to match audience
Remove unnecessary words
Ensure proper grammar and spelling
Verify all key points are covered

Content Types

Professional Emails

Subject: [Clear, specific subject]

Hi [Name],

[Purpose statement - why you're writing]

[Key details or request]

[Next steps or call to action]

Best regards,
[Your name]

Tips:

Keep subject lines under 50 characters
Lead with the most important information
Be specific about any requests or deadlines
Use bullet points for multiple items

Casual Messages

Match the recipient's communication style
Be conversational but clear
Use appropriate greetings for the relationship
Keep it brief unless detail is needed

Formal Documents

Structure:

Executive summary / Introduction
Background / Context
Main content / Analysis
Conclusions / Recommendations
Next steps / Action items

Show full SKILL.md (157 more words)Show less

Thank You Notes

Be specific about what you're thanking them for
Mention the impact or why it mattered
Keep it genuine and personal
Send promptly

Tone Guidelines

Tone	Use When	Characteristics
Formal	Business proposals, official requests	Complete sentences, no contractions, professional vocabulary
Professional	Work emails, client communication	Friendly but polished, clear and direct
Casual	Colleagues, friends	Conversational, contractions OK, relaxed
Urgent	Time-sensitive matters	Clear deadlines, action-oriented, concise
Apologetic	Mistakes, delays	Acknowledge issue, take responsibility, offer solution

Editing Checklist

Is the main point clear in the first paragraph?
Is the tone appropriate for the audience?
Are there any unnecessary words or sentences?
Is the call-to-action clear?
Is the length appropriate?
Are grammar and spelling correct?
Would I be happy to receive this?

Common Improvements

Too long → Cut filler words, combine sentences
Too formal → Use contractions, simpler words
Too casual → Remove slang, add structure
Unclear → Lead with the main point, use bullet points
No action → Add clear next steps

Files

Just SKILL.md in skills/writing-assistant of CraftOS-dev/CraftBot.

Open the folder on GitHubat commit b50970c

Compare with similar skills

Writing Assistant 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.

Writing Assistant compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Writing Assistant this skillCraftOS-dev/CraftBot	392	—	~845	Automated safety check: Pass	MIT	yesterday
Rust Path Typesopeninterpreter/openinterpreter	69k	2 repos	~605	Automated safety check: Pass	Apache-2.0	yesterday
Python Type Safetywshobson/agents	40k	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Pyrefly Type Coveragepytorch/pytorch	104k	—	~3k	Automated safety check: Pass	Custom licence	today
Typescript Advanced Typesrolling-scopes/rsschool-app	10k	25 repos	~4.2k	Automated safety check: Pass	MPL-2.0	4 days ago
API Typessupabase/supabase	111k	—	~557	Automated safety check: Pass	Apache-2.0	today

Similar skills

Rust Path Types
openinterpreter/openinterpreter
Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.
69k GitHub starsUsed in 2 repos~605 tokens
DevelopmentAuto-check passed
Python Type Safety
wshobson/agents
Python type safety with type hints, generics, protocols, and strict type checking.
40k GitHub stars~1.4k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Pyrefly Type Coverage
pytorch/pytorch
Migrate a file to use stricter Pyrefly type checking with annotations required for all functions, classes, and attributes.
104k GitHub stars~3k tokensUpdated today
DevelopmentAuto-check passed
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
10k GitHub starsUsed in 25 repos~4.2k tokens
DevelopmentAuto-check passed
API Types
supabase/supabase
Official
Maintain Supabase API types. An agent skill from supabase/supabase.
111k GitHub stars~557 tokensUpdated today
Backend & APIsAuto-check passed
Twenty Syncable Entity Types
twentyhq/twenty
Walks through the first of six steps for adding a syncable entity to Twenty's server: metadata name, TypeORM entity, flat types and central constants.
58k GitHub stars~2.8k tokensUpdated today
DevelopmentAuto-check passed

Questions about Writing Assistant

What does Writing Assistant do?

Help write, edit, and improve various types of content. An agent skill from CraftOS-dev/CraftBot. Writing Assistant is an agent skill from CraftOS-dev/CraftBot. Help write, edit, and improve various types of content.

When should I use Writing Assistant?

Writing Assistant fits situations like: any text content that needs drafting.

How do I install Writing Assistant in Claude Code?

Run `npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a claude-code`. Or copy the skill folder (skills/writing-assistant in CraftOS-dev/CraftBot) into .claude/skills/writing-assistant in your project. Claude Code loads it when a task matches its description.

How do I install Writing Assistant in Codex?

Run `npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a codex`. Or copy the skill folder (skills/writing-assistant in CraftOS-dev/CraftBot) into .agents/skills/writing-assistant in your project. Codex loads it when a task matches its description.

Can I use Writing Assistant in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CraftOS-dev/CraftBot --skill writing-assistant -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-assistant, .gemini/skills/writing-assistant, .github/skills/writing-assistant and .opencode/skills/writing-assistant in your project.

What does Writing Assistant need to run?

SKILL.md names no scripts, command-line tools or credentials: Writing Assistant is instructions for the agent only.

Does Writing Assistant access the network?

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.

Is Writing Assistant safe to install?

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.

What licence does Writing Assistant use?

Writing Assistant is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Writing Assistant use?

About 845 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Writing Assistant?

Skills that share tags, products or a category with Writing Assistant: Rust Path Types (openinterpreter/openinterpreter, 69k stars), Python Type Safety (wshobson/agents, 40k stars), Pyrefly Type Coverage (pytorch/pytorch, 104k stars) and Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing Assistant?

CraftOS-dev (a GitHub user) maintains it in CraftOS-dev/CraftBot, which has 392 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 7, 2026.

Source: CraftOS-dev/CraftBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Writing Assistant

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Writing Assistant

When to Use

Writing Process

Step 1: Understand the Context

Step 2: Draft the Content

Step 3: Refine and Polish

Content Types

Professional Emails

Casual Messages

Formal Documents

Thank You Notes

Tone Guidelines

Editing Checklist

Common Improvements

Files

Compare with similar skills

Similar skills

More from CraftOS-dev/CraftBot

Questions about Writing Assistant