Agent skill

Rt Desk Reject Risk

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

Use before submitting to score a manuscript against a specific venue's own desk-reject triggers and return a ranked, fixable risk report.

MITAuto-check passed

Install Rt Desk Reject Risk

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills rt-desk-reject-risk --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Research-Toolkit-Skills/skills/rt-desk-reject-risk .claude/skills/rt-desk-reject-risk && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "rt-desk-reject-risk" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk into .claude/skills/rt-desk-reject-risk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rt-desk-reject-risk", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills rt-desk-reject-risk --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Research-Toolkit-Skills/skills/rt-desk-reject-risk .agents/skills/rt-desk-reject-risk && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rt-desk-reject-risk" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk into .agents/skills/rt-desk-reject-risk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rt-desk-reject-risk", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills rt-desk-reject-risk --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Research-Toolkit-Skills/skills/rt-desk-reject-risk .cursor/skills/rt-desk-reject-risk && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rt-desk-reject-risk" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk into .cursor/skills/rt-desk-reject-risk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rt-desk-reject-risk", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Research-Toolkit-Skills/skills/rt-desk-reject-risk

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills rt-desk-reject-risk --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Research-Toolkit-Skills/skills/rt-desk-reject-risk .gemini/skills/rt-desk-reject-risk && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "rt-desk-reject-risk" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk into .gemini/skills/rt-desk-reject-risk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rt-desk-reject-risk", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills rt-desk-reject-risk

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Research-Toolkit-Skills/skills/rt-desk-reject-risk .github/skills/rt-desk-reject-risk && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "rt-desk-reject-risk" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk into .github/skills/rt-desk-reject-risk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rt-desk-reject-risk", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills rt-desk-reject-risk --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Research-Toolkit-Skills/skills/rt-desk-reject-risk .opencode/skills/rt-desk-reject-risk && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rt-desk-reject-risk" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Research-Toolkit-Skills/skills/rt-desk-reject-risk into .opencode/skills/rt-desk-reject-risk/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rt-desk-reject-risk", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: rt-desk-reject-risk
GitHub stars: 1.2k
Token cost: ~1.4k tokens
SKILL.md length: 687 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Use before submitting to score a manuscript against a specific venue's own desk-reject triggers and return a ranked, fixable risk report.

Works in 5 steps: Scope miss — the contribution is not the… → Framing miss — right result, wrong "why… → Format/anonymity breach — length,… → …
Return a ranked
SKILL.md covers When to trigger, Method, Hard rules and Output format, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rt Desk Reject Risk is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜覆盖主流期刊的… The licence is MIT.

When your agent uses it

Return a ranked
Fixable risk report
Rather than applying generic advice

Example prompts

“/rt-desk-reject-risk”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Scope miss — the contribution is not the kind of contribution this venue
Framing miss — right result, wrong "why it matters" for this audience.
Format/anonymity breach — length, abstract, blinding, reference style, ORCID,
Evidence baseline — a robustness or design check the venue treats as table
Policy — data-and-code availability, ethics/IRB, preregistration, conflicts,

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rt Desk Reject Risk loads about 1.4k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 687 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~88
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 687 words, ~1,412 tokens.

