New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Conext Writing Style

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

A skill your agent uses when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real…

MITAuto-check passedWriting & Content

Install Conext Writing Style

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

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

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-writing-style .claude/skills/conext-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/

Facts

Skill name
conext-writing-style
GitHub stars
1.2k
Token cost
~1.4k tokens
SKILL.md length
669 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real…

  • Works in 5 steps: The networking problem, in a real… → Why the current state is inadequate —… → The contribution, as networking claims —… → …
  • Shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context
  • SKILL.md covers The first-page arc, Claims tied to measurements, Limitations as argument, not… and Page-budget discipline (acmart), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Conext Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real target platform, arguing limitations rather than reciting them, and holding the acmart page budget for long (≤16) and short (≤10) papers.

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

  • Shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context
  • Tying every claim to a measurement on the real target platform
  • Arguing limitations rather than reciting them
  • Holding the acmart page budget for long (≤1

Example prompts

  • “/conext-writing-style”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. The networking problem, in a real deployment context — a problem an operator, protocol
  2. Why the current state is inadequate — what existing systems/measurements miss, and why the
  3. The contribution, as networking claims — a mechanism, a measured phenomenon, or both, not a
  4. Evidence on the real target — a testbed run, a deployment, or a trace, each claim paired with
  5. What changes for networking + limitations posture — the payoff for practice, with the central

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

Conext Writing Style loads about 1.4k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 669 words of instructions outside code blocks.

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

Download SKILL.mdSave it as .claude/skills/conext-writing-style/SKILL.md (or your agent's skills folder).
name
conext-writing-style
description
Use when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real target platform, arguing limitations rather than reciting them, and holding the acmart page budget for long (≤16) and short (≤10) papers.

CoNEXT Writing Style

Write to the CoNEXT reader: a networking systems/measurement expert who wants the networking contribution and the evaluation platform on the first page, evidence proportional to the claim and drawn from the real target, and a limitations posture visible from the start. Because CoNEXT papers are PACMNET journal articles judged in a two-round, one-shot-revision process, the draft must read like a manuscript whose claims are already backed, not a promising sketch.

The first-page arc

Lead with the arc the worked example demonstrates (../../resources/worked-examples/01-introduction.md):

  1. The networking problem, in a real deployment context — a problem an operator, protocol designer, or systems builder recognizes, stated in the first breath.
  2. Why the current state is inadequate — what existing systems/measurements miss, and why the gap matters on real paths or hardware.
  3. The contribution, as networking claims — a mechanism, a measured phenomenon, or both, not a model or a score.
  4. Evidence on the real target — a testbed run, a deployment, or a trace, each claim paired with the measurement that backs it.
  5. What changes for networking + limitations posture — the payoff for practice, with the central threat named up front rather than deferred.

Claims tied to measurements

  • State the claim as an outcome an operator or protocol cares about ("completion time for throttled short flows drops"), not as an offline metric ("accuracy is high").
  • Pair each claim with its evidence and its platform: which testbed, which trace, which vantage points, which baseline. A claim with no matching measurement is the fastest path to a one-shot-revision change-list item.
  • Report uncertainty. Confidence intervals, multiple runs, and effect sizes read as rigor; a single bar with no variance reads as a lab artifact to a measurement reviewer.

Limitations as argument, not boilerplate

CoNEXT reviewers reward a paper that names its own central threat and bounds it. Put the limitation where the result lives, not only in a closing section:

  • If a measurement infers an outcome from a proxy signal, say so and bound it with a ground-truth subset.
  • If evaluation is on one testbed or one network, scope the generalization claim explicitly.
  • If a mechanism assumes hardware behavior, state what breaks if the assumption fails.

A limitations section that only lists generic caveats ("results may not generalize") wastes the one place you can pre-empt the reviewer's strongest objection.

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

Page-budget discipline (acmart)

  • Long papers ≤16 pages text+figures (+ unlimited references + ≤4 appendix pages); short papers ≤10 pages (+ unlimited references + ≤2 appendix pages). Verify the current numbers.
  • References are unlimited, so never sacrifice a citation for space; compress prose, figures, and redundant tables instead.
  • The appendix budget is small and for supporting, not deciding, material — nothing a reviewer needs to accept the paper should live only there (see conext-supplementary).
  • Do not alter the acmart template to reclaim space; editorial compression is the only safe lever.

Networking-prose specifics

  • Define the topology and scale early. A reader should know what network, what hardware, and what scale before the evaluation.
  • Name the baselines honestly and describe how they were tuned; an untuned strawman is a soundness flag.
  • Figures earn their space. A topology diagram, a CDF, or a time series that a reviewer can read in one glance is worth more than a paragraph; a decorative architecture box is not.
  • Anonymize as you write — refer to your own system and prior work in the third person, and do not name testbeds, operators, or repositories (double-anonymous review).

Common CoNEXT-specific failure modes

FailureWhy it hurts at CoNEXTFix
Simulation stands in for the real platformPlatform-realism is a core CoNEXT expectationAdd a testbed/deployment run, or scope the claim
Claim outruns the measurementThe two-round review catches itPair each claim with evidence, or soften the claim
Limitations deferred to one closing paragraphMisses the chance to pre-empt objectionsArgue the central threat where the result lives
Model/leaderboard framingReads as an ML paper wearing a networking titleReframe around the networking lesson (topic-selection)
Over-signposted roadmapSubstitutes structure for argumentOne-line roadmap; let the contributions carry it

Output format

text
[First-page arc] problem -> inadequacy -> contribution -> real-target evidence -> what changes + limitations
[Claim-evidence pairs] <claim -> measurement + platform + baseline>
[Limitations posture] <central threat named where the result lives? yes/no>
[Budget] pages used (body/appendix), acmart compliant? refs unlimited
[Anonymity] third-person self-reference; no testbed/operator/repo names

© 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 CoNEXT-Skills/skills/conext-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Conext 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.

Conext Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conext Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.4kAutomated safety check: PassMIT
Narrative Enablement Kitaaron-he-zhu/aaron-marketing-skills2.9k—~3.4kAutomated safety check: PassApache-2.0
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
BrandOhh-889/skyroc79513 repos~733Automated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k1 repos~2.9kAutomated safety check: PassMIT
Writing Guidelinesvercel-labs/agent-skills32k7 repos~309Automated safety check: PassNone

Similar skills

  • Narrative Enablement Kit

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "make everyone tell the same story", "write our elevator pitch ladder", or "build a spokesperson Q&A and approved boilerplate pack"; derives from the…

    2.9k GitHub stars~3.4k tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed

  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed

  • Khazix WeChat Article Writer

    KKKKhazix/khazix-skills

    Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.

    21k GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed

  • Writing Guidelines

    vercel-labs/agent-skills

    Official

    Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.

    32k GitHub starsUsed in 7 repos~309 tokens
    Writing & ContentAuto-check passed

  • Unslop AI Writing Cleanup

    theclaymethod/unslop

    Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.

    518 GitHub stars~1.7k tokensUpdated 1 mo ago
    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

Categories

Questions about Conext Writing Style

What does Conext Writing Style do?

A skill your agent uses when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real…. Conext Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real target platform, arguing limitations rather than reciting them, and holding the acmart page budget for long (≤16) and short (≤10) papers.

When should I use Conext Writing Style?

Conext Writing Style fits situations like: shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context; tying every claim to a measurement on the real target platform; arguing limitations rather than reciting them; holding the acmart page budget for long (≤1.

How do I install Conext Writing Style in Claude Code?

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

How do I install Conext Writing Style in Codex?

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

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

What does Conext Writing Style need to run?

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

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

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

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Conext Writing Style?

Skills that share tags, products or a category with Conext Writing Style: Narrative Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars) and Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conext 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.