|
| 1 | +# MedSci Skills Promotion Plan |
| 2 | + |
| 3 | +Status date: 2026-05-23 |
| 4 | + |
| 5 | +## Current Snapshot |
| 6 | + |
| 7 | +- GitHub: 105 stars, 30 forks, 9 open issues. |
| 8 | +- Traffic window: 2026-05-08 to 2026-05-21. |
| 9 | +- Views: 2,489 total / 844 unique. |
| 10 | +- Clones: 3,227 total / 456 unique. |
| 11 | +- Top referrers: Threads 402, GitHub 325, Google 288, Reddit 126, ChatGPT 58, Aperivue 28. |
| 12 | +- Current public surface: 40 skills, three public end-to-end demos, Zenodo concept DOI `10.5281/zenodo.20155321`. |
| 13 | + |
| 14 | +## Tier 1: Community Visibility |
| 15 | + |
| 16 | +### Awesome Lists |
| 17 | + |
| 18 | +`awesome-claude-code`: no existing medsci-skills PR found in the checked search. Do not create a PR in this cycle. Next cycle task: re-check the maintainer policy, then submit a small one-line addition with the DOI and demo links. |
| 19 | + |
| 20 | +Candidate lists to inspect before outreach: |
| 21 | + |
| 22 | +| Candidate | URL | Likely route | Fit | |
| 23 | +|---|---|---|---| |
| 24 | +| Awesome Claude | https://github.com/ai-for-developers/awesome-claude | Pull request titled `Add: MedSci Skills` | Good fit for Claude/agent-skill ecosystem visibility. | |
| 25 | +| Awesome LLM Apps | https://github.com/Shubhamsaboo/awesome-llm-apps | Issue or pull request after checking contribution conventions | Possible fit only if framed as runnable research workflow templates, not a generic link. | |
| 26 | +| Awesome Healthcare AI | https://github.com/medtorch/awesome-healthcare-ai | Pull request to relevant tools/resources section | Good medical AI audience fit; emphasize research workflow and reporting compliance. | |
| 27 | +| Awesome AI for Science | https://github.com/ai-boost/awesome-ai-for-science | Pull request to research workbench or medical AI section | Good science-tooling fit; keep entry concise and evidence-backed. | |
| 28 | + |
| 29 | +### Reddit Draft Outlines |
| 30 | + |
| 31 | +PII policy: no manuscript IDs, no unpublished study names, no author names, no project-specific identifiers, and no PMID lists in post bodies or comments. Run the PII gate before posting. |
| 32 | + |
| 33 | +#### r/ClaudeAI |
| 34 | + |
| 35 | +Title: `I built 40 Claude Code skills for medical research workflows, with public demos and validators` |
| 36 | + |
| 37 | +Body outline: |
| 38 | + |
| 39 | +- One-sentence problem: medical research work involves many brittle handoffs from literature search to manuscript and submission. |
| 40 | +- What is shipped: 40 Claude Code skills, three public demo pipelines, validator checks, citation/DOI metadata. |
| 41 | +- Why Claude-specific: skills package repeatable procedures, guardrails, and routing patterns rather than one-off prompts. |
| 42 | +- Invite feedback on install friction, skill structure, and missing workflows. |
| 43 | + |
| 44 | +First comment: |
| 45 | + |
| 46 | +```text |
| 47 | +Repo: https://github.com/Aperivue/medsci-skills |
| 48 | +DOI: https://doi.org/10.5281/zenodo.20155321 |
| 49 | +Best starting points: README demos, /setup-medsci, /verify-refs, /meta-analysis, /check-reporting. |
| 50 | +``` |
| 51 | + |
| 52 | +#### r/medicalAI |
| 53 | + |
| 54 | +Title: `Open-source medical research workflow skills: references, reporting checks, meta-analysis, and submission hygiene` |
| 55 | + |
| 56 | +Body outline: |
| 57 | + |
| 58 | +- Lead with safety/hygiene: citation checks, reporting guideline checks, PII guard, public datasets only in demos. |
| 59 | +- Show the clinical research workflow: literature search, full-text retrieval, study design, statistics, figures, manuscript, reporting, revision. |
| 60 | +- Ask for feedback on reporting-guideline coverage and external validation expectations. |
| 61 | + |
| 62 | +First comment: |
| 63 | + |
| 64 | +```text |
| 65 | +The demos use public/sample datasets only. I am especially looking for feedback on whether the validator and reporting-check surfaces are useful enough for independent reuse. |
| 66 | +``` |
| 67 | + |
| 68 | +#### r/medicine |
| 69 | + |
| 70 | +Title: `I open-sourced a physician-built toolkit for making research manuscripts less brittle` |
| 71 | + |
| 72 | +Body outline: |
| 73 | + |
| 74 | +- Avoid AI hype; frame as workflow documentation and QC automation. |
| 75 | +- Mention that it is not clinical decision support and does not process patient data in demos. |
| 76 | +- Ask for practical feedback from clinicians who write or review manuscripts. |
| 77 | + |
| 78 | +First comment: |
| 79 | + |
| 80 | +```text |
| 81 | +This is aimed at research workflow hygiene, not patient care. The most useful criticism would be: what would make this trustworthy enough to try on a low-risk manuscript draft? |
| 82 | +``` |
| 83 | + |
| 84 | +### Hacker News |
| 85 | + |
| 86 | +Candidate title: `Show HN: MedSci Skills, Claude Code workflows for medical research manuscripts` |
| 87 | + |
| 88 | +Timing: weekday morning Pacific Time. Post only after the README/Aperivue sync is live and the repo has no known PII hygiene blockers. |
| 89 | + |
| 90 | +## Tier 3: JOSS Submission Prep |
| 91 | + |
| 92 | +JOSS is a good medium-term target, but the current cycle should stop at prep. The refreshed 2026 criteria emphasize: |
| 93 | + |
| 94 | +- 750-1750 word paper with required sections. |
| 95 | +- Evidence of research impact or credible near-term significance. |
| 96 | +- Six months of public development history before submission. |
| 97 | +- Open-source practice signals: tests, CI, releases, changelog, documentation, contribution pathway. |
| 98 | +- Transparent AI usage disclosure. |
| 99 | + |
| 100 | +This cycle adds `paper.md`, `paper.bib`, and `CONTRIBUTING.md`. Do not submit to JOSS without a user confirmation pass and a fresh criteria check. |
| 101 | + |
| 102 | +### Pre-submission Checklist |
| 103 | + |
| 104 | +- [x] MIT `LICENSE`. |
| 105 | +- [x] `CITATION.cff` refreshed for v3.1.0 date/version. |
| 106 | +- [x] Zenodo concept DOI `10.5281/zenodo.20155321`. |
| 107 | +- [x] README, skill documentation, and three public demos. |
| 108 | +- [x] Validator and contract checks in repository scripts/CI. |
| 109 | +- [x] `CONTRIBUTING.md` added in this cycle. |
| 110 | +- [x] `paper.md` outline and `paper.bib` seed references added in this cycle. |
| 111 | +- [ ] Fresh public-history check: JOSS currently expects more than six months of public development history before submission. |
| 112 | +- [ ] Concrete external adoption/reuse evidence for the research impact statement. |
| 113 | +- [ ] Fresh JOSS criteria review immediately before submission. |
| 114 | + |
| 115 | +## Tier 2: Deferred |
| 116 | + |
| 117 | +- Society newsletter outreach. |
| 118 | +- X/Threads mention strategy beyond current organic traffic. |
| 119 | +- Aperivue blog post. |
| 120 | +- Main page redesign. |
| 121 | + |
| 122 | +## External Maintainer Follow-up Drafts |
| 123 | + |
| 124 | +### OpenClaw Issue #31 |
| 125 | + |
| 126 | +Status: opened 2026-05-13; 10 days elapsed as of 2026-05-23; no comments observed in the working plan. Re-ping threshold: 2026-06-12, or earlier only with explicit user approval. |
| 127 | + |
| 128 | +Draft: |
| 129 | + |
| 130 | +```text |
| 131 | +Hi, quick follow-up on this. MedSci Skills has now added the v2.10 public hygiene updates: 40-skill roster sync, expanded PII validator coverage, and refreshed meta-analysis/reference-checking surfaces. If this still fits OpenClaw's scope, I would be happy to adjust the entry format or split the medical-research workflow pieces into a narrower listing. |
| 132 | +``` |
| 133 | + |
| 134 | +### PR #18 |
| 135 | + |
| 136 | +Action remains separate from this PR. Close only after explicit user confirmation: |
| 137 | + |
| 138 | +```text |
| 139 | +Superseded by #23 -- v1.2.0 full-author cross-check + PubMed efetch authoritative path merged via PR #23 (2026-05-19). Closing this branch. |
| 140 | +``` |
| 141 | + |
| 142 | +## PII Gate |
| 143 | + |
| 144 | +Before any external post, PR body, issue comment, or commit message: |
| 145 | + |
| 146 | +```bash |
| 147 | +bash scripts/validate_skills.sh |
| 148 | +``` |
| 149 | + |
| 150 | +Also run the publication guard in `~/.claude/rules/oss-publication-pii-guard.md` if available. External copy must have zero manuscript IDs, unpublished project IDs, real collaborator names, patient-level examples, or PMID lists. Keep raw blocklist patterns in validator code only, not in promotional copy. |
0 commit comments