Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
A skill your agent uses when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column…
Install Infocom Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-submission --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-submission .claude/skills/infocom-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-submission into .claude/skills/infocom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-submission --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-submission .agents/skills/infocom-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-submission into .agents/skills/infocom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-submission --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-submission .cursor/skills/infocom-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-submission into .cursor/skills/infocom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-submission --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-submission .gemini/skills/infocom-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-submission into .gemini/skills/infocom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/infocom-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-submission into .github/skills/infocom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-submission", 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-submission -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-submission --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-submission .opencode/skills/infocom-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-submission into .opencode/skills/infocom-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 723 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column…
- Works in 6 steps: Freeze the body early; the system model… → Enter title/abstract/co-authors into… → Compile with the exact IEEEtran… → …
- Auditing an IEEE INFOCOM main-conference submission for EDAS readiness
- SKILL.md covers The two-step deadline…, Format and page budget (hard), Double-blind sweep and The five-paper cap, plus 4 more sections
- Calls pdftotext
What it does
Infocom Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
Its SKILL.md is about 1.6k 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
- Auditing an IEEE INFOCOM main-conference submission for EDAS readiness
- Covering the two-step abstract-then-paper registration
- The IEEEtran two-column 10-page/9-page-of-text budget
- Double-blind anonymization of the PDF and metadata
Example prompts
- “/infocom-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the body early; the system model and results cannot churn in the last days.
- Enter title/abstract/co-authors into EDAS before the abstract cutoff; confirm the ≤200-word
- Compile with the exact IEEEtran preamble; measure the 9-page text boundary with references
- Run the mechanical double-blind checks on the final PDF, including pdfinfo metadata.
- Fill every EDAS field — topics that match your evidence so the automated assignment routes you
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 723 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). 723 words, ~1,572 tokens.
Download SKILL.mdSave it as
.claude/skills/infocom-submission/SKILL.md (or your agent's skills folder).- name
- infocom-submission
- description
- Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
INFOCOM Submission
Run this audit before the EDAS deadline. INFOCOM is a large IEEE ComSoc flagship — on the
order of ~1,400-1,500 submissions per year — so mechanical non-compliance is caught at scale and
papers over the length limit are simply not reviewed. Every number below was read from the
INFOCOM 2026/2027 Call for Papers and Submission Guidelines on 2026-07-09 via search renderings of
the ieee-infocom.org URLs (see resources/official-source-map.md); treat them as a one-cycle
snapshot and reopen the live call first.
The two-step deadline (abstract, then paper)
INFOCOM separates the abstract/metadata registration from the full-paper upload, both on EDAS and both AoE:
- Abstract/metadata (INFOCOM 2026: 24 July 2025) locks title, all co-authors, and a ≤200-word abstract into EDAS. This metadata drives the automated review assignment, so it must reflect the real paper.
- Full paper (INFOCOM 2026: 31 July 2025; INFOCOM 2027: 31 July 2026) uploads the anonymized PDF. Miss the abstract step and EDAS will not accept the PDF later.
Register with the real title and abstract, not a placeholder — the assignment system matches your manuscript and abstract to TPC members' publications, and a vague abstract worsens your reviewer fit before a human ever reads the paper.
Format and page budget (hard)
- IEEEtran.cls version 1.8, unmodified, two-column:
\documentclass[10pt, conference, letterpaper]{IEEEtran}, 10-point Times, default margins and line spacing. This is the IEEE path, not ACM/USENIX — do not carry anacmartsingle-column habit over from a sibling venue. - Page budget: 10 pages maximum. The main text — including figures, tables, appendices, and everything other than references — must be no more than 9 pages; only references may use the 10th page. There is no separate supplementary or appendix channel at review time.
- Papers that violate the length limit are not reviewed — this is a mechanical, non-negotiable screen, not a soft preference. Recover space by editing, never by shrinking the font or margins.
Double-blind sweep
INFOCOM runs double-blind review: author identities are removed from the PDF title page, body, and PDF metadata. Because networking papers lean on testbeds, traces, and released tools, the leak surface is wide:
# Mechanical pass on the submission PDF before EDAS upload
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # scrub metadata identity
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|our (prior|previous) (work|system)|acknowledg|this work was supported' | head
grep -nEi '\\thanks|\\author\{[^}]*[A-Za-z]' paper.tex | head # stray author/thanks blocksThe networking-specific leaks: a self-citation phrased as "our previous system," a testbed or university cluster name, a released-tool GitHub URL, a funding/acknowledgement line left in, and identifying dataset names. Cite your own prior work in the third person and defer acknowledgements and grant numbers to the camera-ready.
The five-paper cap
An individual may be listed as author or co-author on at most five papers submitted to a given INFOCOM; if exceeded, only the first five received before the deadline are reviewed. On a large group's submission sprint, confirm nobody crosses the cap before the abstract deadline — EDAS enforces it on receipt order, and a late sixth paper is silently dropped.
Show full SKILL.md (273 more words)Show less
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Text (incl. appendices) over 9 pages, or total over 10 | Not-reviewed-grade | Cut or compress into the budget; references do not absorb body text |
Template altered (margins, shrunk font, wrong IEEEtran options) | Named non-compliance | Recompile clean with the required preamble; recover space editorially |
| Author identity in PDF, metadata, or a "our system" self-citation | Double-blind violation | Re-anonymize; scrub PDF metadata; third-person self-citations |
| Abstract/metadata not registered by the earlier date | No submission slot exists | Nothing fixes this post-AoE — calendar it now |
| A coauthor already on five submissions | Sixth paper dropped | Rebalance authorship before the abstract deadline |
| Same work under review elsewhere | Dual-submission exposure | Withdraw one venue; verify the current concurrent-submission wording |
Final-week order of operations
- Freeze the body early; the system model and results cannot churn in the last days.
- Enter title/abstract/co-authors into EDAS before the abstract cutoff; confirm the ≤200-word abstract matches the paper.
- Compile with the exact IEEEtran preamble; measure the 9-page text boundary with references excluded, not the 10-page total.
- Run the mechanical double-blind checks on the final PDF, including
pdfinfometadata. - Fill every EDAS field — topics that match your evidence so the automated assignment routes you to the right TPC members, and every coauthor's affiliation — a day early.
- Re-download the uploaded PDF and read it cold to confirm it is the file you meant.
Reverify each cycle
- The exact abstract and full-paper dates and their AoE/ET cutoffs.
- The page-budget wording (the 9-of-10 text/references split) and which IEEEtran revision is required.
- The per-author paper cap (5 for 2026), dual-submission wording, and any AI-disclosure rule — all cycle-volatile.
Output format
[INFOCOM submission status] ready / blocked / needs work
[Registration] title/abstract/co-authors in EDAS by the abstract deadline? yes/no
[Format] IEEEtran preamble correct? text pages (excl. refs) / total pages
[Anonymity] clean / leaks: <where, incl. PDF metadata and self-citations>
[Author cap] any coauthor at 5 submissions already? yes/no
[Fix queue] <ordered, with owners and dates before the AoE cutoff>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Infocom Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9.2k | — | ~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 | 316 | 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 Submission
What does Infocom Submission do?
A skill your agent uses when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column…. Infocom Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
When should I use Infocom Submission?
Infocom Submission fits situations like: auditing an IEEE INFOCOM main-conference submission for EDAS readiness; covering the two-step abstract-then-paper registration; the IEEEtran two-column 10-page/9-page-of-text budget; double-blind anonymization of the PDF and metadata.
How do I install Infocom Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-submission -a claude-code`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/infocom-submission in your project. Claude Code loads it when a task matches its description.
How do I install Infocom Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-submission -a codex`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/infocom-submission in your project. Codex loads it when a task matches its description.
Can I use Infocom Submission 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-submission -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-submission, .gemini/skills/infocom-submission, .github/skills/infocom-submission and .opencode/skills/infocom-submission in your project.
What does Infocom Submission need to run?
Going by SKILL.md and its folder, Infocom Submission needs the command-line tools its instructions call (pdftotext).
Does Infocom Submission 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 Submission 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 Submission use?
Infocom Submission 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 Submission use?
About 1.6k tokens (SKILL.md is roughly 6.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 Submission?
Skills that share tags, products or a category with Infocom Submission: Markitdown (ImCa0/just-laws, 781 stars), Gzh Design (isjiamu/gzh-design-skill, 4k stars), GenOffice Document CLI (genspark-ai/genoffice, 9.2k 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 Submission?
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.