conext-writing-style
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`](../../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
- The first-page arc
- Claims tied to measurements
- Limitations as argument, not boilerplate
- Page-budget discipline (acmart)
- Networking-prose specifics
- Common CoNEXT-specific failure modes
- Output format
What does the conext-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.