Individual skill
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.
Research-Toolkit-Skills/skills/rt-desk-reject-risk/SKILL.md
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,400
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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
