Research Playbook

Operational playbook for technical evaluation — project-first framing, criteria-before-candidates, source triangulation with dates, evidence-cited tradeoff matrices, and recommendation-first reporting. Read in full at the start of every task on this team.

49 stars 3 forksResearch & Science Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add toffyui/ccteams

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add toffyui/ccteams --skill research-playbook
Manual install
git clone --depth 1 https://github.com/toffyui/ccteams.git /tmp/ccteams
mkdir -p ~/.claude/skills
cp -r /tmp/ccteams/teams/research/skills/research-playbook ~/.claude/skills/research-playbook

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Research Playbook

This is the literal procedure a frontier model follows to evaluate a technical
choice and write a recommendation. This team writes no code. The order is the
point: defining criteria AFTER seeing candidates is how motivated reasoning
sneaks in, and it is the single most expensive mistake in research.

## Operating loop

1. **Read the PROJECT first — the recommendation lives in its constraints.** A
   generic "A vs B" comparison is worthless; the same question has opposite
   answers in different projects. Before searching the web, read the repo:
   - Stack, language, framework, and their VERSIONS (from lockfiles /
     dependency files, not memory — a project on framework v2 can't use a
     library that needs v5).
   - Deployment target (serverless, container, edge, on-prem), team size, and
     what is ALREADY installed (an incumbent that half-solves the problem
     changes the math entirely).
   - What the user actually needs the tech to DO — restate it in one sentence,
     including any constraint they didn't say out loud (license, bundle size,
     sync/async, data residency).
2. **Define 3–6 weighted decision criteria FROM those constraints, BEFORE
   looking at candidates.** Write them down first. Weight them (e.g., "fit for
   async: high; maintenance health: high; migration cost: medium; license:
   gate"). Fixing criteria before candidates is what prevents you from
   reverse-engineering criteria to justify a favorite.
Read the full skill on GitHub

Details

Skill name
research-playbook
Path
teams/research/skills/research-playbook/SKILL.md
License
MIT
Repo updated
31 August 2026

FAQ

What does the Research Playbook skill do?

Operational playbook for technical evaluation — project-first framing, criteria-before-candidates, source triangulation with dates, evidence-cited tradeoff matrices, and recommendation-first reporting. Read in full at the start of every task on this team.

How do I install the Research Playbook skill?

Claude Code plugin: /plugin marketplace add toffyui/ccteams. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Research Playbook popular?

It lives in toffyui/ccteams, which has 49 GitHub stars and 3 forks.

Related skills

Choose Team

49

toffyui/ccteams

Pick and apply the best ccteams agent team for a described need using natural language — reads team metadata, selects the closest match, and applies it.

AI, LLMs & Agents

Debug Playbook

49

toffyui/ccteams

Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.

Software Development

Django Playbook

49

toffyui/ccteams

Operational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.

Software Development

Sample Space Physics

44

siyunhao2025-beep/Ku-academic

A fully-filled WORKED EXAMPLE domain pack for space-physics thermosphere storm research (TIMED/SABER temperature/density). It teaches how to fill a domain pack; it is NOT a default and ships no results, thresholds or fixed values. For your own field, copy domains/example-domain instead.

Research & Science

Research Mother

44

siyunhao2025-beep/Ku-academic

Orchestrate evidence-grounded research with replaceable domain packs across seven explicit phases (onboarding/preparation, topic and paper investigation, literature review, experiment design, computation, figures and manuscript writing, conclusion and revision): literature discovery and reviews, study design, real analysis, research roadmaps and schematic figures, genuine citation provenance and claim-support verification, de-AI writing, methods, manuscript development, contribution-driven supplementation, journal-corpus style learning and scientific editing. Use when a researcher asks to buil

Research & Science

Employment Law Research

43

bstevescherer/heycounsel-community

Research a US employment law topic across federal, state, and city jurisdictions and produce structured research notes with proper source attribution. Use this skill any time the user asks about US employment laws, regulations, or pending legislation - from a single jurisdiction question to a 50-state survey. Triggers include phrases like "research [employment law topic]", "what are the laws on [employment topic]", "state-by-state [employment topic]", "help me understand [topic] across the US", or any prompt that asks for a legal landscape overview before another deliverable. Always run this B

Research & Science

Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.