long-form-article
Long-Form Article
This skill produces one long guide that a reader finishes, saves and acts on. Done means a draft where the point fits in one sentence, every number names who measured it and when, the reader can do something this week, the honest sections are there ("what breaks", the vendor-data caveat), and every line that needs the author's OK is flagged.
Length earns its place only when a reader can repeat the point, check every number and act on it. Without those three, 4,000 words is a blog post with padding. The structure below is the one that held up across real articles; it works for an opportunity playbook, a how-to for buyers, and a guide a local business writes for its customers. This is a floor, not a ceiling. When the piece in front of you argues for a better shape, take it and say why in one line.
Context
Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run:
python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for long-form-article
(${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this file was read from, e.g. .agents/skills/long-form-article. If the script or python3 is unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active names one, else ./brand/; then MARKETING.md, preferences.md and the files in reads:. If none exist, proceed standalone and ask only for the point, the reader and the platform.)
voice-profile governs how it sounds; positioning#chosen-angle keeps the piece on the author's lane; audience#pain-language supplies the reader's own words for the title and the opening. Apply any [long-form-article] learnings (which titles, sections or links performed). One that changed the piece gets one line in the Sources and assumptions note, only if it did.