rt-workflow
Use to sequence a manuscript across venues — which cross-journal toolkit skill to invoke next, from picking a target journal through execution, submission-readiness, simulated review, rebuttal, and the replication package. Routes; it does not replace the per-journal depth packs or the specialized toolkit skills.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-workflow --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-Journal Workflow Router (rt-workflow) The author-side loop that runs *across* journals, complementing the per-journal depth packs (which answer "how do I clear THIS venue's bar?"). Each step is backed by a canonical capability doc in `shared-resources/`. ## When to trigger - You have a result/draft and don't yet know the venue, or just got a reject and need the next target. - You are mid-project and want the next cross-journal step. - You want the end-to-end sequence: pick → execute → ready → rehearse → submit → rebut → replicate. ## The loop (and the skill that owns each step) 1. **`rt-journal-match`** — profile the paper → ranked reach/match/safe shortlist + resubmission ladder. 2. **`rt-venue-reframe`** — when the target changes (a reject, or a switch), diff the manuscript from the old venue's framing to the new one. 3. **`rt-execution-bridge`** — run the analysis through the StatsPAI / Stata MCP tools (estimate + audit), not just advise it. 4. **`rt-submission-readiness`** — go/no-go scorecard on the manuscript against the target venue's bar. 5. **`rt-desk-reject-risk`** — score the draft against the target's own documented desk-reject triggers before uploading. 6. **`r
- When to trigger
- The loop (and the skill that owns each step)
- Routing table
- How it relates to the per-journal packs
- Anti-patterns
- Output format
What does the rt-workflow skill do?
Use to sequence a manuscript across venues — which cross-journal toolkit skill to invoke next, from picking a target journal through execution, submission-readiness, simulated review, rebuttal, and the replication package. Routes; it does not replace the per-journal depth packs or the specialized toolkit skills.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-workflow --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.