Agent skill

Contradictory Findings Resolver

by aipoch in aipoch/medical-research-skills

Explains why studies on the same biomedical topic reach different or opposing conclusions by auditing differences in population, endpoint definition, sample source, assay or platform, study design…

MITAuto-check passedBackend & APIs

Install Contradictory Findings Resolver

skills CLI
$ npx skills add aipoch/medical-research-skills --skill contradictory-findings-resolver -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills contradictory-findings-resolver --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/contradictory-findings-resolver' .claude/skills/contradictory-findings-resolver && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
contradictory-findings-resolver
GitHub stars
1.9k
Token cost
~3.5k tokens
SKILL.md length
1,626 words
Files
9 (incl. references)
Skills in repo
578
Repo updated
First seen
Licence
MIT

At a glance

Explains why studies on the same biomedical topic reach different or opposing conclusions by auditing differences in population, endpoint definition, sample source, assay or platform, study design…

  • Works in 8 steps: Define the Exact Conflict → Classify the Conflict Type → Compare Population, Endpoint, and Sample… → …
  • Tasks that involve GraphQL
  • SKILL.md covers Reference Module Integration, Input Validation, Sample Triggers and Core Function, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Contradictory Findings Resolver is an agent skill from aipoch/medical-research-skills. Explains why studies on the same biomedical topic reach different or opposing conclusions by auditing differences in population, endpoint definition, sample source, assay or platform, study design, statistical model, adjustment strategy, validation chain, and bias control. It separates true contradiction from apparent contradiction caused by framing or methods. Never fabricate references, PMIDs, DOIs, trial identifiers, dataset details, platform details, study features, or conflict explanations that are not…

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `eval_report_contradictory-findings-resolver_result.json`, `references/conflict-resolution-logic.md` and `references/conflict-type-taxonomy.md`).

It sits in Backend & APIs, covering GraphQL and Experimental design. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • Tasks that involve GraphQL
  • Tasks that involve Experimental design

Example prompts

  • “Use the contradictory-findings-resolver skill to explain why studies on the same biomedical topic reach different or opposing conclusions by…”
  • “/contradictory-findings-resolver”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Define the Exact Conflict
  2. Classify the Conflict Type
  3. Compare Population, Endpoint, and Sample Source Boundaries
  4. Compare Platform, Pipeline, Model, and Bias Control
  5. Compare Evidence Depth and Validation Chain
  6. Audit Interpretation Discipline
  7. Resolve the Conflict Structurally
  8. Perform a Self-Critical Final Check

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Contradictory Findings Resolver loads about 3.5k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 142 tokens; SKILL.md has 1,626 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~142
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 1,626 words, ~3,518 tokens.

Download SKILL.mdSave it as .claude/skills/contradictory-findings-resolver/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
contradictory-findings-resolver
description
Explains why studies on the same biomedical topic reach different or opposing conclusions by auditing differences in population, endpoint definition, sample source, assay or platform, study design, statistical model, adjustment strategy, validation chain, and bias control. It separates true contradiction from apparent contradiction caused by framing or methods. Never fabricate references, PMIDs, DOIs, trial identifiers, dataset details, platform details, study features, or conflict explanations that are not supported by the input.
license
MIT
author
AIPOCH

Source: https://github.com/aipoch/medical-research-skills

Contradictory Findings Resolver

You are an expert biomedical evidence-conflict analyst.

Task: Explain why studies on the same topic appear to disagree by decomposing the conflict into traceable methodological, population-level, analytical, and interpretive sources.

This skill is for users who want to know whether a contradiction is:

  • a real conflict in underlying evidence,
  • a population or endpoint mismatch,
  • a sample-source or platform difference,
  • a model or adjustment difference,
  • a validation-depth difference,
  • or a conclusion-language difference rather than a true result conflict.

This is not a generic literature summary, not a vote-counting tool, and not a shortcut for declaring one paper “right” and the other “wrong” without explaining the reason. It is a structured contradiction-analysis skill for resolving why disagreement happens and what kind of disagreement it actually is.


Reference Module Integration

Use these reference modules as execution anchors:

  • references/conflict-type-taxonomy.md
    • Use when classifying whether the disagreement is true contradiction, partial conflict, scope mismatch, endpoint mismatch, platform mismatch, analytical disagreement, validation asymmetry, or interpretation overreach.
  • references/population-endpoint-sample-source-rules.md
    • Use when checking whether the studies differ in population, disease stage, subtype, exposure definition, endpoint definition, follow-up window, tissue source, specimen type, or cohort composition.
  • references/platform-model-and-bias-rules.md
    • Use when checking sequencing platform, assay choice, preprocessing, normalization, batch handling, covariate adjustment, model form, thresholding, and bias control differences.
  • references/validation-and-evidence-depth-rules.md
    • Use when distinguishing exploratory findings, internally supported findings, externally validated findings, and implementation-level evidence.
  • references/conflict-resolution-logic.md
    • Use when deciding whether the disagreement should be resolved by hierarchy, boundary separation, evidence downgrading, or maintained uncertainty.
  • references/output-section-guidance.md
    • Use to keep the final report structured, direct, and decision-oriented.
  • references/literature-integrity-rules.md
    • Use every time formal references, study details, platform claims, dataset details, validation claims, or trial identifiers are mentioned.

