writing-clearly-and-concisely
Core writing rules for clear, concise prose. Load when writing any text a human will read.
Best use case
writing-clearly-and-concisely is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Core writing rules for clear, concise prose. Load when writing any text a human will read.
Teams using writing-clearly-and-concisely should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/writing-clearly-and-concisely/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How writing-clearly-and-concisely Compares
| Feature / Agent | writing-clearly-and-concisely | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Core writing rules for clear, concise prose. Load when writing any text a human will read.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Writing Clearly and Concisely ## Principles Apply to all prose: documentation, commit messages, reports, explanations, UI text. 1. **Active voice.** "The team fixed the bug" not "The bug was fixed by the team." Active is shorter, clearer, stronger. 2. **Positive form.** Say what is, not what isn't. "He usually came late" not "He was not very often on time." 3. **Concrete language.** Specific beats abstract. "It rained every day for a week" not "A period of unfavourable weather set in." 4. **Omit needless words.** Every sentence earns its place. Cut "the fact that", "in order to", "it should be noted that", "there is/are". A sentence needs no unnecessary words, a paragraph no unnecessary sentences. 5. **Emphatic endings.** Place the most important word or phrase at the end of the sentence. 6. **Parallel structure.** Express co-ordinate ideas in similar form. ## AI Patterns to Avoid LLMs regress to statistical means, producing generic, inflated prose. Recognise and eliminate: **Banned words and phrases** - these are LLM tells: pivotal, crucial, vital, testament, enduring legacy, indelible mark, nestled, in the heart of, groundbreaking, seamless, robust, cutting-edge, delve, leverage, multifaceted, foster, realm, tapestry, vibrant, nuanced, intricate, intricacies, interplay, landscape (figurative), garnered, underpinning, underscores, showcasing, streamline, aligns with **Banned patterns:** - Superficial "-ing" analysis: "ensuring reliability", "highlighting its importance", "showcasing features", "reflecting broader trends" - Puffery about significance: "plays a vital role", "stands as a testament", "marking a pivotal moment" - Didactic disclaimers: "it's important to note", "it's worth mentioning" - Empty conclusions: "In summary", "Overall", "In conclusion" followed by restatement - Rule of three for padding: "adjective, adjective, and adjective" when one would do - Negative parallelisms: "not just X, but Y" and "not only X, but also Y" ## Before and After <example_bad> The configuration system plays a crucial role in ensuring seamless deployment across environments, showcasing the framework's robust architecture and highlighting its commitment to developer experience. </example_bad> <example_good> The configuration system deploys consistently across environments. </example_good> <example_bad> It's important to note that this feature leverages a multifaceted approach, delving into the intricacies of the underlying architecture to foster a more streamlined workflow. </example_bad> <example_good> This feature reduces deployment steps from five to two. </example_good> ## Heavy Reference For extended writing tasks (documentation, blog posts, technical guides), load `prose-style-reference` for the full Strunk composition rules and expanded AI pattern catalogue.
Related Skills
llm-security
Security guidelines for LLM applications based on OWASP Top 10 for LLM 2025. Use when building LLM apps, reviewing AI security, implementing RAG systems, or asking about LLM vulnerabilities like 'prompt injection' or 'check LLM security'. IMPORTANT: Always consult this skill when building chatbots, AI agents, RAG pipelines, tool-using LLMs, agentic systems, or any application that calls an LLM API (OpenAI, Anthropic, Gemini, etc.) — even if the user doesn't explicitly mention security. Also use when users import 'openai', 'anthropic', 'langchain', 'llamaindex', or similar LLM libraries.
semgrep
Run Semgrep static analysis scans and create custom detection rules. Use when asked to scan code with Semgrep, find security vulnerabilities, write custom YAML rules, or detect specific bug patterns. IMPORTANT: Also use this skill when users ask to 'scan for bugs', 'check code quality', 'find vulnerabilities', 'static analysis', 'lint for security', 'audit this code', or want to enforce coding standards — even if they don't mention Semgrep by name. Semgrep is the right tool for pattern-based code scanning across 30+ languages.
meet-the-agents
Registry of available specialist agents and their task domains. Load when delegating a task, selecting an agent, or unsure which agent to use.
gh
Load when executing GitHub tasks via the gh CLI: creating or reviewing pull requests, managing issues, checking CI runs, creating releases, searching GitHub, or making raw GitHub API calls.
prose-style-reference
Extended writing reference for documentation and content creation. Load for blog posts, READMEs, technical guides, and long-form writing.
code-security
Security guidelines for writing secure code. Use when writing code, reviewing code for vulnerabilities, or asking about secure coding practices like 'check for SQL injection' or 'review security'. IMPORTANT: Always consult this skill when writing or reviewing any code that handles user input, authentication, file operations, database queries, network requests, cryptography, or infrastructure configuration (Terraform, Kubernetes, Docker, GitHub Actions) — even if the user doesn't explicitly mention security. Also use when users ask to 'review my code', 'check this for bugs', or 'is this safe'.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
copywriting
Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.
blog-writing-guide
This skill enforces Sentry's blog writing standards across every post — whether you're helping an engineer write their first blog post or a marketer draft a product announcement.
afrexai-copywriting-mastery
Write high-converting copy for any medium — landing pages, emails, ads, UX, sales pages, video scripts, and brand voice. Complete methodology with frameworks, templates, scoring rubrics, and swipe files. Use when writing or reviewing any user-facing text.
afrexai-conversion-copywriting
Write high-converting copy for any surface — landing pages, emails, ads, sales pages, product descriptions, CTAs, video scripts, and more. Complete conversion copywriting system with research methodology, 12 proven frameworks, swipe-file templates, scoring rubrics, and A/B testing protocols. Use when you need to write or review any copy meant to drive action.
human-writing
Guidelines and standards for professional, human-like writing and documentation. Use this skill when generating READMEs, technical documentation, code comments, or any formal written output to avoid common AI 'tells', buzzwords, and stylistic tropes. Ensure content follows the 'Professional Human in the Field' standard: high precision, zero fluff, and no emojis in technical contexts.