craftos-dev/craftbot

writing-assistant

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

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/craftos-dev/craftbot --skill writing-assistant

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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

ToneUse WhenCharacteristics
FormalBusiness proposals, official requestsComplete sentences, no contractions, professional vocabulary
ProfessionalWork emails, client communicationFriendly but polished, clear and direct
CasualColleagues, friendsConversational, contractions OK, relaxed
UrgentTime-sensitive mattersClear deadlines, action-oriented, concise
ApologeticMistakes, delaysAcknowledge 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

Tâches connexes