Clinical Trial logo

Clinical Trial

Community
beita6969
clinical-trial

Designs and analyzes clinical trials including sample size calculation, randomization schemes, endpoint selection, CONSORT reporting, and interim analysis planning; trigger when users ask about RCTs, Phase I-IV trials, or clinical study design.

Overview

Publisherbeita6969
RepositoryScienceClaw
Skill nameclinical-trial
Stars
950
Forks
106
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by beita6969 on GitHub. Read the source before you install it.

Installation

Install the Clinical Trial AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/beita6969/ScienceClaw/tree/main/skills/clinical-trial
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/beita6969/ScienceClaw.git /tmp/ScienceClaw
mkdir -p .claude/skills
cp -r /tmp/ScienceClaw/skills/clinical-trial .claude/skills/clinical-trial
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Clinical Trial in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Clinical Trial on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Clinical Trial is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

When to Trigger

Activate this skill when the user mentions:

  • Clinical trial design, RCT, randomized controlled trial
  • Sample size calculation, power analysis for trials
  • CONSORT, STROBE, SPIRIT guidelines
  • Phase I, II, III, IV trials
  • Primary/secondary endpoints, composite endpoints
  • Interim analysis, adaptive trial design, futility
  • Blinding, randomization, allocation concealment
  • Intention-to-treat (ITT), per-protocol analysis

Step-by-Step Methodology

  1. Define the research question - Specify PICO (Population, Intervention, Comparator, Outcome). Determine if superiority, non-inferiority, or equivalence design is appropriate.
  2. Select trial phase and design - Choose phase (I: safety/dose, II: efficacy signal, III: confirmatory, IV: post-market). Consider parallel, crossover, factorial, or adaptive designs.
  3. Primary endpoint selection - Define primary outcome (must be clinically meaningful). Specify measurement timing and minimal clinically important difference (MCID).
  4. Sample size calculation - Specify alpha (typically 0.05, two-sided), power (typically 80-90%), expected effect size, and dropout rate. Use appropriate formula for the endpoint type (continuous, binary, time-to-event).
  5. Randomization and blinding - Recommend randomization method (simple, block, stratified, minimization). Specify blinding level (open-label, single, double, triple).
  6. Statistical analysis plan - Pre-specify primary analysis method (t-test, chi-square, log-rank, mixed models). Define interim analysis schedule with alpha-spending function (O'Brien-Fleming, Lan-DeMets).
  7. Reporting - Follow CONSORT for RCTs, STROBE for observational, SPIRIT for protocols. Include flow diagram, enrollment numbers, and all pre-specified analyses.

Key Databases and Tools

  • ClinicalTrials.gov - Trial registration and results
  • Cochrane Library - Systematic reviews of trials
  • FDA / EMA guidance documents - Regulatory requirements
  • nQuery / PASS / G*Power - Sample size software
  • CONSORT / SPIRIT checklists - Reporting standards

Output Format

  • Sample size as a table: assumptions, formula, per-arm and total N.
  • Trial design as a structured summary: phase, design type, arms, blinding, duration.
  • CONSORT flow diagram description with all participant numbers.
  • Statistical analysis plan with pre-specified primary and secondary analyses.

Quality Checklist

  • PICO clearly defined
  • Primary endpoint is clinically meaningful and measurable
  • Sample size assumptions explicitly stated with references
  • Dropout rate factored into sample size
  • Randomization and blinding method specified
  • Multiple comparison adjustment for secondary endpoints
  • Interim analysis boundaries pre-specified if applicable
  • ITT and per-protocol populations defined
  • Regulatory guideline alignment noted (FDA/EMA/ICH)

Frequently asked questions

What does the Clinical Trial AI skill do?

Designs and analyzes clinical trials including sample size calculation, randomization schemes, endpoint selection, CONSORT reporting, and interim analysis planning; trigger when users ask about RCTs, Phase I-IV trials, or clinical study design.

Why use Clinical Trial on TypingMind?

Because you install it once and use it with any model. Clinical Trial is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Clinical Trial in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/beita6969/ScienceClaw/tree/main/skills/clinical-trial. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Clinical Trial?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Clinical Trial?

As many as you like. As long as a model supports skills, you can use Clinical Trial with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Clinical Trial AI skill free?

Yes. It is published on GitHub by beita6969 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