rt-venue-reframe
Use after a rejection, or when switching target journals, to turn a manuscript framed for one venue into one framed for another. Produces a concrete reframing diff — introduction arc, contribution claim, evidence to add or cut, house style, format — by reading both venues' own packs. Complements rt-journal-match, which picks the venue; this one does the rewrite plan.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-venue-reframe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Cross-Venue Reframe (rt-venue-reframe) `rt-journal-match` answers *which venue next*. This answers the question that immediately follows and that nothing else in the repository covers: **what actually has to change in the paper.** Authors do this after almost every rejection, and they do it badly — usually by swapping the journal name in the cover letter and resubmitting. A real reframe is a diff across five layers, and both endpoints are already documented in this repo: the source venue's pack and the target venue's pack. ## When to trigger - A paper was rejected at venue A and the next rung is venue B. - The author is choosing between two live targets and wants to know the cost of each. - An editor or referee said "this reads like a *<other venue>* paper". - A paper written for an international venue is being re-aimed at a Chinese venue, or the reverse — the largest reframe distance in this repository. ## Inputs 1. **From venue** and **to venue** — as `venue_id`s in [`venue-index.tsv`](../../../shared-resources/journal-selection/venue-index.tsv). If the author only names a rejection, take the next rung from [`ladder.tsv`](../../../shared-resources/journal-selection/ladder.tsv)
- When to trigger
- Inputs
- Method — diff five layers, in this order
- Hard rules
- Output format
- Anti-patterns
What does the rt-venue-reframe skill do?
Use after a rejection, or when switching target journals, to turn a manuscript framed for one venue into one framed for another. Produces a concrete reframing diff — introduction arc, contribution claim, evidence to add or cut, house style, format — by reading both venues' own packs. Complements rt-journal-match, which picks the venue; this one does the rewrite plan.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-venue-reframe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.