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 Use - 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
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Gemini CLI or understanding what capabilities are actually available in their environment.
visa-doc-translate
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.
video-editing
AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.
verification-loop
Comprehensive verification system for code changes
unified-notifications-ops
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
terminal-ops
Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
team-builder
Interactive agent picker for composing and dispatching parallel teams
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.