corl-writing-style
Use when writing or revising a CoRL paper's prose — leading with the embodied task and the learned component, calibrating claims to evaluation scale, writing the mandatory Limitations section as a scored asset, fitting the argument into 8 pages, and satisfying a dual reviewer audience of ML and robotics readers.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-writing-style --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.
# CoRL Writing Style A CoRL paper is read by two audiences at once: reviewers fluent in learning methods who will probe the algorithmic claim, and reviewers fluent in robots who will probe the physical claim. Prose that serves only one of them loses the other's score. The style guidance here is about keeping both readers oriented inside 8 pages — with a mandatory Limitations section spending part
What does the corl-writing-style skill do?
Use when writing or revising a CoRL paper's prose — leading with the embodied task and the learned component, calibrating claims to evaluation scale, writing the mandatory Limitations section as a scored asset, fitting the argument into 8 pages, and satisfying a dual reviewer audience of ML and robotics readers.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-writing-style --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.