Menu

Individual skill

write-blog

0upvotes

Write and ship a blog post for your project that reads like a human wrote it and pulls SEO traffic to your site. Use when a contributor wants to draft, edit, or publish a blog post, add a post to the site, write about the project for search/traction, or make an existing draft sound less like AI. Enforces the house voice (no em dashes), picks a non-cannibalizing angle, uses ASD-STE100 Simplified Technical English for technical prose, wires the post into your site, and runs the humanizer pass before shipping.

skills/write-blog/SKILL.md

Read pinned source

Source commit 1be9984bdafbb68eaff400bdd82773a1d41ee7ec

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 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)
228
Repository last updated
Aug 16, 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

# Write a blog post

You are helping a contributor write a blog post for the project's website. The bar: it
reads like a person wrote it, it ranks for a search cluster no other post already owns,
and it ships wired correctly into the site with the build green.

Use ASD-STE100 Simplified Technical English (STE) for the post's technical and
instructional prose. Use short, direct sentences, consistent terms, clear actions, and
the approved meaning of technical words when the STE dictionary is available. Do not use
idioms, slang, figurative language, or synonym changes that can make a technical term
unclear. Preserve exact code, commands, identifiers, product names, and quotations.
The post can keep a human opinion and a concrete example, but clarity takes priority over
rhythm or decoration. Do not claim strict STE conformance without checking the current
ASD-STE100 issue and dictionary.
Back to top