Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
A skill your agent uses when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the…
MITAuto-check passed
Install Iros Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/IROS-Skills/skills/iros-workflow .claude/skills/iros-workflow && rm -rf skills-srcUse ~/.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/
Install the "iros-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflow into .claude/skills/iros-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-workflow", 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 install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflowType 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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/IROS-Skills/skills/iros-workflow .agents/skills/iros-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iros-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflow into .agents/skills/iros-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-workflow", 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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/IROS-Skills/skills/iros-workflow .cursor/skills/iros-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iros-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflow into .cursor/skills/iros-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-workflow", 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 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path IROS-Skills/skills/iros-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/IROS-Skills/skills/iros-workflow .gemini/skills/iros-workflow && rm -rf skills-srcUse ~/.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/
Install the "iros-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflow into .gemini/skills/iros-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-workflow", 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.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-workflowInstalls 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).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/IROS-Skills/skills/iros-workflow .github/skills/iros-workflow && rm -rf skills-srcUse ~/.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/
Install the "iros-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflow into .github/skills/iros-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-workflow", 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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/IROS-Skills/skills/iros-workflow .opencode/skills/iros-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iros-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-workflow into .opencode/skills/iros-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-workflow", 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
iros-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 538 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the…
- Planning an IROS project timeline from venue fit through the spring paper deadline
- SKILL.md covers The fall-venue rhythm (2026…, Milestones, Backward plan from the paper… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The separate video deadline
What it does
Iros Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.
Its SKILL.md is about 1.1k 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
- Planning an IROS project timeline from venue fit through the spring paper deadline
- The separate video deadline
- The summer review silence
- The June notification
Example prompts
- “/iros-workflow”
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
Iros Workflow loads about 1.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 538 words of instructions outside code blocks.
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). 538 words, ~1,102 tokens.
Download SKILL.mdSave it as
.claude/skills/iros-workflow/SKILL.md (or your agent's skills folder).- name
- iros-workflow
- description
- Use when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.
IROS Workflow
Use this as the project-management skill for an IROS submission. Replace every date with the current official timetable and work backward from PaperPlaza cutoffs.
IROS is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. It is co-sponsored by IEEE RAS and the Robotics Society of Japan (RSJ) — hence "IEEE/RSJ" — and the organizing committee rotates yearly between regions, so re-check the current CFP and committee page rather than carrying names or rules forward. The cost model is registration plus any per-page charge, and proceedings go to IEEE Xplore.
The fall-venue rhythm (2026 shape)
IROS is the fall IEEE-RAS mega-venue, the seasonal counterpart to ICRA's spring cycle. The 2026 edition ran a spring submission into an autumn conference:
- Paper deadline in early spring (2026: March 2).
- Video attachment a few days later (2026: March 5) — a distinct cutoff, not tied to the paper.
- A long summer review silence, then notification in mid-June (2026: June 16).
- Camera-ready in July (2026: July 10), then the conference in late September/October (2026: Sept 27 - Oct 1, Pittsburgh).
Knowing you are on the fall calendar changes routing: a project that misses IROS's spring deadline has CoRL and the next ICRA as nearer alternatives than waiting a full IROS year.
Milestones
- Venue fit: confirm the contribution is an integrated intelligent system with credible robot evidence.
- Evidence lock: freeze the platform, task distribution, trial protocol, baselines, and the video plan.
- Paper deadline: upload the anonymous PDF (references counted in the page budget) and PaperPlaza fields.
- Video deadline: upload the ≤ 60 s / ≤ 10 MB attachment by its own cutoff.
- Review silence: nothing to do but keep the robot and logs intact for camera-ready.
- Notification: triage reviews; there is traditionally no rebuttal, so plan camera-ready edits instead.
- Camera-ready: de-anonymize, integrate meta-review asks, file the IEEE copyright form, register.
- Presentation: at least one author presents in person; prepare the talk and any live/updated video.
Show full SKILL.md (218 more words)Show less
Backward plan from the paper deadline
| Weeks out (heuristic) | Real-robot systems milestone |
|---|---|
| 10+ | Platform frozen; task distribution and success criterion defined |
| 8 | Baselines implemented on the same hardware for a fair comparison |
| 6 | Main trials run, resets logged, failures categorized |
| 4 | Sim-to-real study complete; the gap is a number, not a hope |
| 3 | Full draft in IEEE two-column format; references budgeted as content |
| 2 | Video footage banked from real sessions; rough 60 s cut assembled |
| 1 | Anonymity sweep across PDF, figures, and video; PaperPlaza PINs collected |
| 0 | Paper uploaded; video by its separate cutoff |
These offsets are planning heuristics only — anchor each to the current official timetable, never to a previous cycle's calendar.
Failure modes by stage
- Filming on deadline week produces worse footage and worse anonymity than banking clips all along.
- Treating references as free space overruns the budget, because IROS counts them in.
- Assuming a rebuttal exists wastes the notification window; IROS traditionally ships reviews with the decision, so the only lever is camera-ready.
- Letting the robot get reconfigured before camera-ready makes a requested extra trial impossible.
Coordination notes
- Assign one named owner for the video and one for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF and video, since the camera-ready must trace to the reviewed version.
Output format
[Current stage] idea / experiments / writing / submission / video / review / notified / camera-ready
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page-budget/anonymity/robot-evidence/video/transfer>
[Owner map] <task -> person or role>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in IROS-Skills/skills/iros-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iros Workflow 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iros Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| VenueLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Table Fitasgeirtj/system_prompts_leaks | 69k | — | ~772 | Automated safety check: Pass | CC0-1.0 | |
| Furniture Fit Checkpascalorg/editor | 25k | — | ~5.1k | Automated safety check: Pass | MIT |
Similar skills
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Venue
LeoYeAI/openclaw-master-skills
Music venue where AI agents stream concerts as mathematics. An agent skill from LeoYeAI/openclaw-master-skills.
Table Fit
asgeirtj/system_prompts_leaks
Keep a Markdown table readable in a narrow terminal of about 100 display columns - a wide table or one carrying prose in its cells wraps into unreadable ragged rows.
Furniture Fit Check
pascalorg/editor
Checks whether a sofa, table, bed or appliance fits in a measured Pascal room and reports only what the evidence supports, or asks for the missing measurements.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Questions about Iros Workflow
What does Iros Workflow do?
A skill your agent uses when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the…. Iros Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.
When should I use Iros Workflow?
Iros Workflow fits situations like: planning an IROS project timeline from venue fit through the spring paper deadline; the separate video deadline; the summer review silence; the June notification.
How do I install Iros Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a claude-code`. Or copy the skill folder (IROS-Skills/skills/iros-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iros-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Iros Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-workflow -a codex`. Or copy the skill folder (IROS-Skills/skills/iros-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iros-workflow in your project. Codex loads it when a task matches its description.
Can I use Iros Workflow 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 iros-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iros-workflow, .gemini/skills/iros-workflow, .github/skills/iros-workflow and .opencode/skills/iros-workflow in your project.
What does Iros Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Iros Workflow is instructions for the agent only.
Does Iros Workflow 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 Iros Workflow 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 Iros Workflow use?
Iros Workflow 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 Iros Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Iros Workflow?
Skills that share tags, products or a category with Iros Workflow: Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Venue (LeoYeAI/openclaw-master-skills, 2.2k stars) and Table Fit (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iros Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.