Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
A skill your agent uses 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…
Install Kdd Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-writing-style --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/KDD-Skills/skills/kdd-writing-style .claude/skills/kdd-writing-style && 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 "kdd-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-style into .claude/skills/kdd-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-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 install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-styleType 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 kdd-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-writing-style --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/KDD-Skills/skills/kdd-writing-style .agents/skills/kdd-writing-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kdd-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-style into .agents/skills/kdd-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-writing-style --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/KDD-Skills/skills/kdd-writing-style .cursor/skills/kdd-writing-style && 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 "kdd-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-style into .cursor/skills/kdd-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-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 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path KDD-Skills/skills/kdd-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-writing-style --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/KDD-Skills/skills/kdd-writing-style .gemini/skills/kdd-writing-style && 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 "kdd-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-style into .gemini/skills/kdd-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-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.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-writing-styleInstalls 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 kdd-writing-style -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/KDD-Skills/skills/kdd-writing-style .github/skills/kdd-writing-style && 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 "kdd-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-style into .github/skills/kdd-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-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.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-writing-style -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 kdd-writing-style --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/KDD-Skills/skills/kdd-writing-style .opencode/skills/kdd-writing-style && 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 "kdd-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-writing-style into .opencode/skills/kdd-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-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
kdd-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 769 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Works in 5 steps: The data regime that makes the problem… → Why existing method families fail in… → The named mechanism this paper adds (a… → …
- Revising a KDD paper into the venues register
- SKILL.md covers First-page contract, Register rules, Contribution bullets that… and ADS voice, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Kdd Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.8k 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 and Architecture decision records. 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 a KDD paper into the venues register
- Where the first page names a data regime
- Efficiency adjectives trace to design decisions
- Two-column sigconf pages punish sprawl
Example prompts
- “/kdd-writing-style”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The data regime that makes the problem hard (not "X is important").
- Why existing method families fail in that regime, each for a mechanism-level
- The named mechanism this paper adds (a primitive someone could re-implement).
- Evidence scoped with numbers: dataset scale, throughput or memory if claimed,
- For ADS: where this is deployed and the post-launch headline number.
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 (its code samples are bash).
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
Kdd Writing Style loads about 1.8k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 769 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). 769 words, ~1,769 tokens.
Download SKILL.mdSave it as
.claude/skills/kdd-writing-style/SKILL.md (or your agent's skills folder).- name
- kdd-writing-style
- description
- 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 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:
- The data regime that makes the problem hard (not "X is important").
- Why existing method families fail in that regime, each for a mechanism-level reason.
- The named mechanism this paper adds (a primitive someone could re-implement).
- Evidence scoped with numbers: dataset scale, throughput or memory if claimed, headline quality delta.
- For ADS: where this is deployed and the post-launch headline number.
If the introduction could open an ICML or a database paper unchanged, the framing is not yet KDD's.
Register rules
| Draft habit | KDD-register rewrite | Why it matters here |
|---|---|---|
| "novel framework" | Name the mechanism: "drift-weighted sketch family" | Frameworks are unreviewable; mechanisms are ablatable |
| "large-scale experiments" | "3 graphs, 10M-2.1B edges" | Scale is the venue's currency; unquantified scale reads as small |
| "efficient" | "O(1) update; 1.4M events/s on one core" | Efficiency claims must be attributable and checkable |
| "significantly outperforms" | "+3.3 AUPRC, median of 5 seeds, IQR ±0.4" | Practitioner reviewers distrust unquantified superlatives |
| "real-world data" | Name the datasets and their provenance | "Real-world" without provenance signals toy benchmarks |
| "can be applied to many domains" | One demonstrated transfer, or silence | Unpaid generality checks are a known reject pattern |
Contribution bullets that survive review
Circular bullets ("we propose X, we evaluate X") waste the most-read lines of the paper. Each bullet should assert a falsifiable fact:
Weak: - We propose StreamHive, a novel framework for stream anomaly detection.
Strong: - We show bounded-memory detection under drift reduces to online decay-rate
selection, and give a mixture-of-sketches scheme with O(1) update cost.
Weak: - Extensive experiments demonstrate the effectiveness of our approach.
Strong: - Across three streams up to 2.1B events, the scheme matches window-retrained
deep baselines on AUPRC at fixed 512MB memory; ablations attribute the gain
to the drift weighting rather than the ensemble.ADS voice
The Applied Data Science register differs deliberately from the Research register:
- Lead with the business/operational problem and the deployment context, then the technical path — reviewers of ADS papers score problem realism before novelty.
- Lessons learned are content, not filler: what failed before the shipped design, which offline metrics mispredicted online behavior, what broke at rollout. The classic KDD applied papers are remembered for exactly these sections.
- Post-launch numbers must be flagged as such and separated from offline evaluation — the track's desk-reject rule is about quantified post-launch performance, so make those numbers typographically impossible to miss.
Two-column compression tactics
The ACM sigconf format is tight, and submission is 8 content pages:
- Write display math sparingly; inline the one-off definitions and reserve display lines for objects the paper reuses.
- Every figure earns its column-width: delete any plot whose caption cannot state
what decision it supports. Wide tables go
table*(full width) early, since late layout flips cascade page breaks. - Algorithm environments are expensive; one algorithm block for the core mechanism, prose for variants, full pseudocode in the appendix.
- Kill roadmap paragraphs ("Section 2 discusses...") — in an 8-page paper the structure is visible without a tour guide.
- The camera-ready adds exactly one content page; do not defer required content to it (reviewers score the submission, and refs+appendix get capped at 3 pages later).
Show full SKILL.md (250 more words)Show less
Anonymity phrasing
- Research Track: "our production system at a large e-commerce platform" is fine; naming the company usually is not — and internal system codenames are as identifying as the company name.
- Cite your own prior work in third person, and check the referenced repository's
README carries no author trace (
kdd-artifact-evaluation).
Title and abstract mechanics
- KDD titles favor named-system-plus-claim ("
<Name>:<what it does><in what regime>") or a direct claim; question titles and pun-only titles underperform with this reviewer pool. - The abstract is bid-bait: reviewers choose papers from it, so the regime vocabulary (graph, stream, drift, recommendation, fraud, spatio-temporal) must appear honestly — the wrong vocabulary buys the wrong experts.
- One quantitative claim in the abstract, minimum: an abstract with no number is a style violation at a venue whose currency is measured evidence.
Revision pass order
A concrete sequence for turning a complete draft into a KDD submission, one pass per day in the final week:
- Regime pass: rewrite page one until the data regime leads; fix the abstract's vocabulary and number.
- Adjective audit: grep the draft for "novel", "significantly", "efficient", "large-scale", "real-world"; each occurrence either gains a mechanism/number or dies.
grep -n -iE "novel|significant|efficient|large-scale|real-world|extensive" \
sections/*.tex | wc -l # target: near zero unattached occurrences- Claim-evidence pass: every contribution bullet cross-referenced to its table, figure, or section; circular bullets rewritten as assertions.
- Compression pass: apply the two-column tactics until the body sits at 8 pages
without spacing hacks (
kdd-submissiontreats those as desk-level). - Anonymity pass: self-citations, system codenames, acknowledgements, repo traces — last, so later edits cannot reintroduce leaks.
Output format
[Register diagnosis] regime-first / model-first (needs reframe) / journal-paced
[First-page contract] items present: <1-5 checklist>
[Adjective audit] <unattached efficiency/scale adjectives found>
[Bullet quality] assertive / circular -> <rewrites>
[ADS voice] lessons-learned present / post-launch numbers flagged / N-A
[Compression cuts] <move/delete/merge list to reach 8 pages>© 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 KDD-Skills/skills/kdd-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Kdd 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Kdd Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Agent Stylepchalasani/claude-code-tools | 2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Good Docs AuditComposioHQ/composio | 30k | — | ~293 | Automated safety check: Pass | MIT | |
| Agent Styleyzhao062/agent-style | 709 | — | ~1.2k | Automated safety check: Pass | None | |
| Readability FeedbackJetBrains/youtrackdb | 439 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Feature Blogpockethost/pockethost | 1.4k | — | ~818 | Automated safety check: Pass | MIT |
Similar skills
Good Docs Audit
ComposioHQ/composio
Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations.
Agent Style
yzhao062/agent-style
Literature-backed English technical-prose writing rules. An agent skill from yzhao062/agent-style.
- Official
Readability Feedback
JetBrains/youtrackdb
Audit a finished design document for hard-to-read or hard-to-understand paragraphs, then harden the house-style rules so future design docs avoid them.
Feature Blog
pockethost/pockethost
Ship user-facing PocketHost features with a blog post instead of semver release notes.
Adk Style Guide
BrainDAO/adk-ts
ADK-TS brand voice, terminology, and writing conventions. An agent skill from BrainDAO/adk-ts.
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 Kdd Writing Style
What does Kdd Writing Style do?
A skill your agent uses 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…. Kdd Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Kdd Writing Style?
Kdd Writing Style fits situations like: revising a KDD paper into the venues register; where the first page names a data regime; efficiency adjectives trace to design decisions; two-column sigconf pages punish sprawl.
How do I install Kdd Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-writing-style -a claude-code`. Or copy the skill folder (KDD-Skills/skills/kdd-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/kdd-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Kdd Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-writing-style -a codex`. Or copy the skill folder (KDD-Skills/skills/kdd-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/kdd-writing-style in your project. Codex loads it when a task matches its description.
Can I use Kdd 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 kdd-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/kdd-writing-style, .gemini/skills/kdd-writing-style, .github/skills/kdd-writing-style and .opencode/skills/kdd-writing-style in your project.
What does Kdd Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Kdd Writing Style is instructions for the agent only.
Does Kdd 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 Kdd 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 Kdd Writing Style use?
Kdd 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 Kdd Writing Style use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Kdd Writing Style?
Skills that share tags, products or a category with Kdd Writing Style: Agent Style (pchalasani/claude-code-tools, 2k stars), Good Docs Audit (ComposioHQ/composio, 30k stars), Agent Style (yzhao062/agent-style, 709 stars) and Readability Feedback (JetBrains/youtrackdb, 439 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kdd 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.