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 |
references/memo-template.md
View on GitHub# Memo template — skeleton + provenance grammar
This is the contract `scripts/verify.sh` checks against. Keep the section headings and the
provenance line shape, and the gate passes.
## Provenance line grammar
Every finding line carries one of these shapes:
```text
<CLAIM> — [Source title](https://url), pub 2026-04-12 / accessed 2026-06-02 · confidence: high
<CLAIM> — corroborated by [A](https://a, 2026-03-01) and [B](https://b, 2026-05-10) · confidence: high
<CLAIM> — [Source](https://url), pub n/a / accessed 2026-06-02 · confidence: low
```
Rules:
- A **citation token** is required on every finding: a Markdown link or an explicit URL.
- A **date** is required: `pub YYYY-MM-DD`, `accessed YYYY-MM-DD`, or both. If the source
has no publication date, write `pub n/a` and keep the access date — don't drop the date
field entirely.
- A **confidence tier** token is required: `high`, `med`/`medium`, or `low`.
- Triangulated claims name ≥2 independent sources, each with its own date.
## Memo skeleton
```markdown
# Research memo — <question, scoped>
_As of: 2026-06-02 · researcher: <name/agent> · budget: <N searches, M sources read>_
## Answer
<The direct answer, 2–4 sentences. Bottom line up front. If the honest answer is
"it depends", state on what.>
## Findings
- <claim> — [Source title](https://url), pub 2026-04-12 / accessed 2026-06-02 · confidence: high
- <claim, triangulated> — corroborated by [A](https://a, 2026-03-01) and [B](https://b, 2026-05-10) · confidence: high
- <weaker claim> — [Blog](https://url), pub n/a / accessed 2026-06-02 · confidence: low
## Disagreements
- <where sources conflicted; what each said; which you weight higher and why>
- (If none: "No source-level disagreement found across the N sources read.")
## Open questions / could not verify
- <what you could not source>
- <what remains an assumption, flagged as such>
- <what would settle it if someone spent more budget>
## Sources
1. [Source title](https://url) — pub 2026-04-12, accessed 2026-06-02 — <one-line what it is / why trusted>
2. ...
```
## What "good" looks like
- The **Answer** stands alone — a reader who stops there still got the bottom line.
- Every **Findings** line is independently checkable: click the link, see the date, see
the tier.
- **Disagreements** is never empty silently — either it lists conflicts or it states none
were found.
- **Open questions** is present even on a confident memo; it's the boundary of the
evidence, not an admission of failure.
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 |