사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/craftos-dev/craftbot --skill writing-assistant시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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
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
