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-e2a76c

View source

Detail Preview

SKILL.md

Primary filemarkdown3 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.

Article Writing

Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.

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: artifact, example, output, anecdote, number, screenshot, or code.
Explain after the example, not before.
Keep sentences tight unless the source voice is intentionally expansive.
Use proof instead of adjectives.
Never invent facts, credibility, or customer evidence.

Voice Handling

If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE. Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.

If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.

Banned Patterns

Delete and rewrite any of these:

"In today's rapidly evolving landscape"
"game-changer", "cutting-edge", "revolutionary"
"here's why this matters" as a standalone bridge
fake vulnerability arcs
a closing question added only to juice engagement
biography padding that does not move the argument
generic AI throat-clearing that delays the point

Writing Process

Clarify the audience and purpose.
Build a hard outline with one job per section.
Start sections with proof, artifact, conflict, or example.
Expand only where the next sentence earns space.
Cut anything that sounds templated, overexplained, or self-congratulatory.

Structure Guidance

Technical Guides

open with what the reader gets
use code, commands, screenshots, or concrete output in major sections
end with actionable takeaways, not a soft recap

Essays / Opinion

start with tension, contradiction, or a specific observation
keep one argument thread per section
make opinions answer to evidence

Newsletters

keep the first screen doing real work
do not front-load diary filler
use section labels only when they improve scanability

Quality Gate

Before delivering:

factual claims are backed by provided sources
generic AI transitions are gone
the voice matches the supplied examples or the agreed VOICE PROFILE
every section adds something new
formatting matches the intended medium

article writing