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.
Best use case
article-writing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using article-writing 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/article-writing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How article-writing Compares
| Feature / Agent | article-writing | 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?
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.
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
# Article Writing Write long-form content that sounds like a real person or brand, not generic AI output. ## When to Activate - drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues - turning notes, transcripts, or research into polished articles - matching an existing founder, operator, or brand voice from examples - tightening structure, pacing, and evidence in already-written long-form copy ## Core Rules 1. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block. 2. Explain after the example, not before. 3. Prefer short, direct sentences over padded ones. 4. Use specific numbers when available and sourced. 5. Never invent biographical facts, company metrics, or customer evidence. ## Voice Capture Workflow If the user wants a specific voice, collect one or more of: - published articles - newsletters - X / LinkedIn posts - docs or memos - a short style guide Then extract: - sentence length and rhythm - whether the voice is formal, conversational, or sharp - favored rhetorical devices such as parentheses, lists, fragments, or questions - tolerance for humor, opinion, and contrarian framing - formatting habits such as headers, bullets, code blocks, and pull quotes If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype. ## Banned Patterns Delete and rewrite any of these: - generic openings like "In today's rapidly evolving landscape" - filler transitions such as "Moreover" and "Furthermore" - hype phrases like "game-changer", "cutting-edge", or "revolutionary" - vague claims without evidence - biography or credibility claims not backed by provided context ## Writing Process 1. Clarify the audience and purpose. 2. Build a skeletal outline with one purpose per section. 3. Start each section with evidence, example, or scene. 4. Expand only where the next sentence earns its place. 5. Remove anything that sounds templated or self-congratulatory. ## Structure Guidance ### Technical Guides - open with what the reader gets - use code or terminal examples in every major section - end with concrete takeaways, not a soft summary ### Essays / Opinion Pieces - start with tension, contradiction, or a sharp observation - keep one argument thread per section - use examples that earn the opinion ### Newsletters - keep the first screen strong - mix insight with updates, not diary filler - use clear section labels and easy skim structure ## Quality Gate Before delivering: - verify factual claims against provided sources - remove filler and corporate language - confirm the voice matches the supplied examples - ensure every section adds new information - check formatting for the intended platform
Related Skills
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
wp-performance
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
wp-interactivity-api
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
wp-block-themes
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
wp-block-development
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
wp-abilities-api
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.