mnt/user-data/outputs/PaperClaw/skills/synthesis/contradiction-detection/SKILL.md
# Contradiction Detection ## Overview Scans a corpus of papers for conflicting empirical claims, methodological disagreements, or opposing conclusions on the same topic. Surfaces genuine scientific contradictions that the team needs to be aware of — before they cite conflicting work or build on a shaky premise. ## When to Use - User asks "do any of our papers disagree with each other?" - User is writing a discussion section and needs to address conflicting findings - User wants to know if a cl
npx skillsauth add 0xmerl99/paperclaw mnt/user-data/outputs/PaperClaw/skills/synthesis/contradiction-detectionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Scans a corpus of papers for conflicting empirical claims, methodological disagreements, or opposing conclusions on the same topic. Surfaces genuine scientific contradictions that the team needs to be aware of — before they cite conflicting work or build on a shaky premise.
contradictions = contradiction_detection.scan(
corpus=review.get_papers(),
topic="learning rate schedules in transformer training",
min_confidence=0.7
)
contradiction_detection.check_claim(
claim="Dropout consistently improves generalization in large language models",
corpus=review.get_papers(),
search_external=True
)
contradiction_detection.report(
topic="benchmark evaluation of protein structure prediction",
format="discussion_section_draft",
include_resolution_suggestions=True
)
Returns list of contradiction pairs with: paper A, paper B, conflicting claims, contradiction type, severity score, and suggested resolution or explanation. Optionally formatted as a discussion section narrative.
evidence-grading to assess which side of a contradiction has stronger supportdevelopment
# Lab Knowledge Handoff ## Overview Packages a departing team member's knowledge — their reading history, annotations, notes, and expertise — into a structured handoff document that the lab retains permanently. Prevents institutional knowledge loss when students graduate, postdocs move on, or collaborators leave. ## When to Use - A lab member is graduating, leaving, or transitioning off a project - Lab wants to archive what a departing member knew before they go - New member is onboarding to a
documentation
# Living Review ## Overview Maintains a continuously updated, structured literature review for a research team. Ingests papers from multiple sources, synthesizes findings across the team's collective reading, and produces a living document that evolves as new work is published. ## When to Use - User asks to "update our literature review" or "add this paper to the review" - User wants a summary of what their team has read on a topic - User asks "what do we know about X based on our papers?" - O
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.