writing_skill

Overview

This skill turns raw notes, outlines, or research into technical articles and long-form pieces that read like a human wrote them. It avoids common AI writing tells and follows a clear template so the output feels personal, opinionated, and practical. Use it when authenticity matters for tutorials, case studies, or blog posts.

How this skill works

You provide a topic, audience, desired length, and any raw material or an outline. The skill applies a writing philosophy that mixes prose and bullets, varies sentence length, and enforces a vocabulary blacklist to remove mechanical phrasing. It produces a full draft with at least one numeric claim and one concrete before/after example, plus a TL;DR and a closing with a clear point of view.

When to use it

• Turning interview notes into a 800–1,200 word case study for engineering teams
• Drafting a tutorial that must feel like a personal walkthrough, not a manual
• Producing a blog post that includes opinions, tradeoffs, and measurable results
• Converting research findings into an accessible long-form article for non-experts
• Preparing content that must pass human review or low-risk detection checks

Best practices

• Provide a short hook (1–2 sentences) explaining why the topic matters to you
• Give at least 3 raw examples or metrics so the draft can include specific numbers
• Ask for a target audience and publication context (newsletter, blog, docs)
• Request before/after text snippets for any stylistic changes you want shown
• Limit high-level constraints to 2–3 items so voice and rhythm remain natural

Example use cases

• A 900-word tutorial that shows step-by-step config changes with code snippets
• A 1,200-word case study with before/after performance numbers (e.g., 40% speedup)
• A long-form opinion piece that states tradeoffs and names the tools used
• An onboarding essay for a team that narrates a migration and its surprising results