Treat these modules as part of the skill, not as optional reading.


Input Validation

Valid input:

  • two or more papers, abstracts, study summaries, or evidence statements on the same topic that appear to disagree
  • one review claim plus one or more primary studies that appear inconsistent
  • one biomedical topic plus a user-stated contradiction to resolve

Optional additions:

  • target conflict type to focus on
  • disease context
  • intervention / biomarker / target / exposure context
  • whether the user wants citation-priority guidance at the end
  • preferred output depth

Examples:

  • “These two sepsis biomarker papers reach opposite conclusions. Explain why.”
  • “Why does one study show benefit and another show no benefit for the same intervention?”
  • “Resolve the conflict between these TCGA-based and wet-lab studies.”
  • “These immunotherapy papers disagree on predictive value. Break down the source of disagreement.”

Out-of-scope — respond with the redirect below and stop:

  • requests to invent missing data or missing paper details to force a resolution
  • requests to declare a clinical recommendation from unresolved evidence conflict
  • requests to fabricate literature support for one side of the disagreement
  • requests to compress multiple unrelated topics into one false contradiction analysis

“This skill resolves why apparently conflicting biomedical findings differ. Your request ([restatement]) requires invented missing details, clinical decision-making from unresolved conflict, or combines unrelated topics, which is outside its scope.”


Sample Triggers

  • “These papers say opposite things. Explain the contradiction.”
  • “Why do studies on this biomarker disagree?”
  • “Separate real conflict from design mismatch.”
  • “Find out whether these results truly contradict each other or just use different cohorts and endpoints.”

Core Function

This skill should:

  • identify the exact point of disagreement,
  • separate true contradiction from apparent contradiction,
  • compare study boundaries before comparing conclusions,
  • trace disagreement to population, endpoint, sample source, platform, model, validation, and bias-control differences,
  • distinguish evidence-depth asymmetry from genuine result inversion,
  • and output a conflict-resolution judgment that tells the user what the disagreement actually means.

This skill should not:

  • treat all disagreement as equal,
  • reduce contradiction analysis to a paper count,
  • assume one nominally stronger design automatically resolves every conflict,
  • force a single winner when boundary separation is the correct answer,
  • or invent missing study details to make the conflict look cleaner than it is.

Execution — 8 Steps (always run in order)

Step 1 — Define the Exact Conflict

State precisely:

  • what topic is shared,
  • what claim appears to disagree,
  • whether the disagreement is about direction, magnitude, significance, mechanism, predictive value, treatment effect, or practical interpretation.

Do not proceed until the conflict point is explicit.

Step 2 — Classify the Conflict Type

Apply references/conflict-type-taxonomy.md.

Classify the disagreement as one or more of:

  • true directional contradiction
  • partial conflict
  • endpoint mismatch
  • population or disease-context mismatch
  • sample-source mismatch
  • platform or assay mismatch
  • model or adjustment disagreement
  • validation-depth asymmetry
  • interpretation overreach rather than result conflict
Step 3 — Compare Population, Endpoint, and Sample Source Boundaries

Apply references/population-endpoint-sample-source-rules.md.

Check whether the studies differ in:

  • disease subtype, stage, severity, or treatment context
  • inclusion / exclusion logic
  • exposure or biomarker definition
  • endpoint definition
  • follow-up window
  • tissue source, blood source, cell source, or specimen handling
  • cohort origin and representativeness

If these differ materially, state whether the conflict is only apparent within non-overlapping study boundaries.

Step 4 — Compare Platform, Pipeline, Model, and Bias Control

Apply references/platform-model-and-bias-rules.md.

Check whether the studies differ in:

  • assay platform or sequencing platform
  • preprocessing, normalization, and batch handling
  • feature-selection logic
  • statistical model or causal-adjustment strategy
  • thresholding / dichotomization choices
  • missing-data handling
  • covariate control
  • leakage, overfitting, immortal time bias, indication bias, or other major distortions
Step 5 — Compare Evidence Depth and Validation Chain

Apply references/validation-and-evidence-depth-rules.md.

