Agent skill

Infocom Writing Style

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

Install Infocom Writing Style

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-writing-style -a claude-code

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

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-writing-style --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/INFOCOM-Skills/skills/infocom-writing-style .claude/skills/infocom-writing-style && 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 "infocom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-writing-style into .claude/skills/infocom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-writing-style", 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/INFOCOM-Skills/skills/infocom-writing-style

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 infocom-writing-style -a codex

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

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-writing-style --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/INFOCOM-Skills/skills/infocom-writing-style .agents/skills/infocom-writing-style && 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 "infocom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-writing-style into .agents/skills/infocom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-writing-style", 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 infocom-writing-style -a cursor

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

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-writing-style --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/INFOCOM-Skills/skills/infocom-writing-style .cursor/skills/infocom-writing-style && 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 "infocom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-writing-style into .cursor/skills/infocom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-writing-style", 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 INFOCOM-Skills/skills/infocom-writing-style

--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 infocom-writing-style -a gemini-cli

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

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-writing-style --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/INFOCOM-Skills/skills/infocom-writing-style .gemini/skills/infocom-writing-style && 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 "infocom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-writing-style into .gemini/skills/infocom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-writing-style", 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 infocom-writing-style

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 infocom-writing-style -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/INFOCOM-Skills/skills/infocom-writing-style .github/skills/infocom-writing-style && 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 "infocom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-writing-style into .github/skills/infocom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-writing-style", 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 infocom-writing-style -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 infocom-writing-style --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/INFOCOM-Skills/skills/infocom-writing-style .opencode/skills/infocom-writing-style && 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 "infocom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-writing-style into .opencode/skills/infocom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-writing-style", 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-writing-style
GitHub stars: 1.2k
Token cost: ~1.4k tokens
SKILL.md length: 601 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Revising an IEEE INFOCOM paper for a networking problem and system model stated up front
SKILL.md covers Revision rules, Networking-paper skeleton, Sentence-level rewrites and Defensive-writing discipline…, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Protocol design that pay off

What it does

Infocom Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.

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.

It sits in Writing & Content, covering Brand voice and tone. 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

Revising an IEEE INFOCOM paper for a networking problem and system model stated up front
Protocol design that pay off
Evaluation proportional to the claim
Defensive writing that pre-empts objections (because there is no rebuttal)

Example prompts

“/infocom-writing-style”

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 Writing Style loads about 1.4k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 601 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~91
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). 601 words, ~1,388 tokens.

