Individual skill

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.

Research-Toolkit-Skills/skills/rt-venue-reframe/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top