Claude Code Plugins

Community-maintained marketplace

Feedback

evidence-draft

@WILLOSCAR/research-units-pipeline
1
0

|

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name evidence-draft
description Create per-subsection evidence packs (NO PROSE): claim candidates, concrete comparisons, evaluation protocol, limitations, plus citation-backed evidence snippets with provenance. **Trigger**: evidence draft, evidence pack, claim candidates, concrete comparisons, evidence snippets, provenance, 证据草稿, 证据包, 可引用事实. **Use when**: `outline/subsection_briefs.jsonl` exists and you want evidence-first section drafting where every paragraph can be backed by traceable citations/snippets. **Skip if**: `outline/evidence_drafts.jsonl` already exists and is refined (no placeholders; >=3 comparisons per subsection; `blocking_missing` empty). **Network**: none (richer evidence improves with abstracts/fulltext). **Guardrail**: NO PROSE; do not invent facts; only use citation keys that exist in `citations/ref.bib`.

Evidence Draft (NO PROSE)

Purpose: turn papers/paper_notes.jsonl + subsection mapping into writeable evidence packs so the writer never has to guess (and never copies outline placeholders).

Key design: every pack should contain evidence snippets (1–2 sentences) with provenance (abstract/fulltext/notes pointer). Even abstract-level snippets are better than template prose.

Non-negotiables

  • NO PROSE: packs are bullets-only evidence, not narrative paragraphs.
  • No fabrication: do not invent datasets/metrics/numbers.
  • Citation hygiene: every cite key must exist in citations/ref.bib.
  • Claim candidates must be snippet-derived (no axis-driven “Hypothesis: …” items); put questions into verify_fields instead.
  • Evidence-aware language:
    • fulltext-backed → can summarize comparisons
    • abstract-only/title-only → must be provisional + list verify-fields (no strong “dominant trade-offs” language)

Inputs

Required:

  • outline/subsection_briefs.jsonl
  • papers/paper_notes.jsonl
  • citations/ref.bib

Optional (recommended for addressable evidence):

  • papers/evidence_bank.jsonl
  • outline/evidence_bindings.jsonl

Outputs

  • outline/evidence_drafts.jsonl

Optional (human-readable):

  • outline/evidence_drafts/ (folder of per-subsection Markdown packs)

Output format (outline/evidence_drafts.jsonl)

JSONL (one JSON object per line). Required fields per record:

  • sub_id, title
  • evidence_ids (list[str]; if outline/evidence_bindings.jsonl exists, this should match the binding for the subsection)
  • evidence_level_summary (counts: fulltext|abstract|title)
  • evidence_snippets (list; each has text, paper_id, citations, provenance)
  • definitions_setup (list of cited bullets)
  • claim_candidates (3–5 items; each has claim, citations, evidence_field)
  • concrete_comparisons (>=3 items; each has axis, A_papers, B_papers, citations, evidence_field)
  • evaluation_protocol (list of concrete protocol bullets + citations)
  • failures_limitations (2–4 cited bullets)
  • blocking_missing (list[str]; if non-empty, drafting must stop)
  • verify_fields (list[str]; non-blocking: fields to verify before making strong claims)

Provenance schema (per snippet)

Example:

{"source":"abstract","pointer":"papers/paper_notes.jsonl:paper_id=P0012#abstract","evidence_level":"abstract"}

Allowed source: fulltext|abstract|paper_notes|title.

Workflow

  1. Load outline/subsection_briefs.jsonl and read each subsection’s rq, axes, clusters, and evidence-level policy.
  2. Load papers/paper_notes.jsonl and build a per-paper evidence index (bibkey, evidence_level, abstract, fulltext_path, limitations).
  3. For each subsection:
    • Build evidence_snippets from mapped papers (prefer fulltext, else abstract), and record provenance.
    • Definitions/setup: 1–2 bullets that define setup + scope boundary (with citations).
    • Claim candidates: 3–5 checkable candidates (prefer snippet-derived; tag with evidence_field).
    • Concrete comparisons: >=3 A-vs-B comparisons (cluster-vs-cluster) along explicit axes.
    • Evaluation protocol: list concrete benchmark/metric tokens if extractable; otherwise treat as a blocking gap.
    • Failures/limitations: 2–4 concrete limitations/failure modes with citations.
    • Set blocking_missing for hard blockers (e.g., no usable citations; title-only evidence; no eval tokens for an eval-heavy subsection).
  4. Write outline/evidence_drafts.jsonl and per-subsection Markdown copies.

Quality checklist

  • Every subsection has >=3 concrete comparisons.
  • evidence_snippets is non-empty and includes provenance.
  • claim_candidates has >=3 snippet-derived items (no axis-driven hypotheses).
  • blocking_missing is empty.
  • No TODO / (placeholder) / <!-- SCAFFOLD --> / unicode ellipsis (…) remains.

Helper script

  • python .codex/skills/evidence-draft/scripts/run.py --help
  • python .codex/skills/evidence-draft/scripts/run.py --workspace <ws>

Script

Quick Start

  • python .codex/skills/evidence-draft/scripts/run.py --help
  • python .codex/skills/evidence-draft/scripts/run.py --workspace <ws>

All Options

  • See --help.
  • Inputs: outline/subsection_briefs.jsonl, papers/paper_notes.jsonl, citations/ref.bib.

Examples

  • Generate evidence packs after citations:
    • Ensure citations/ref.bib exists.
    • Ensure outline/subsection_briefs.jsonl exists (axes/clusters/plan filled).
    • Ensure papers/paper_notes.jsonl has usable evidence (abstract/fulltext/limitations).
    • Run: python .codex/skills/evidence-draft/scripts/run.py --workspace workspaces/<ws>