Skill Introduction

Overview

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.

Core value

Turns reusable Documentation know-how into an installable skill, helping users complete github, community work faster.

Target users

Developers, testers, and maintainers who handle Documentation tasks in Focus Code.
Teams that already trust workflows or content from affaan-m.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Documentation, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install article-writing-0a4dc2

View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: article-writing description: 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. origin: ECC

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

Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
Explain after the example, not before.
Prefer short, direct sentences over padded ones.
Use specific numbers when available and sourced.
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

Clarify the audience and purpose.
Build a skeletal outline with one purpose per section.
Start each section with evidence, example, or scene.
Expand only where the next sentence earns its place.
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

article writing