rt-submission-readiness
Use when an author is one revision away from submission and needs a venue-parameterized go/no-go scorecard on the actual manuscript: fit, identification, robustness, exhibits, exposition, venue mechanics, data/code, and pre-empted objections. Returns PASS/FLAG/FAIL per dimension, the blocking gaps, and the desk-reject risk. Reads the venue bar from the target pack + source-map.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-submission-readiness --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.
# Submission-Readiness Self-Check (rt-submission-readiness) The mechanical/structural go/no-go that catches avoidable desk rejects before you hit submit. Full rubric: [`shared-resources/submission-readiness/readiness-checklist.md`](../../../shared-resources/submission-readiness/readiness-checklist.md). It is the outward-facing analogue of the repo's internal `tools/quality_scorecard.py`. ## When to trigger - The draft is "done" and the author is about to submit to a named venue. - Before paying a submission fee / starting the portal. - After `rt-journal-match` selects the target and after `rt-execution-bridge` has run any empirical checks the paper depends on. ## Inputs to load 1. The manuscript or submission packet, including front matter, main text, exhibits, appendix, data/code statement, and cover letter if drafted. 2. The target journal pack's `README.md`, relevant skills, and `resources/official-source-map.md`. 3. Any executed analysis artifacts from `rt-execution-bridge`: result handles, audit gaps, robustness outputs, and replication/package notes. ## What it does Reads the target pack's skills + `resources/official-source-map.md`, inspects the actual manuscript (cite §/tab
- When to trigger
- Inputs to load
- What it does
- Decision contract
- Hard rules
- Output format
What does the rt-submission-readiness skill do?
Use when an author is one revision away from submission and needs a venue-parameterized go/no-go scorecard on the actual manuscript: fit, identification, robustness, exhibits, exposition, venue mechanics, data/code, and pre-empted objections. Returns PASS/FLAG/FAIL per dimension, the blocking gaps, and the desk-reject risk. Reads the venue bar from the target pack + source-map.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-submission-readiness --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.