Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
A skill your agent uses when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December…
Install Infocom Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-workflow .claude/skills/infocom-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 "infocom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-workflow into .claude/skills/infocom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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/INFOCOM-Skills/skills/infocom-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 infocom-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-workflow .agents/skills/infocom-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 "infocom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-workflow into .agents/skills/infocom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 infocom-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-workflow .cursor/skills/infocom-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 "infocom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-workflow into .cursor/skills/infocom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 INFOCOM-Skills/skills/infocom-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 infocom-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-workflow .gemini/skills/infocom-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 "infocom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-workflow into .gemini/skills/infocom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 infocom-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 infocom-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/INFOCOM-Skills/skills/infocom-workflow .github/skills/infocom-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 "infocom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-workflow into .github/skills/infocom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 infocom-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 infocom-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/INFOCOM-Skills/skills/infocom-workflow .opencode/skills/infocom-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 "infocom-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-workflow into .opencode/skills/infocom-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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
infocom-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 634 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 IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December…
- Planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration
- SKILL.md covers Milestones, Backward plan from the…, The single-summer calendar… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The early-reject checkpoint
What it does
Infocom Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with backward-planning offsets for a networking paper and honest handling of the single-summer deadline.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering PDF. 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 IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration
- The early-reject checkpoint
- The December notification
- The IEEE Xplore camera-ready with PDF eXpress and eCF
Example prompts
- “/infocom-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
Infocom Workflow loads about 1.3k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 634 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). 634 words, ~1,323 tokens.
Download SKILL.mdSave it as
.claude/skills/infocom-workflow/SKILL.md (or your agent's skills folder).- name
- infocom-workflow
- description
- Use when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with backward-planning offsets for a networking paper and honest handling of the single-summer deadline.
INFOCOM Workflow
Use this as the project-management skill for an INFOCOM submission. Replace every date with the current official timetable and work backwards from the abstract/metadata deadline (in late July), which precedes the full-paper deadline by about a week. INFOCOM runs a single annual summer deadline, so a missed cycle costs roughly a year — plan the calendar as tightly as the paper.
INFOCOM is an IEEE ComSoc conference with no standing editor-in-chief and no article-processing charge. Rotating leadership is the per-edition General Co-Chairs and TPC Co-Chairs, appointed under ComSoc; the cost model is conference registration, and at least one author must register for the paper to enter IEEE Xplore. Chairs rotate yearly; re-check the organizing-committee page rather than carrying a name forward.
Milestones
- Venue fit: confirm INFOCOM over SIGCOMM/NSDI/MobiCom and confirm the paper is ready this
cycle (
infocom-topic-selection). - Evidence lock: freeze the system model, theorems/proofs, simulator setup, baselines, and the evaluation results.
- Abstract/metadata registration: enter real title, abstract (≤200 words), co-authors, and topic tags into EDAS by the abstract deadline (INFOCOM 2026: 24 Jul 2025; 2027: 24 Jul 2026).
- Full-paper submission: upload the anonymized IEEEtran PDF (INFOCOM 2026: 31 Jul 2025; 2027: 31 Jul 2026), within the 10-page / ≤9-page-of-text budget.
- Early-reject checkpoint (if the cycle runs one): INFOCOM 2027 posts early-reject on 9 Oct 2026 — a mid-cycle signal, not a final verdict.
- Notification: final decision (INFOCOM 2026: 8 Dec 2025; 2027: 8 Dec 2026).
- Camera-ready: eCF copyright, PDF eXpress validation, IEEE Xplore-compliant PDF (INFOCOM 2026: 9 Jan 2026), plus author registration.
- Presentation: at least one author registers and presents at the conference.
Backward plan from the full-paper deadline
| Weeks out (heuristic) | Networking-paper milestone |
|---|---|
| 12+ | Problem formulated; system model and assumptions fixed; baselines chosen |
| 10 | Theorems proved / protocol designed; simulator or testbed built |
| 8 | Experiments/simulations complete; seeds and configs logged |
| 6 | Analysis done; plots and tables built; proofs written up |
| 4 | Full draft in IEEEtran; measured against the 9-page text boundary (refs excluded) |
| 3 | Internal mock review by a reader from the other side (theory ↔ systems) |
| 2 | Baselines hardened, related-work delta sharpened, page budget met |
| 1 | Double-blind sweep on the PDF and metadata; abstract entered in EDAS |
| 0 | Full paper on EDAS within the budget; five-paper cap re-checked |
These offsets are planning heuristics only — anchor every one to the current Call for Papers, never to a previous cycle's calendar.
Show full SKILL.md (246 more words)Show less
The single-summer calendar reality
INFOCOM runs one annual research deadline in late July, with notification in December and the conference the following May. As of 2026-07-09, INFOCOM 2026 (Tokyo) is decided, so the live next target is INFOCOM 2027 (Honolulu; abstract 24 Jul 2026, paper 31 Jul 2026). Two planning consequences:
- A near-miss on the July deadline costs a full year at INFOCOM; a sibling flagship (SIGCOMM/NSDI/MobiCom) or a journal (ToN/JSAC) may have a nearer date — factor that into routing rather than idling.
- There is no rebuttal to plan for (traditionally): budget the pre-submission mock review as the one and only chance to hear "your baseline is unfair" from a friend instead of a reviewer.
Failure modes by stage
- Evidence still moving at week 4 forces last-minute simulation nobody has audited — the classic soundness reject.
- Discovering the paper is a page over at week 1 with appendices counted inside the nine pages — a not-reviewed outcome that editing weeks earlier would have prevented.
- Skipping the cross-side mock review forfeits the chance to catch an unstated assumption (theory reader) or an unrealistic topology (systems reader).
- Forgetting the five-paper cap on a group's submission sprint, so a sixth paper is dropped.
Coordination notes
- Assign one owner for the EDAS metadata/topic tags (they drive automated assignment) and another for the double-blind sweep; shared ownership is how both slip.
- Archive the exact submitted PDF and the simulator/testbed configuration — the camera-ready must match, and any released artifact must reproduce it.
Output format
[Current stage] idea / evidence / writing / abstract-registered / submitted / early-reject / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page budget / double-blind / evidence / baselines / author cap / registration>
[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 INFOCOM-Skills/skills/infocom-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Infocom 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 |
|---|---|---|---|---|---|---|
| Infocom Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 782 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9k | — | ~19k | Automated safety check: Pass | Apache-2.0 | |
| Harness Book Best Practicewquguru/harness-books | 3.2k | — | ~4.1k | Automated safety check: Pass | None | |
| Bookforge Korean Ebook PDF Makergongnyang/bookforge | 315 | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
Harness Book Best Practice
wquguru/harness-books
Best practices for working on the Harness books repo. An agent skill from wquguru/harness-books.
Bookforge Korean Ebook PDF Maker
gongnyang/bookforge
Produces book-style Korean ebook PDFs from a topic or finished manuscript, with six design styles, real book parts and quality-check gates before output.
- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
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…
Related
Categories
Questions about Infocom Workflow
What does Infocom Workflow do?
A skill your agent uses when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December…. Infocom Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with backward-planning offsets for a networking paper and honest handling of the single-summer deadline.
When should I use Infocom Workflow?
Infocom Workflow fits situations like: planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration; the early-reject checkpoint; the December notification; the IEEE Xplore camera-ready with PDF eXpress and eCF.
How do I install Infocom Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-workflow -a claude-code`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/infocom-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Infocom Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-workflow -a codex`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/infocom-workflow in your project. Codex loads it when a task matches its description.
Can I use Infocom 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 infocom-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/infocom-workflow, .gemini/skills/infocom-workflow, .github/skills/infocom-workflow and .opencode/skills/infocom-workflow in your project.
What does Infocom Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Infocom Workflow is instructions for the agent only.
Does Infocom 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 Infocom 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 Infocom Workflow use?
Infocom 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 Infocom Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Infocom Workflow?
Skills that share tags, products or a category with Infocom Workflow: Markitdown (ImCa0/just-laws, 782 stars), Gzh Design (isjiamu/gzh-design-skill, 3.9k stars), GenOffice Document CLI (genspark-ai/genoffice, 9k stars) and Harness Book Best Practice (wquguru/harness-books, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Infocom 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.