Skip to content

Commit 46235c1

Browse files
GiaoLeeclaude
andcommitted
feat: update SKILL.md metadata format and eval reports across all skills
Rename author field to skill-author, remove redundant source links, add content improvements to multiple skills, and refresh eval report results. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 6981f5b commit 46235c1

204 files changed

Lines changed: 15808 additions & 8765 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

awesome-med-research-skills/Academic Writing/author-response-builder/SKILL.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,8 @@
22
name: author-response-builder
33
description: Turns reviewer comments into structured, professional point-by-point responses linked to manuscript revisions, clarifications, rebuttals, and additional analyses.
44
license: MIT
5-
author: aipoch
5+
skill-author: AIPOCH
66
---
7-
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
87

98
# Author Response Builder
109

@@ -141,6 +140,10 @@ This skill should:
141140
If the user provides only fragments of reviewer comments, vague revision notes, or no clear information about what has actually changed in the manuscript, do not immediately produce a full point-by-point response.
142141
First explain what is missing, ask focused follow-up questions, or recommend uploading the full review package and revision notes.
143142

143+
**Constructive pivot for incomplete revisions:** If the user has not completed revisions, do not simply refuse. Instead offer: "I can draft provisional responses for any revisions you can describe now, noting that final revision-linkage text should be confirmed once revisions are complete. Which comments have you already addressed?" This keeps the interaction productive without fabricating completed changes.
144+
145+
**Editor letter format:** Editor decision letters should be addressed as a single block response unless the editor letter contains enumerated action items. Tone should be slightly more formal than reviewer responses, and the opening should directly acknowledge the editorial decision.
146+
144147
### Step 2 — Identify the response unit
145148
Determine whether the response should be built:
146149
- comment by comment,
@@ -165,6 +168,13 @@ Check whether the response should point to:
165168
- limitation statement,
166169
- or no manuscript change with a transparent explanation.
167170

171+
### Step 4.5 — Tiered Output Mode
172+
173+
Apply the following output mode based on input complexity:
174+
175+
- **Simple mode** (2 or fewer comments, all fully resolved acceptances): Combine Sections F, G, and H into a single brief "Notes" block. Reserve the full 8-section structure for mixed-mode, partially-resolved, or rebuttal-containing responses.
176+
- **Complex mode** (5 or more comments): Section C must include a mode-distribution count (e.g., "3 acceptances, 2 explanations, 1 rebuttal, 1 additional-analysis, 1 partial-with-limit") rather than a generic "mixed" label.
177+
168178
### Step 5 — Draft the point-by-point response
169179
Construct each reply so that it:
170180
- acknowledges the comment,
@@ -233,6 +243,10 @@ When helpful, recommend uploading reviewer comments, editor letter, revision str
233243
- Do not overuse empty courtesy formulas.
234244
- Do not produce a confident full response package when the actual revision status is still too incomplete.
235245

246+
## Editorial Consequence Rule
247+
248+
When refusing to produce dismissive or reviewer-targeting language, explain the downstream editorial consequence: editors routinely interpret dismissive responses as author inflexibility and often rule in favor of the reviewer, increasing rejection probability. Frame the alternative bounded rebuttal as the strategically stronger choice — not just the polite one.
249+
236250
## Hard Rules
237251

238252
1. **Do not invent completed manuscript changes, analyses, experiments, or figure revisions.**

awesome-med-research-skills/Academic Writing/author-response-builder/eval_report_author-response-builder_result.json

Lines changed: 280 additions & 113 deletions
Large diffs are not rendered by default.

awesome-med-research-skills/Academic Writing/claim-strength-calibrator/SKILL.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,8 @@
22
name: claim-strength-calibrator
33
description: Calibrates manuscript claim strength so wording matches the actual evidence level, study design, and validation status.
44
license: MIT
5-
author: aipoch
5+
skill-author: AIPOCH
66
---
7-
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
87

98
# Claim Strength Calibrator
109

awesome-med-research-skills/Academic Writing/claim-strength-calibrator/eval_report_claim-strength-calibrator_result.json

Lines changed: 213 additions & 117 deletions
Large diffs are not rendered by default.

awesome-med-research-skills/Academic Writing/conference-abstract-writer/SKILL.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,8 @@
22
name: conference-abstract-writer
33
description: Condenses a full study into conference-submission abstract format. Use when adapting a manuscript abstract or study summary to meet a specific conference's word limit, structured format (Background/Methods/Results/Conclusion), character limits, or required section headings. Also triggers on "adapt my abstract for [conference]", "shorten my abstract to 250 words", "reformat for ASCO/ASGCT/SfN/AACR", "I need a conference abstract", or "cut my abstract to fit the word limit".
44
license: MIT
5-
author: aipoch
5+
skill-author: AIPOCH
66
---
7-
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
87

98
# Conference Abstract Adaptor
109

@@ -32,13 +31,15 @@ Out-of-scope:
3231
3332
## Supported Conference Formats
3433

34+
> ⚠️ **Conference requirements change annually.** Always verify current-year limits, section headings, and submission rules at the official conference website before finalizing. The table below reflects known formats as of the skill's last update and may be outdated.
35+
3536
| Conference | Limit | Format |
3637
|---|---|---|
3738
| **ASGCT** | 250 words | Structured: Background / Methods / Results / Conclusion |
3839
| **ASCO** | 260 words | Structured: Background / Methods / Results / Conclusions |
3940
| **AACR** | 300 words | Structured: Background / Methods / Results / Conclusions |
4041
| **ASM** | 300 words | Single-paragraph or structured (conference-dependent) |
41-
| **SfN** | 2,000 characters | Single paragraph (no headings) |
42+
| **SfN** | 2,000 characters (including spaces) | Single paragraph (no headings) |
4243
| **ESC / AHA / ACC** | 250–350 words | Structured (verify current year requirements) |
4344
| **Custom** | User-specified | User-specified |
4445

@@ -82,7 +83,9 @@ When cutting to fit the word limit:
8283
After adapting, provide:
8384
1. The adapted abstract, fully formatted
8485
2. The word count (or character count) with a clear note: `Word count: X / [limit]`
86+
- **For character-limited formats (e.g., SfN):** state the count as `[N] characters including spaces`. SfN and most character-limited conferences count spaces. Users should verify using a tool that counts spaces (e.g., Python `len()` or Word character count with spaces enabled).
8587
3. A one-line note on any content that was cut to fit the limit, so the user can decide whether to restore it
88+
4. **Word-limit conflict resolution:** If preserving the primary result, sample size N, and conclusion still exceeds the word limit after aggressive cutting, notify the user: "Preserving required elements (primary result, N, conclusion) results in [X] words vs. [limit]. Please indicate which secondary elements to deprioritize." Do not silently cut required elements.
8689

8790
### Step 5 — Final Check
8891

0 commit comments

Comments
 (0)