Skip to content

Question: inclusion process for external skill collections (medsci-skills) #31

Description

@Yoojin-nam

Hi OpenClaw team — really impressive aggregation work, especially the curation across 12+ source repositories.

I maintain medsci-skills, a 39-skill MIT-licensed Claude Code skill collection focused specifically on the medical-manuscript pipeline (PubMed search with anti-hallucination citation verification, IRB protocol drafting, IMRAD writing, 33-guideline EQUATOR reporting compliance, peer review, revision response). It's built and used by a practicing radiologist, with three end-to-end demos that produce submission-ready manuscripts from public datasets in under 10 minutes. v3.0.0 is archived on Zenodo for academic citation.

I noticed that the README mentions aggregating 12+ open-source skill repositories but I couldn't find a CONTRIBUTING.md or a documented inclusion process. Before sending a PR, I wanted to ask:

  1. Preferred format: Do you prefer (a) a PR adding a single linked entry to the README, (b) a structured manifest file (e.g., YAML/JSON) listing source repos, or (c) a category-specific listing under a particular section?
  2. Mirror vs link-only: Are skills from external repos mirrored into your skills/ directory, or only linked from the README?
  3. Quality gates: Are there any inclusion criteria (minimum stars, license requirements beyond MIT/Apache/BSD, demo coverage, contributor identity)?

Happy to follow whatever format you prefer. Repo for reference: https://github.com/Aperivue/medsci-skills

Thanks for the work on this — it's a great resource for the biomedical AI community.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions