ericrisco/rsc-harness / skills/article-writing
article-writing
VerifiedUse when writing one long-form article end to end — answer-first lede, question-shaped headings, plus its on-page surface (title, meta, slug, FAQ, Article/FAQPage JSON-LD) — or fixing a draft that buries the answer or reads AI-padded. NOT keyword research or topic selection (that is `seo-geo`), NOT the editorial calendar (that is `content-engine`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| evals/README.md | markdown | 927 B |
| evals/cases.yaml | config | 3.4 KB |
| references/ai-tell-banlist.md | markdown | 4.7 KB |
| references/on-page-seo.md | markdown | 6.2 KB |
| scripts/verify.shexecutable | script | 5.9 KB |
evals/README.md
View on GitHub# Evals — article-writing
`cases.yaml` is read by the repo's standard eval harness. The `should_trigger` and `should_not_trigger` cases test routing and description discrimination: each `should_trigger` prompt must load this skill (including the non-obvious answer-first-lede and the Catalan cases), and each `should_not_trigger` prompt must route to the named sibling (`seo-geo`, `content-engine`, `brand-voice`, `landing-copy`) instead — that confirms the boundary in the description holds. The single `capability` case is graded by rubric, not pass/fail automation: a grader (human or model) asks the skill to draft the standing-desk article and checks the produced markdown against each `must_include` item, then runs `scripts/verify.sh path/to/draft.md` to confirm the structural and banlist gates pass. There is no automated scoring beyond the harness and that verify lint; run it with the repo's usual eval runner.
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 |