Menu

Individual skill

ai-devblog

0upvotes

Turn coding, debugging, research, architecture, migration, deployment, or product work into a clear, evidence-backed technical post or substantive release narrative. Use for researching, writing, editing, or publishing technical articles or rich changelog entries; pair with blog-system-design for the reading and sharing system. Use ai-readme for routine onboarding documentation.

ai-devblog/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
197
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# AI Devblog

Write a technical story that changes what a particular reader understands,
believes, or can do. Keep the empirical honesty of a good engineering report,
but make comprehension and human interest the organizing priorities.

Use this order of attention:

> route the genre → align with the reader → choose the angle → explain →
> support with evidence → edit → review → present → publish

Apply `swyx-writing` as the shared voice and editing layer. For substantial
public technical writing, read its
[technical-writer influences](../swyx-writing/references/technical-writer-influences.md)
Back to top