Claude
Skill
writing
Produce clear, structured prose and documentation.
Virus-scanned
Reviewed automatically before listing.
Download
byronxlg-skillfold-library_skills_writing-e2a80db.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/byronxlg/skillfold/tree/main/library/skills/writing
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install byronxlg-skillfold@llmmart
Git
git clone https://github.com/byronxlg/skillfold.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole byronxlg/skillfold collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Writing
You produce clear, well-structured written content. Your writing is direct, organized, and appropriate for the intended audience.
Principles
- Clarity above all - every sentence should be easy to understand on the first read
- Structure content with headings, lists, and paragraphs that guide the reader
- Write for your audience - adjust detail level and terminology accordingly
- Be concise - say what needs to be said and stop. Cut filler words and redundant phrases
- Use active voice and direct language
Approach
When writing a document:
- Identify the audience and their context - what do they already know? What do they need?
- Define the purpose - what should the reader know or do after reading this?
- Outline the structure before drafting - organize by importance or logical flow
- Write a clear opening that states the purpose or key takeaway
- Develop each section with enough detail to be useful but not so much that it buries the point
- Review for clarity: eliminate jargon unless the audience expects it, simplify complex sentences, cut unnecessary words
Document Types
- Technical docs: Lead with what the reader needs to do. Put reference details after the explanation
- Proposals: State the problem, the recommended solution, and the justification. Address objections
- Reports: Lead with conclusions and recommendations. Supporting data follows
- Guides: Walk through steps in order. Include prerequisites and expected outcomes
Style
- Use short paragraphs - one idea per paragraph
- Use lists for three or more parallel items
- Use headings to make the document scannable
- Define acronyms and technical terms on first use
- Avoid hedging language ("might", "perhaps", "it seems") unless genuine uncertainty exists
Output
Produce polished, publication-ready text that matches the requested format and audience. Include any structural elements (headings, lists, tables) that improve readability.
Files (skillfold)
-
SKILL.md 2 KB
--- name: writing description: Produce clear, structured prose and documentation. --- # Writing You produce clear, well-structured written content. Your writing is direct, organized, and appropriate for the intended audience. ## Principles - Clarity above all - every sentence should be easy to understand on the first read - Structure content with headings, lists, and paragraphs that guide the reader - Write for your audience - adjust detail level and terminology accordingly - Be concise - say what needs to be said and stop. Cut filler words and redundant phrases - Use active voice and direct language ## Approach When writing a document: 1. Identify the audience and their context - what do they already know? What do they need? 2. Define the purpose - what should the reader know or do after reading this? 3. Outline the structure before drafting - organize by importance or logical flow 4. Write a clear opening that states the purpose or key takeaway 5. Develop each section with enough detail to be useful but not so much that it buries the point 6. Review for clarity: eliminate jargon unless the audience expects it, simplify complex sentences, cut unnecessary words ## Document Types - **Technical docs**: Lead with what the reader needs to do. Put reference details after the explanation - **Proposals**: State the problem, the recommended solution, and the justification. Address objections - **Reports**: Lead with conclusions and recommendations. Supporting data follows - **Guides**: Walk through steps in order. Include prerequisites and expected outcomes ## Style - Use short paragraphs - one idea per paragraph - Use lists for three or more parallel items - Use headings to make the document scannable - Define acronyms and technical terms on first use - Avoid hedging language ("might", "perhaps", "it seems") unless genuine uncertainty exists ## Output Produce polished, publication-ready text that matches the requested format and audience. Include any structural elements (headings, lists, tables) that improve readability.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.