Download SKILL.mdSave it as .claude/skills/infocom-writing-style/SKILL.md (or your agent's skills folder).

name: infocom-writing-style
description: Use when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.

INFOCOM Writing Style

Use this when revising the main paper. INFOCOM papers are read by a broad networking TPC that spans theory and systems, inside a nine-page IEEEtran budget and (traditionally) with no rebuttal. Two constraints follow: the paper must be legible to both an analyst and a systems reader, and it must pre-empt the reviewer's objection in the text, because you will not get to answer it later.

Revision rules

State the networking problem and the system model first. By the end of the introduction a reader should know the setting (topology, traffic, constraints), the gap, the contribution (analysis and/or design), and what improves. Do not open with a technology-trend paragraph.
Make the model do work. If you formulate an optimization or a Markov/queueing model, its assumptions must be stated plainly and its results must yield insight or an algorithm — not a formalism that the evaluation ignores. Reviewers reward a model whose theorem changes what you build or bound.
Pair every claim with proportional evidence — a proof for an analytical claim, a simulation/testbed number with the setup named, or a measurement with its methodology — not adjectives like "significantly improves."
Write defensively. Name the assumption a theory reviewer will question and justify it; name the baseline a systems reviewer will call unfair and tune it; state the regime where your result does not hold. Because there is no rebuttal, an unaddressed objection becomes a reject.
Respect the page budget as a design constraint. Nine pages of text (appendices included) is tight; a proof sketch in the body with the full proof compressed, and a focused evaluation, beat an over-scoped paper that only fits by cutting the model.
Maintain double-blind wording in self-citations (third person), tool names, testbed/cluster identifiers, acknowledgements, and funding.

Networking-paper skeleton

Section	Job it must do	Common failure
Intro	Problem, setting, gap, contribution, what improves — by the first column or two	Leads with a trend, not a networking problem
System model	Topology, traffic, constraints, assumptions, notation, stated plainly	Assumptions hidden or introduced only in the evaluation
Analysis / design	Theorems + proof sketches, or the protocol/algorithm, reproducibly	A model no result uses; a design too thin to re-implement
Evaluation	Each claim answered with proportional evidence, honest baselines	Toy topology; untuned baseline; metric that proxies the claim
Discussion / limits	The regime where the result holds; deployment caveats	No limits stated (invites the objection you cannot rebut)
Related work	Delta-first positioning against the networking literature	Citation catalog with no contrast

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

Sentence-level rewrites

Draft pattern	INFOCOM-safe rewrite
"Our scheme significantly improves throughput."	"improves median throughput by X% (95% CI ...) over `<tuned baseline>` in <topology/scale>"
"We prove our algorithm is optimal."	"We prove a (1-1/e) approximation under `<stated assumptions>`; §V bounds the gap empirically"
"We evaluate on a large simulation."	"We simulate `<N nodes>` in <ns-3/custom>, `<traffic model>`, `<M seeds>`; setup in §V-A"
"The model captures the system."	"Under assumptions A1-A3 (stated and justified in §III), the model yields Theorem 1"
"State-of-the-art performance."	Claim scoped to the topology, traffic, and regime actually tested

Defensive-writing discipline (no rebuttal)

text

[Assumption]  which modeling assumption will a theory reviewer challenge? -> justify it in §III
[Baseline]    which comparison will a systems reviewer call unfair? -> tune it, document the budget
[Scale]       does the evaluation reach a realistic size? -> if not, scope the claim and say so
[Regime]      where does the result break? -> state it before a reviewer finds it
-> each objection answered in the PDF, because there is no turn to answer it in a reply

Vignette: compressing an over-scoped analytical paper

A draft with two models, five theorems, and a sprawling evaluation: keep the one model the design uses, the two theorems that carry the insight (full proofs compressed or sketched), and the two evaluation figures that test the headline claim; move notation-heavy derivations into a tight in-budget appendix (remember it counts toward the nine pages); cut the second model to a remark. The test of a good cut: a reviewer should be able to state your assumptions, your main result, and why your baseline is fair — from the body alone.

Output format

text

[Writing diagnosis] clear / under-modeled / over-claimed / evidence-mismatched / over-scoped
[First-page fix] <new framing leading with the networking problem + system model>
[Claim audit] <claim -> proof or simulation/measurement -> proportional? yes/no>
[Defensive gaps] <assumption/baseline/scale/regime objection -> where to pre-empt it>
[Anonymity edits] <self-citations / tool / testbed names / acks to rewrite>

Files

Just SKILL.md in INFOCOM-Skills/skills/infocom-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Infocom Writing Style 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.

Infocom Writing Style compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Infocom Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.4k	Automated safety check: Pass	MIT	14 days ago
Crim Writing Stylefranklee16/academic-research-skills	223	1 repos	~975	Automated safety check: Pass	None	23 days ago
Est Writing Stylefranklee16/academic-research-skills	223	1 repos	~798	Automated safety check: Pass	None	23 days ago
Jaar Writing Stylefranklee16/academic-research-skills	223	1 repos	~760	Automated safety check: Pass	None	23 days ago
Jcf Writing Stylefranklee16/academic-research-skills	223	1 repos	~669	Automated safety check: Pass	None	23 days ago
Joc Writing Stylefranklee16/academic-research-skills	223	1 repos	~873	Automated safety check: Pass	None	23 days ago

Similar skills

Crim Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Criminology (ASC / Wiley) manuscript so it reads for an interdisciplinary criminology audience, follows the journal's APA-based style, and uses…
223 GitHub starsUsed in 1 repo~975 tokens
Writing & ContentAuto-check passed
Est Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of an Environmental Science & Technology (ES&T) manuscript so it reads for a multidisciplinary audience in ACS style and fits the…
223 GitHub starsUsed in 1 repo~798 tokens
Writing & ContentAuto-check passed
Jaar Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of a Journal of the American Academy of Religion (JAAR) article so it is clear, analytic, gender-neutral, and readable across the study…
223 GitHub starsUsed in 1 repo~760 tokens
Writing & ContentAuto-check passed
Jcf Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Corporate Finance (JCF) manuscript — the ≤250-word abstract, 1–7 keywords, author-date (Harvard) in-text citations, and the…
223 GitHub starsUsed in 1 repo~669 tokens
Writing & ContentAuto-check passed
Joc Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Journal of Communication (JoC) manuscript so it reads for the whole field, follows APA 7th edition, and fits the limits (main document <= 35…
223 GitHub starsUsed in 1 repo~873 tokens
Writing & ContentAuto-check passed
Jpe Writing Style
franklee16/academic-research-skills
A skill your agent uses when polishing the prose of a Journal of Political Economy (JPE) manuscript into its spare, analytical, economics-first register.
223 GitHub starsUsed in 1 repo~1.1k tokens
Writing & ContentAuto-check passed

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 Infocom Writing Style

What does Infocom Writing Style do?

A skill your agent uses when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim…. Infocom Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.

When should I use Infocom Writing Style?

Infocom Writing Style fits situations like: revising an IEEE INFOCOM paper for a networking problem and system model stated up front; protocol design that pay off; evaluation proportional to the claim; defensive writing that pre-empts objections (because there is no rebuttal).

How do I install Infocom Writing Style in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-writing-style -a claude-code`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/infocom-writing-style in your project. Claude Code loads it when a task matches its description.

How do I install Infocom Writing Style in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-writing-style -a codex`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/infocom-writing-style in your project. Codex loads it when a task matches its description.

Can I use Infocom Writing Style 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-writing-style -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-writing-style, .gemini/skills/infocom-writing-style, .github/skills/infocom-writing-style and .opencode/skills/infocom-writing-style in your project.

What does Infocom Writing Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Infocom Writing Style is instructions for the agent only.

Does Infocom Writing Style 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 Writing Style 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 Writing Style use?

Infocom Writing Style 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 Writing Style 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 Infocom Writing Style?

Skills that share tags, products or a category with Infocom Writing Style: Crim Writing Style (franklee16/academic-research-skills, 223 stars), Est Writing Style (franklee16/academic-research-skills, 223 stars), Jaar Writing Style (franklee16/academic-research-skills, 223 stars) and Jcf Writing Style (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Infocom Writing Style?

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 Infocom Writing Style

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

INFOCOM Writing Style

Revision rules

Networking-paper skeleton

Sentence-level rewrites

Defensive-writing discipline (no rebuttal)

Vignette: compressing an over-scoped analytical paper

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Related

Questions about Infocom Writing Style