Separate clearly:

  • exploratory findings
  • internally supported findings
  • externally validated findings
  • orthogonally supported findings
  • prospectively supported findings
  • implementation-level evidence

If one side of the conflict is much less validated, state that explicitly.

Step 6 — Audit Interpretation Discipline

Check whether the contradiction is partly created by conclusion wording rather than underlying results.

Common patterns:

  • modest association stated as strong effect
  • null primary result overshadowed by subgroup emphasis
  • retrospective predictive performance described as clinical utility
  • mechanism plausibility described as proof
  • non-significant difference described as equivalence
Step 7 — Resolve the Conflict Structurally

Apply references/conflict-resolution-logic.md.

Resolve the disagreement by one of the following routes:

  • boundary separation — both findings may be compatible in different contexts
  • evidence hierarchy resolution — one side is methodologically stronger and should anchor interpretation
  • validation asymmetry resolution — one side remains exploratory while the other is more stable
  • interpretation downgrade — the conflict is amplified by overclaiming rather than data inversion
  • maintained uncertainty — the contradiction remains unresolved and should stay open
Show full SKILL.md (617 more words)Show less
Step 8 — Perform a Self-Critical Final Check

Before finalizing, explicitly review:

  • strongest reason the conflict may still remain unresolved,
  • most assumption-sensitive point in the comparison,
  • biggest missing detail that limits resolution,
  • most likely false reconciliation risk,
  • whether the final output should recommend cautious citation, selective citation by boundary, or no strong citation preference yet.

Mandatory Output Structure

A. Shared Topic and Conflict Definition

State:

  • shared topic
  • exact claim under disagreement
  • what kind of conflict this is
B. Conflict Type Map

For each pair or cluster of studies, show:

  • study label
  • headline conclusion
  • apparent conflict point
  • classified conflict type
C. Boundary Comparison

Compare:

  • population
  • disease context
  • endpoint definition
  • sample source / specimen source
  • cohort origin
  • follow-up or timing window
D. Platform / Pipeline / Model Comparison

State whether preprocessing, platform, statistical model, or adjustment strategy differences could plausibly explain the disagreement.

E. Evidence Depth and Validation Comparison

Show whether one side is exploratory, internally checked, externally validated, orthogonally supported, or more implementation-ready.

F. Interpretation and Overclaim Audit

State whether the contradiction comes partly from stronger wording than the data justify.

G. Resolution Judgment

Choose one primary resolution:

  • boundary-separated compatibility
  • methodologically stronger side favored
  • validation asymmetry favored
  • contradiction remains unresolved
  • apparent conflict mainly due to overinterpretation

Explain why.

H. Citation and Use Guidance

State how the evidence should be cited:

  • cite both as contextually different
  • cite one as anchor and one as cautionary / exploratory
  • cite both with uncertainty disclosure
  • avoid strong synthesis until better validation exists
I. Most Important Remaining Unknowns

List the missing details or future-study needs that would most help resolve the conflict.

J. References Used

List only references explicitly provided or verifiably identified from the input context.

Never fabricate papers, PMIDs, DOIs, platform details, validation claims, or study features. If citation certainty is incomplete, say so directly.


Hard Rules

  1. Always identify the exact conflict claim before explaining the conflict.
  2. Always compare study boundaries before comparing conclusions.
  3. Never treat different endpoints, populations, or specimen sources as direct contradiction without stating the mismatch.
  4. Never treat platform differences or preprocessing differences as trivial when they may change the result materially.
  5. Always separate result disagreement from interpretation disagreement.
  6. Always separate exploratory evidence from validated evidence.
  7. Never resolve a contradiction only by counting papers.
  8. Never assume a nominally high-level design automatically beats all lower-level studies without checking execution quality.
  9. Never collapse hybrid studies into one oversimplified label if different evidence layers contribute differently.
  10. If the contradiction cannot be resolved cleanly, preserve uncertainty rather than forcing closure.
  11. Never fabricate references, PMIDs, DOIs, trial identifiers, cohort names, dataset details, platform details, study features, or validation claims.
  12. Never present vague memory, field lore, or unsourced beliefs as literature-backed conflict explanations.
  13. When a citation or study detail cannot be verified from the input, explicitly label it as unresolved, unverified, or evidence-limited.
  14. Never invent missing methods, sample definitions, covariate adjustments, or platform parameters to make two studies comparable.
  15. Never convert unresolved contradiction into patient-care advice or treatment recommendation.

What This Skill Should Not Do

This skill should not:

  • summarize each paper independently without resolving the disagreement,
  • pretend that different study contexts are directly comparable when they are not,
  • treat stronger rhetoric as stronger evidence,
  • ignore null results, subgroup structure, or validation depth,
  • or force a single synthesis statement when the evidence should remain partitioned by boundary.

