rt-desk-reject-risk
Use before submitting to score a manuscript against a specific venue's own desk-reject triggers and return a ranked, fixable risk report. Venue-conditional — it reads the target's documented triggers rather than applying generic advice. Run it after rt-submission-readiness clears the mechanical bar and before the paper is uploaded.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk --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.
# Desk-Reject Risk (rt-desk-reject-risk) Desk rejection is the modal outcome at a strong venue, it arrives before any referee reads the paper, and it costs weeks for reasons that are almost always documented in advance. This repository already carries those reasons — **456 of 743 indexed venues (61%) publish an explicit desk-reject section in their pack** — but nothing turned them into a check a paper could be scored against. `rt-submission-readiness` answers *"is the manuscript mechanically complete?"*. This answers the different and harder question: **"given this specific venue's stated triggers, what will get this desk-rejected, and what is the cheapest fix?"** ## When to trigger - A target venue is chosen and the paper is near-final. - An author asks "will this survive the editor?" or "why did the last one get desked?" - Immediately after `rt-venue-reframe`, to score the reframed draft against its new home. - Before a resubmission up the ladder, where the previous desk reject is evidence. ## Method **Step 1 — locate the venue's triggers.** From [`venue-index.tsv`](../../../shared-resources/journal-selection/venue-index.tsv), take the row's `pack_dir` (depth) or `profile_path` (
- When to trigger
- Method
- Hard rules
- Output format
- Anti-patterns
What does the rt-desk-reject-risk skill do?
Use before submitting to score a manuscript against a specific venue's own desk-reject triggers and return a ranked, fixable risk report. Venue-conditional — it reads the target's documented triggers rather than applying generic advice. Run it after rt-submission-readiness clears the mechanical bar and before the paper is uploaded.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk --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 984 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.