Download SKILL.mdSave it as .claude/skills/rt-desk-reject-risk/SKILL.md (or your agent's skills folder).

name: rt-desk-reject-risk
description: 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.

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, take the row's pack_dir (depth) or profile_path (breadth) and read:

the ## Common desk-reject triggers section (or the pack's Desk-reject and triage / decline-without-review variant) in its *-submission, *-review-process and *-topic-selection skills;
the scope and format constraints in resources/official-source-map.md, read live — length caps, abstract style, anonymity rules and fee/policy gates are volatile and are a large share of real desk rejects.

If the venue publishes no explicit trigger list (about 4 in 10), say so, and fall back to the venue's fit and house-style skills plus the generic gate in Step 3 — do not invent venue-specific triggers.

Step 2 — score each trigger. For every documented trigger, judge the manuscript against it and assign:

Level	Meaning
Fatal	The editor will desk-reject on this alone. Fix before upload or change venue.
Likely	A common desk cause at this venue; the paper is exposed but not certain to fail.
Watch	Survivable, but it is the first thing a referee will raise.
Clear	Documented trigger the paper demonstrably does not hit.

Cite the evidence in the manuscript for each judgement (a section, a table, a claim), not a general impression. A risk with no located evidence is a hypothesis — mark it as one, or drop it.

Step 3 — the universal gate (applies at every venue, on top of the venue's own):

Scope miss — the contribution is not the kind of contribution this venue publishes. This is the single largest desk cause and the least fixable.
Framing miss — right result, wrong "why it matters" for this audience.
Format/anonymity breach — length, abstract, blinding, reference style, ORCID, supplementary rules. Mechanical and always worth fixing.
Evidence baseline — a robustness or design check the venue treats as table stakes and the paper omits.
Policy — data-and-code availability, ethics/IRB, preregistration, conflicts, prior dissemination or dual-submission rules.

Step 4 — return a cost-ranked fix list. Sort by (severity × 1/effort). Distinguish fixes that are edits from fixes that need new analysis; say explicitly when the honest conclusion is "this venue is wrong for this paper" and route to rt-journal-match.

Show full SKILL.md (188 more words)Show less

Hard rules

Venue-conditional, never generic. Every Fatal/Likely must trace to a trigger the venue's own pack or source map states. Generic advice belongs in Step 3 and must be labelled as such.
Volatile constraints are read at scoring time from resources/official-source-map.md — never quoted from memory.
No fabricated triggers. If the pack does not document a trigger list, say so.
Do not present this as a prediction of the editor's decision. It is a documented-risk audit; there is no acceptance-probability number to give, and inventing one would be false precision.
Defer scope/fit judgement to the venue's *-topic-selection skill.

Output format

【Venue】<display name>  (pack: <pack_dir | profile_path>)
【Trigger source】<n> documented triggers read from <files>  |  none documented
【Source-map read】<date>
【Fatal】  trigger — evidence in the manuscript — fix (edit | new analysis)
【Likely】 …
【Watch】  …
【Clear】  triggers the paper demonstrably passes
【Cost-ranked fixes】1..n, each: severity · effort · what to change
【Verdict】submit as-is / fix first (n items) / wrong venue → rt-journal-match

Anti-patterns

Producing a percentage "acceptance chance". The inputs do not support it.
Listing every trigger as Watch — a report with no ranking is not a report.
Scoring against a venue's reputation instead of its documented triggers.
Running this instead of rt-submission-readiness; they check different things and the mechanical bar comes first.
Treating a Clear on all triggers as an acceptance signal. Surviving the desk means the paper reaches referees, nothing more.

Next: rt-simulated-referee once the desk gate is clear, then rt-replication-package for the deposit.

Files

Just SKILL.md in Research-Toolkit-Skills/skills/rt-desk-reject-risk of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Rt Desk Reject Risk next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rt Desk Reject Risk compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rt Desk Reject Risk this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.4k	Automated safety check: Pass	MIT	14 days ago
Claw Scoreopenclaw/openclaw	392k	—	~2.5k	Automated safety check: Pass	MIT	today
Tooluniverse Polygenic Risk Scorewu-yc/LabClaw	1.1k	2 repos	~3.7k	Automated safety check: Pass	None	6 mo ago
Dd Risk ScoringAbilityai/trinity	636	—	~736	Automated safety check: Pass	Apache-2.0	yesterday
Cve Risk Scoretransilienceai/communitytools	563	—	~565	Automated safety check: Notes	MIT	2 mo ago
Dpia Risk Scoringmukul975/Privacy-Data-Protection-Skills	301	—	~1k	Automated safety check: Pass	Apache-2.0	6 mo ago

Similar skills

Claw Score
openclaw/openclaw
Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.
392k GitHub stars~2.5k tokensUpdated today
Auto-check passed
Tooluniverse Polygenic Risk Score
wu-yc/LabClaw
Build and interpret polygenic risk scores (PRS) for complex diseases using GWAS summary statistics.
1.1k GitHub starsUsed in 2 repos~3.7k tokens
Research & ScienceAuto-check passed
Dd Risk Scoring
Abilityai/trinity
Calculate weighted risk scores from specialist agent reports.
636 GitHub stars~736 tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Cve Risk Score
transilienceai/communitytools
Retrieve CVE risk scores from NVD. An agent skill from transilienceai/communitytools.
563 GitHub stars~565 tokensUpdated 2 mo ago
SecurityAuto-check: notes
Dpia Risk Scoring
mukul975/Privacy-Data-Protection-Skills
Provides a structured risk scoring methodology for Data Protection Impact Assessments aligned with ENISA threat taxonomy and ISO 29134.
301 GitHub stars~1k tokensUpdated 6 mo ago
Legal & ComplianceAuto-check passed
Harness Score
ruvnet/ruflo
5-dimension harness readiness scorecard from metaharness score {path}.
74k GitHub stars~605 tokensUpdated yesterday
DevelopmentAuto-check: notes

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Rt Desk Reject Risk

What does Rt Desk Reject Risk do?

Use before submitting to score a manuscript against a specific venue's own desk-reject triggers and return a ranked, fixable risk report. Rt Desk Reject Risk is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use before submitting to score a manuscript against a specific venue's own desk-reject triggers and return a ranked, fixable risk report.

When should I use Rt Desk Reject Risk?

Rt Desk Reject Risk fits situations like: return a ranked; fixable risk report; rather than applying generic advice.

How do I install Rt Desk Reject Risk in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a claude-code`. Or copy the skill folder (Research-Toolkit-Skills/skills/rt-desk-reject-risk in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/rt-desk-reject-risk in your project. Claude Code loads it when a task matches its description.

How do I install Rt Desk Reject Risk in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a codex`. Or copy the skill folder (Research-Toolkit-Skills/skills/rt-desk-reject-risk in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/rt-desk-reject-risk in your project. Codex loads it when a task matches its description.

Can I use Rt Desk Reject Risk in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-desk-reject-risk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rt-desk-reject-risk, .gemini/skills/rt-desk-reject-risk, .github/skills/rt-desk-reject-risk and .opencode/skills/rt-desk-reject-risk in your project.

What does Rt Desk Reject Risk need to run?

SKILL.md names no scripts, command-line tools or credentials: Rt Desk Reject Risk is instructions for the agent only.

Does Rt Desk Reject Risk access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rt Desk Reject Risk safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rt Desk Reject Risk use?

Rt Desk Reject Risk is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rt Desk Reject Risk use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rt Desk Reject Risk?

Skills that share tags, products or a category with Rt Desk Reject Risk: Claw Score (openclaw/openclaw, 392k stars), Tooluniverse Polygenic Risk Score (wu-yc/LabClaw, 1.1k stars), Dd Risk Scoring (Abilityai/trinity, 636 stars) and Cve Risk Score (transilienceai/communitytools, 563 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rt Desk Reject Risk?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Rt Desk Reject Risk

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Desk-Reject Risk (rt-desk-reject-risk)

When to trigger

Method

Hard rules

Output format

Anti-patterns

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Rt Desk Reject Risk