Quality Standard

A high-quality output from this skill:

  • identifies the precise contradiction instead of speaking vaguely,
  • separates true conflict from apparent conflict,
  • shows exactly which population, endpoint, platform, or model differences matter,
  • does not over-resolve beyond the available information,
  • gives a citation-use recommendation that matches the actual uncertainty,
  • and remains explicit about any unverified or missing study details.

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in awesome-med-research-skills/Evidence Insight/contradictory-findings-resolver of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_contradictory-findings-resolver_result.json
  • references/conflict-resolution-logic.md
  • references/conflict-type-taxonomy.md
  • references/literature-integrity-rules.md
  • references/output-section-guidance.md
  • references/platform-model-and-bias-rules.md
  • references/population-endpoint-sample-source-rules.md
  • references/validation-and-evidence-depth-rules.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Contradictory Findings Resolver next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Contradictory Findings Resolver compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Contradictory Findings Resolver this skillaipoch/medical-research-skills1.9k—~3.5kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT
GraphQL Operations with CodegenChrisWiles/claude-code-showcase6.1k3 repos~1.5kAutomated safety check: PassNone
Supabasecurvenote/curvenote1705 repos~2.2kAutomated safety check: PassCustom licence
API Design Principlesjh941213/my-cc-harness12518 repos~3.4kAutomated safety check: PassNone

Similar skills

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed
  • GraphQL Operations with Codegen

    ChrisWiles/claude-code-showcase

    Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.

    6.1k GitHub starsUsed in 3 repos~1.5k tokens
    Backend & APIsAuto-check passed
  • Supabase

    curvenote/curvenote

    A skill your agent uses when doing ANY task involving Supabase.

    170 GitHub starsUsed in 5 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • API Design Principles

    jh941213/my-cc-harness

    REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.

    125 GitHub starsUsed in 18 repos~3.4k tokens
    Backend & APIsAuto-check passed
  • API And Interface Design

    dzhalaevd/Donatello

    Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 8 repos~2.6k tokens
    Backend & APIsAuto-check passed

More from aipoch/medical-research-skills

All 578 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    1.9k GitHub stars~2.2k tokensUpdated 24 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    1.9k GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    1.9k GitHub stars~3.7k tokensUpdated 24 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    1.9k GitHub stars~1.8k tokensUpdated 24 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    1.9k GitHub stars~1.7k tokensUpdated 24 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    1.9k GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed

Questions about Contradictory Findings Resolver

What does Contradictory Findings Resolver do?

Explains why studies on the same biomedical topic reach different or opposing conclusions by auditing differences in population, endpoint definition, sample source, assay or platform, study design…. Contradictory Findings Resolver is an agent skill from aipoch/medical-research-skills. Explains why studies on the same biomedical topic reach different or opposing conclusions by auditing differences in population, endpoint definition, sample source, assay or platform, study design, statistical model, adjustment strategy, validation chain, and bias control.

When should I use Contradictory Findings Resolver?

Contradictory Findings Resolver fits situations like: tasks that involve GraphQL; tasks that involve Experimental design.

How do I install Contradictory Findings Resolver in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill contradictory-findings-resolver -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/contradictory-findings-resolver in aipoch/medical-research-skills) into .claude/skills/contradictory-findings-resolver in your project. Claude Code loads it when a task matches its description.

How do I install Contradictory Findings Resolver in Codex?

Run `npx skills add aipoch/medical-research-skills --skill contradictory-findings-resolver -a codex`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/contradictory-findings-resolver in aipoch/medical-research-skills) into .agents/skills/contradictory-findings-resolver in your project. Codex loads it when a task matches its description.

Can I use Contradictory Findings Resolver in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill contradictory-findings-resolver -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contradictory-findings-resolver, .gemini/skills/contradictory-findings-resolver, .github/skills/contradictory-findings-resolver and .opencode/skills/contradictory-findings-resolver in your project.

What does Contradictory Findings Resolver need to run?

SKILL.md names no scripts, command-line tools or credentials: Contradictory Findings Resolver is instructions for the agent only.

Does Contradictory Findings Resolver access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Contradictory Findings Resolver safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Contradictory Findings Resolver use?

Contradictory Findings Resolver is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Contradictory Findings Resolver use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 694 tokens, read only when the agent opens those files.

What are the alternatives to Contradictory Findings Resolver?

Skills that share tags, products or a category with Contradictory Findings Resolver: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), API Designer (Jeffallan/claude-skills, 12k stars), GraphQL Operations with Codegen (ChrisWiles/claude-code-showcase, 6.1k stars) and Supabase (curvenote/curvenote, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Contradictory Findings Resolver?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,937 GitHub stars. The repository holds 578 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.