ericrisco/rsc-harness / skills/research-ops
research-ops
VerifiedUse when someone hands you an open question whose answer must survive scrutiny — a tech choice, a regulation, a what-is-actually-true-about-X — with every non-obvious claim dated and sourced, source disagreements surfaced rather than averaged away, and a cited memo as the deliverable. Also for refreshing a stale research memo. NOT sizing a market with TAM/SAM/SOM (that is `market-research`), NOT a standing cadence watch on named rivals (that is `competitor-watch`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| evals/README.md | markdown | 949 B |
| evals/cases.yaml | config | 2.6 KB |
| references/credibility-rubric.md | markdown | 4.2 KB |
| references/memo-template.md | markdown | 2.5 KB |
| scripts/verify.shexecutable | script | 6.9 KB |
evals/README.md
View on GitHub# Evals — research-ops
These cases are run by the rsc eval harness. `should_trigger` and `should_not_trigger`
check description routing — does the skill fire on real research asks (including the
non-obvious "settle this argument" and the Spanish/Catalan phrasings) and stay quiet on
market-sizing, standing-watch, scraping, and knowledge-filing asks that belong to siblings.
The `capability` case is a rubric a human or LLM grader scores against an actual research
run: did the agent loop rather than one-shot, triangulate a load-bearing claim, date and
tier every claim, surface (or rule out) disagreement, and ship an answer-first memo with an
open-questions section. There is no automated grading of memo *correctness* — the only
mechanical check is `scripts/verify.sh`, which lints a produced memo for provenance
structure (answer section, citations, dates, confidence tiers, open-questions section), not
for whether the answer is right.
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 |