Individual skill

kdd-writing-style

Use when revising a KDD paper into the venue's register, where the first page names a data regime, a mechanism, and scale evidence, efficiency adjectives trace to design decisions, and two-column sigconf pages punish sprawl. Covers Research vs ADS voice, dataset-size discipline, assertive contribution bullets, and 8-page compression.

KDD-Skills/skills/kdd-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,397
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# KDD Writing Style

Use this during revision passes. KDD prose has a recognizable register: it talks about
**data regimes** (scale, drift, sparsity, heterogeneity, label scarcity) rather than
model families, it attaches every performance adjective to a mechanism, and it treats
dataset cardinalities as part of grammar — a dataset without a size reads as
unfinished. The `resources/worked-examples/01-introduction.md` file shows a full
before/after; this skill is the rule set behind it.

## First-page contract

Within page one, a KDD reviewer expects to find, in some order:

1. The **data regime** that makes the problem hard (not "X is important").
Back to top