Agent skill · writing content · pedronauck
writing-tech-post
Write or edit engineering posts with supported claims. Use for drafts, rewrites, and publication reviews; excludes marketing pages, API references, release notes, and internal specs.
Why this skill is useful
Provides structured guidance on writing technical blog posts with specific archetypes and evidence requirements that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Writing Engineering Posts Produce the requested artifact: a new post, an outline, a focused rewrite, or a publication review. Reuse the accepted brief and evidence. Choose a structure that fits the reader and material; a small edit does not restart an entire authoring workflow. 1. Establish the reader, main point, and supported facts from available context. Ask only for missing information that materially affects the requested output. 2. For a new post, choose a useful primary archetype and outline. For an existing draft, retain working structure and edit the requested scope. Frontmatter, rung labels, depth tuples, and per-section evidence plans are optional tools unless the publisher requires them. 3. Explain the mechanism and why it matters. Support quantitative, comparative, security, and capability claims with appropriate evidence and limitations. Distinguish actual measurements, illustrative examples, hypotheses, and work still in progress. 4. Refine voice and flow where needed. Publisher style matrices, H2 question chains, and first/last-200-word comparisons are editorial heuristics, not universal gates. Do not invent failed mitigations, partial victories, benchmark results, or lessons to satisfy an arc. 5. Before external publication, apply references/pre-publish-checklist.md to the relevant claims and disclosure obligations. Draft delivery is not publication authorization. The optional linter reports heuristics; human factual review owns unsupported claims and disclosure decisions. Reference router Read the reference for the current archetype or editing concern, not every phase: Structure: references/archetypes-and-structure.md; optional depth diagnosis: references/depth-and-abstraction.md. Incident: references/postmortems.md; migration: references/migrations.md; performance: references/performance-deep-dive.md. AI/agents: references/ai-and-agents.md; security/reliability: references/security-and-reliability.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/writing-tech-post