Claude Skill

teamwork-research

Use when a broad or deep external investigation needs multiple source classes, claim-level evidence synthesis, or contradiction resolution; do not use for a narrow lookup or local code inspection.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download jinplu-teamwork-skills_teamwork-research-8f23dcd.zip · 2 KB

jinplu/teamwork 12 0 forks MIT Updated 9d ago

Part of jinplu/teamwork — 8 skills

Install

skills CLI npx skills add https://github.com/JinPLu/Teamwork/tree/main/skills/teamwork-research

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jinplu-teamwork@llmmart

Git git clone https://github.com/JinPLu/Teamwork.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole jinplu/teamwork collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Teamwork Research

Keep narrow lookups native. When Research is activated, investigate the complete question rather than creating a lightweight ritual around a few searches.

Method

Name the decision this investigation serves, then define intended use, scope, freshness cutoff, privacy boundary, and material claims.
Search the strongest primary and current sources first, then add independent source classes where they can change confidence.
Connect each material claim to direct support, counterevidence, inference, confidence, date, and nearby citation.
Investigate contradictions and explain rejected sources or unresolved gaps.
Stop when the evidence distinguishes the served direction, the scope is answered, or further retrieval is unlikely to change the conclusion; state which condition applies. Results feed the matching discussion or plan section; they do not rewrite the whole case. Supplied sources are seeds, not automatic proof or a search boundary. Split work only across independent evidence areas and keep one synthesis owner.

Maintain an early provisional conclusion as evidence develops, clearly marked as provisional. The research synthesis must preserve the decision use, a question tree, a claim-to-evidence table, contradictions and unknowns, coverage and stop conditions, and notes for every source that actually participated in the reasoning; source notes are embedded in the document rather than delegated to a separate index.

Return the supported conclusion, contradictions, residual uncertainty, coverage result, and the explicit stop basis.

Persistence

When a listed checkpoint fires, write in the same response cycle. If separate stable identities each cross a checkpoint, write each to its own path.

Cross-chat memory lives in one Markdown document from references/research.md at docs/teamwork/research/<slug>.md. Same identity means the same research question; reuse that path and name the document you read. A different subject gets a new path.

Checkpoints: a material claim-to-evidence synthesis is first settled; contradictions change confidence or the conclusion; or a stop condition is reached.

Files (teamwork)

agents

openai.yaml 227 B

interface:
  display_name: "Teamwork Research"
  short_description: "Investigate broad external questions with evidence"
  default_prompt: "Use $teamwork-research to investigate this external question across reliable sources."

references

research.md 1.1 KB

---
status: active
superseded-by:
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---

# Research: <question>

## Identity and decision use

- Subject identity: <stable identity>
- Decision use: <what this research informs>
- Authoritative owner: <research owner>
- Scope and freshness: <scope, cutoff, privacy boundary>

## Question tree

<global question and dependent subquestions>

## Current synthesis

<supported conclusion or clearly labelled provisional conclusion>

## Claim-to-evidence table

| Claim | Direct support | Counterevidence | Inference | Confidence | Date/version |
| --- | --- | --- | --- | --- | --- |
| <claim> | <nearby citation> | <evidence or none found> | <owner interpretation> | <owner confidence> | <date/version> |

## Contradictions and unknowns

<unresolved conflicts, rejected-source reasons, and gaps>

## Source notes

### <source citation>

<identity, date or version, class, claim role, and disposition>

## Coverage and stop condition

<material-claim coverage and explicit stop basis>

## History

<Append only. Never rewrite or remove; a correction is a new dated entry.>

### <date/time — semantic change>

<certified synthesis delta>

SKILL.md 2.4 KB

---
name: teamwork-research
description: Use when a broad or deep external investigation needs multiple source classes, claim-level evidence synthesis, or contradiction resolution; do not use for a narrow lookup or local code inspection.
---

# Teamwork Research

Keep narrow lookups native. When Research is activated, investigate the complete
question rather than creating a lightweight ritual around a few searches.

## Method

1. Name the decision this investigation serves, then define intended use, scope,
   freshness cutoff, privacy boundary, and material claims.
2. Search the strongest primary and current sources first, then add independent
   source classes where they can change confidence.
3. Connect each material claim to direct support, counterevidence, inference,
   confidence, date, and nearby citation.
4. Investigate contradictions and explain rejected sources or unresolved gaps.
5. Stop when the evidence distinguishes the served direction, the scope is
   answered, or further retrieval is unlikely to change the conclusion; state
   which condition applies. Results feed the matching discussion or plan
   section; they do not rewrite the whole case. Supplied sources are seeds, not
   automatic proof or a search boundary. Split work only across independent
   evidence areas and keep one synthesis owner.

Maintain an early provisional conclusion as evidence develops, clearly marked
as provisional. The research synthesis must preserve the decision use, a
question tree, a claim-to-evidence table, contradictions and unknowns, coverage
and stop conditions, and notes for every source that actually participated in
the reasoning; source notes are embedded in the document rather than delegated
to a separate index.

Return the supported conclusion, contradictions, residual uncertainty, coverage
result, and the explicit stop basis.

## Persistence

When a listed checkpoint fires, write in the same response cycle. If separate
stable identities each cross a checkpoint, write each to its own path.

Cross-chat memory lives in one Markdown document from `references/research.md`
at `docs/teamwork/research/<slug>.md`. Same identity means the same
research question; reuse that path and name the document you read. A different
subject gets a new path.

Checkpoints: a material claim-to-evidence synthesis is first settled;
contradictions change confidence or the conclusion; or a stop condition is
reached.