About writing-tech-post
writing-tech-post is a skill for drafting, revising, outlining, and reviewing engineering posts. It helps technical authors shape material around supported evidence, explain mechanisms and impact, and avoid treating editorial heuristics as mandatory rules.
Key features
- 01Develop posts, outlines, rewrites, and reviews
- 02Identify readers, main points, and supported facts
- 03Choose structures suited to the material
- 04Ground technical claims in evidence
- 05Review publication claims and disclosures
- 06Run an optional heuristic linter
Use cases
- 01Outlining a new engineering article
- 02Revising an existing technical draft
- 03Explaining a performance or security issue
- 04Checking claims before external publication
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/writing-tech-postin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
assets/evidence-block.snippets.mdfrontmatter.template.mdoutline.ai-agent-post.mdoutline.launch-deep-dive.mdoutline.migration.mdoutline.performance.mdoutline.postmortem.mdoutline.research-translation.mdoutline.security-disclosure.mdoutline.tutorial.mdreferences/ai-and-agents.mdanti-patterns.mdarchetypes-and-structure.mddepth-and-abstraction.mdevidence-diagrams-code.mdmigrations.mdnarrative-and-pacing.mdperformance-deep-dive.mdpostmortems.mdpre-publish-checklist.mdpublisher-voice-matrix.mdsecurity-and-reliability.mdvoice-and-disclosure.mdscripts/lint-post.pyvalidate-metadata.pyDetails
From the project READMEWriting 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.
- Establish the reader, main point, and supported facts from available context. Ask only for missing information that materially affects the requested output.
- 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.
- 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.
- 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.
- Before external publication, apply
references/pre-publish-checklist.mdto 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. - Evidence/assets:
references/evidence-diagrams-code.md; narrative:references/narrative-and-pacing.md. - Voice/disclosure:
references/voice-and-disclosure.md; a requested publisher register:references/publisher-voice-matrix.md; specific prose problems:references/anti-patterns.md.
Use an assets/outline.<archetype>.md template only when useful; omit irrelevant sections. Run helpers through this skill's absolute directory: python3 <writing-tech-post-dir>/scripts/lint-post.py <draft.md>. --strict makes heuristic warnings fail for an explicitly chosen editorial gate. A clean lint result does not prove factuality or disclosure readiness.