ericrisco/rsc-harness / skills/content-engine
content-engine
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.2 KB |
| evals/README.md | markdown | 1.3 KB |
| evals/cases.yaml | config | 4.1 KB |
| references/atomization.md | markdown | 4.1 KB |
| references/brief-and-pipeline.md | markdown | 5.2 KB |
| scripts/verify.shexecutable | script | 5.0 KB |
evals/README.md
View on GitHub# Evals — content-engine
`cases.yaml` is read by the repo's standard eval harness. The `should_trigger` and
`should_not_trigger` cases check routing discrimination: each `should_trigger` prompt
must select this skill (including the non-obvious "turn this pillar post into everything"
atomization-plan case, the symptom-only "our content is chaos" case, and the Spanish
phrasing), while each `should_not_trigger` prompt must route to the named sibling
(`article-writing`, `social-publisher`, `seo-geo`, `brand-voice`, `calendar-scheduling`)
rather than here — they guard the description's boundary between *the system* and
*producing/distributing one artifact*. The single `capability` case is rubric-graded,
not auto-scored: have the skill build the 4-person B2B SaaS Q3 calendar+pipeline and
check the output against the `must_include` list (grounded in 02-DOCS, 4–6 pillars,
cadence baseline, slot-mix, a CSV artifact, briefs, stage gates, a ≥10 atomization plan,
and everything routed out). Run it through whatever runner the skills repo uses. For the
CSV-artifact subset you can sanity-check a real calendar with
`../scripts/verify.sh path/to/calendar.csv` — it lints columns, stages, flagship
brief/atomization, and mix sanity, but does not judge whether the plan is good.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |