add-blog-post SKILL.md skillA
add-blog-post from 5hirish/duct is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 5hirish/duct/add-blog-post@git:20261110.451b27ePins git:20261110.451b27e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 5hirish/duct
- Path
.agents/skills/add-blog-post/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261110.451b27e, committed Nov 10, 2026
- First version recorded
- Oct 27, 2026
- Size
- 28,015 bytes
- Repository stars
- 10
- License
- MIT
Research, write, illustrate and publish a post on the Duct blog that ranks in search and gets cited by answer engines (ChatGPT, Perplexity, Google AI Overviews, Claude). Runs a research arm first (demand, the pages answer engines cite today, primary sources, Duct's first-hand evidence), then writes for extraction, draws the hero, renders, lists and verifies the post, and keeps the publishing cadence. Use for "write a blog post", "next post", "blog about <topic or URL>", or a blog content…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
A post exists to be **found, quoted and trusted**: found by search, quoted by answer engines, trusted by the reader who clicks through. Answer engines matter more than blue links now. A reader who asks ChatGPT, Perplexity or an AI Overview gets an answer assembled from a handful of pages, with those pages cited. Being one of the handful is the goal, and the evidence on what earns it is in [`references/aio.md`](references/aio.md). Read it once. The short version: engines lift **self-contained, specific, sourced passages** from **crawlable pages** that **other places already mention**. Every phase below serves one of those three. **Sharing a post published somewhere else** (Shirish's own blog, a guest post) is not this recipe: it is a *link post*, a card on the blog index that goes to the original, with no page and no copy here. Write the front matter only, with `link:` set to the original's address, then draw the card and run the generator (`scripts/build_blog.py` docstring, "Link posts"). Nothing in the phases below applies to it. ## The value bar: no post without it A post earns its place only if a reader leaves able to **do something they …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fihgbcb3uhorw4jm/8ff5bc8aeec42ed464e87391c9ca003e32df7ebcc4c7bc826243efe6cf9fa8e2.json
Then /plugin install add-blog-post@markdownregistry-fihgbcb3uhorw4jm in Claude Code. It installs git:20261110.451b27e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add 5hirish/duct/add-blog-post@sha256:8ff5bc8aeec42ed4The line at the top of this page pins the label git:20261110.451b27e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fihgbcb3uhorw4jm)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in 5hirish/duct/add-blog-post since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of add-blog-post from somewhere else? Ask it: where did my add-blog-post come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 27, 2026 and Nov 10, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261110.451b27e latest | 2026-11-10 | 451b27e | 28,015 B | A | view · diff |
| git:20261108.51d49af | 2026-11-08 | 51d49af | 27,986 B | A | view · diff |
| git:20261102.181f3fc | 2026-11-02 | 181f3fc | 27,516 B | A | view · diff |
| git:20261030.d9ef0db | 2026-10-30 | d9ef0db | 27,524 B | A | view · diff |
| git:20261027.af8f7c5 | 2026-10-27 | af8f7c5 | 27,147 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/add-blog-post/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (28015 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
5hirish/duct · 10 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fihgbcb3uhorw4jm GET https://markdownregistry.com/api/v1/resolve?ref=5hirish/duct/add-blog-post GET https://markdownregistry.com/api/v1/blob/8ff5bc8aeec42ed464e87391c9ca003e32df7ebcc4c7bc826243efe6cf9fa8e2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from 5hirish/duct
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.