content-engine SKILL.md skillA
content-engine from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/content-engine@git:20261011.c7821cdPins git:20261011.c7821cd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/content-engine/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261011.c7821cd, committed Oct 11, 2026
- First version recorded
- Jun 2, 2026
- Size
- 12,504 bytes
- Repository stars
- 236
- License
- MIT
Use when a content operation needs a SYSTEM: a dated editorial calendar built top-down from pillars, plus the stage gates, briefs, WIP limits and 1:10 atomization plan that move each slot to publish-ready. NOT writing the pieces (that is `article-writing`), NOT publishing them (that is `social-publisher`), NOT keyword research (that is `seo-geo`).
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
# Content Engine — The Calendar and the Pipeline That Feeds It *The factory floor and the production schedule, not the words off any single station.* You own two machines: the **calendar** (what gets made and when — a dated, slotted plan anchored to pillars, so "what do we post Thursday?" is a lookup, not a weekly panic) and the **pipeline** (how each slot moves from idea to publish-ready through stage gates, so output is consistent regardless of who writes). You do not write the pieces and you do not publish them — you decide what gets made, you spec the brief, and you route each station to a specialist. Content fails not from one bad post but from **no system**: no documented cadence, no brief, no stage gate, pillars that never get atomized. ~78% of high-performing content teams run a documented strategy and see ~3x the engagement of teams without one (InfluenceFlow, 2026). This skill is that system. ## Ground first (STOP gate) You plan content for a real brand; you do not invent its strategy. Before building anything, read what already exists. …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/content-engine@sha256:9db32f5576b2bfa6The line at the top of this page pins the label git:20261011.c7821cd, 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_o7bilwylgtj2prof)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 2, 2026 and Oct 11, 2026, about one every 44 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.c7821cd latest | 2026-10-11 | c7821cd | 12,504 B | A | view · diff |
| git:20260729.3ecb845 | 2026-07-29 | 3ecb845 | 11,912 B | A | view · diff |
| git:20260628.e37ed23 | 2026-06-28 | e37ed23 | 12,931 B | A | view · diff |
| git:20260602.ff52dba | 2026-06-02 | ff52dba | 12,623 B | A | view |
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 (12504 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
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o7bilwylgtj2prof GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/content-engine GET https://markdownregistry.com/api/v1/blob/9db32f5576b2bfa6aa1de4d7b6cc6a8873e9cb2f02a0bf7fe4538756ad5c59b8
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 ericrisco/rsc-harness
Every file in ericrisco/rsc-harness