Skip to content
Agentmart
Submit a tool

writing-assistant

Help write, edit, and improve various types of content.

Skill by CraftOS-dev

IndexedMIT★ 400
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/craftos-dev-writing-assistant

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Help write, edit, and improve various types of content. Use when writing emails, documents, messages, or any text content that needs drafting or polishing.

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/writing-assistant

What's inside

Skill 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.
License
MIT
Instructions
116 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# 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:
1. Executive summary / Introduction
2. Background / Context
3. Main content / Analysis
4. Conclusions / Recommendations
5. Next steps / Action items

### 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

From CraftOS-dev/CraftBot, MIT.

More from CraftOS-dev/CraftBot

Signals

Stars
400
Forks
49
Open issues
12
Last commit (this folder)
Feb 16, 2026 (8 months ago)
Last release
Oct 23, 2026 (6 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from CraftOS-dev

Cite this page

writing-assistant skill. Agent Mart. https://agentmart.dev/skills/craftos-dev-writing-assistant (last updated 2026-10-24)