Back to skills
extension
Category: Productivity & OfficeNo API key required

clinical-cohort-protocol-designer

Index entry for an upstream research Skill intended for research work involving clinical cohort protocol designer. Maintained upstream by aipoch; source files are not included in this package.

personAuthor: OpenScientificSkillshubOpenAPI

clinical-cohort-protocol-designer — upstream index

This is an index-only record created by OpenScientificSkills. It contains an attributed catalog summary, but does not bundle, mirror, or redistribute the upstream Skill instructions, code, or assets.

What this Skill is for

This indexed Skill is intended for research work involving clinical cohort protocol designer. It helps researchers discover the upstream project that may provide instructions, templates, scripts, or workflow guidance for that task. Exact capabilities, requirements, and behavior must be confirmed in the canonical repository because they can change upstream.

Attributed upstream catalog summary:

Designs retrospective or prospective clinical cohort study protocols for biomedical and clinical research. Always use this skill when the user needs a cohort-based study plan rather than a general study idea, evidence summary, or mechanistic experiment design. Focus on cohort appropriateness, enrollment logic, baseline time-zero definition, follow-up structure, endpoint definition, variable collection, confounding...

Canonical source

  • Upstream author or maintainer: aipoch
  • Repository: https://github.com/aipoch/awesome-medical-research-skills
  • Upstream Skill path: clinical-cohort-protocol-designer/SKILL.md
  • Upstream license status: not verified

The CC0-1.0 value on this ModelScope entry applies only to the newly written index structure and explanatory text. It does not apply to the attributed upstream summary and does not grant any license to the upstream repository.

Before use

Open the canonical repository, review its current license, security posture, dependencies, and instructions, and obtain any permission required by the upstream author. Always treat the upstream repository as the source of truth.