Inference Autopilot
rednote-machine-learning/Inference-autopilot
Analyze, benchmark, diagnose, and optimize large-model inference deployments from hardware inventory, model details, workload traces, and latency or throughput SLOs.
A skill your agent uses when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal…
Install Kdd Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-workflow --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-workflow .claude/skills/kdd-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-workflow into .claude/skills/kdd-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-workflow --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-workflow .agents/skills/kdd-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-workflow into .agents/skills/kdd-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-workflow --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-workflow .cursor/skills/kdd-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-workflow into .cursor/skills/kdd-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills kdd-workflow --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-workflow .gemini/skills/kdd-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-workflow into .gemini/skills/kdd-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/kdd-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-workflow into .github/skills/kdd-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/kdd-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/KDD-Skills/skills/kdd-workflow into .opencode/skills/kdd-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kdd-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 746 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal…
- Planning a KDD project calendar across the venues two submission cycles per year
- SKILL.md covers Cycle-choice decision, Pipeline milestones (per cycle), The Resubmit loop as a plan and Failure modes on this calendar, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Including cycle choice
What it does
Kdd Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.
Its SKILL.md is about 1.7k 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 DevOps & Cloud, covering Site reliability engineering. 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
- Planning a KDD project calendar across the venues two submission cycles per year
- Including cycle choice
- Abstract-then-paper deadline pairs a week apart
- Rebuttal capacity planning
Example prompts
- “/kdd-workflow”
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 yaml).
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 Workflow loads about 1.7k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 746 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). 746 words, ~1,699 tokens.
Download SKILL.mdSave it as
.claude/skills/kdd-workflow/SKILL.md (or your agent's skills folder).- name
- kdd-workflow
- description
- Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.
KDD Workflow
Use this as the project-management layer. KDD's calendar is structurally different from single-deadline ML venues: two cycles per year, each with an abstract deadline about one week before the paper deadline (2026 anchors: Jul 24/Jul 31, 2025 and Feb 1/Feb 8, 2026, AoE), a rebuttal window inside review, and a Resubmit outcome that connects the cycles into a pipeline. Plan the pipeline, not a single date.
KDD is an ACM conference, not a journal: no standing editor, leadership rotates per edition (the KDD 2026 committee roster lives on the conference site; individual names 待核实 before citing), and the cost surface is registration plus, under ACM Open, a possible APC for authors at non-participating institutions — with a temporary 65% ACM subsidy announced for 2026. Verify all money facts against current pages.
Cycle-choice decision
| Situation | Choose | Reasoning |
|---|---|---|
| Evidence complete, paper drafted | Nearest cycle | Waiting adds staleness risk in fast subfields |
| Core result solid, ablations/scale runs missing | Next cycle | Rebuttal cannot carry links, so missing evidence has no delivery channel later |
| Prior cycle returned Resubmit | Next cycle, always declared | Addressed resubmissions carry better odds per the CFP; the forum id travels with you |
| ADS paper, launch too recent to measure | Cycle after the measurement window closes | The desk-check needs quantified post-launch numbers, not projections |
Pipeline milestones (per cycle)
- T-10 weeks — evidence lock plan: four-axis experiment plan agreed
(
kdd-experiments); ADS measurement windows already running. - T-6 weeks — mechanism freeze: no new components after this point; ablation matrix enumerable.
- T-4 weeks — draft in acmart: writing directly in the two-column format; scale runs queued (cluster time is the real deadline for large-data papers).
- T-2 weeks — artifact freeze: anonymized repository built fresh, cited in the
PDF, smoke-tested on a clean machine (
kdd-artifact-evaluation). - T-1 week — abstract deadline: title/abstract/authors/track registered; all co-author OpenReview profiles complete (five-year history, DBLP, ORCID — chasing this is a named person's job).
- T-0 — paper deadline: submission audit (
kdd-submission); ADS deployment quantification pointed to; resubmission declarations attached. - Review window — rebuttal capacity: reserve author-days in advance; per-review
responses under a link ban are writing-intensive (
kdd-author-response). - Decision — branch: Accept → e-rights + TAPS + APC status check
(
kdd-camera-ready); Resubmit → change-summary plan against the review contract; Reject → routing decision (kdd-topic-selection).
The Resubmit loop as a plan
# kdd-pipeline.yaml - one paper, tracked across cycles
paper: streamhive
track: research
cycle_history:
- cycle: 2026-C1
outcome: resubmit
contract: # concerns named in reviews = next cycle's spec
- temporal-split rebuild (R2)
- decay-mechanism ablation (R1)
- scale claim beyond 10M edges (R3)
- cycle: 2026-C2
changes_summary_page: drafted # mandatory first page of the PDF
prior_forum_id: declared
new_evidence: [table5_ablation, 2.1B_run, rebuilt_splits]
owners:
profiles_gate: <name> # co-author OpenReview completeness
artifact_freeze: <name>
rebuttal_window: <name, name>The discipline: the review contract is written down the day reviews arrive, and every contract item maps to a change-summary line before the next cycle's abstract deadline.
Show full SKILL.md (354 more words)Show less
Failure modes on this calendar
- Treating the abstract deadline as soft: at KDD it gates the submission and the track choice; a placeholder abstract in the wrong track is a real incident.
- Discovering an incomplete co-author profile on paper-deadline day — the one blocker that requires someone else's login to fix.
- Queuing the largest-scale run after the draft: at KDD the scale run is the contribution evidence, not a garnish, and clusters have queues.
- Winning a Resubmit and then re-litigating the reviews instead of executing the contract — the returning AC checks the named concerns first.
- Forgetting that notification and camera-ready dates for the current cycle were never verified (待核实) and promising co-authors a calendar the venue never published.
Vignette: one paper, three cycles, two tracks
A team's trajectory that the pipeline model handles cleanly: Cycle 1, the sampling
method goes to Research and draws a Resubmit with three named concerns. Between
cycles, the method also ships inside the company's ranking system. Cycle 2 now offers
a fork: return the Research paper with the contract executed, or wait one more cycle
and submit the deployed system to ADS with a real measurement window. The pipeline
answer: do both, sequenced — Research resubmission in Cycle 2 (the contract items
are done and Resubmit standing decays with staleness), ADS submission the following
cycle once the post-launch window closes. Two papers, two tracks, no dual-submission
conflict, each riding the evidence it actually has (kdd-topic-selection governs the
fork; kdd-related-work governs the overlap declarations between them).
Capacity planning numbers
Planning heuristics — replace with your team's observed values after one cycle:
- Rebuttal window: one author-day per review for text-only responses; double it if any new run is permitted and needed.
- Anonymized artifact build from a mature internal repo: 2-3 days including the clean-machine smoke test, dominated by de-identification review.
- ADS measurement window: whatever the CFP demands is a floor; credible pre/post or A/B windows are typically weeks, which is why the ADS decision happens a quarter early, not a deadline-month early.
- Profile-gate sweep across N co-authors: an hour of work, a week of waiting on other people — start it at abstract-minus-two-weeks.
Output format
[Pipeline stage] planning / evidence / drafting / submitted-C<k> / rebuttal / decision-branch
[Cycle target] <cycle + abstract/paper dates from current CFP, AoE>
[Critical path] <three tasks that decide readiness>
[Resubmit contract] <items + owners, or N-A>
[Money checks] ACM Open status / APC exposure / registration (待核实 items flagged)
[Owner map] profiles: <who> / artifact: <who> / rebuttal: <who>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Kdd Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Inference Autopilotrednote-machine-learning/Inference-autopilot | 144 | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Executing Distributed System Testsshenli/distributed-system-testing | 231 | — | ~5.1k | Automated safety check: Notes | MIT | |
| Alerting Irmgrafana/skills | 281 | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Slo Implementationwshobson/agents | 40k | 11 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Agentforce D360 Analyzeforcedotcom/sf-skills | 1.1k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Executing Distributed System Tests
shenli/distributed-system-testing
A skill your agent uses when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability /…
- Official
Alerting Irm
grafana/skills
Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack/PagerDuty/email/webhook)…
Slo Implementation
wshobson/agents
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
- Official
Promql
grafana/skills
Write, validate, and optimize PromQL for Prometheus / Grafana Mimir / Grafana Cloud Metrics.
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 Workflow
What does Kdd Workflow do?
A skill your agent uses when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal…. Kdd Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.
When should I use Kdd Workflow?
Kdd Workflow fits situations like: planning a KDD project calendar across the venues two submission cycles per year; including cycle choice; abstract-then-paper deadline pairs a week apart; rebuttal capacity planning.
How do I install Kdd Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-workflow -a claude-code`. Or copy the skill folder (KDD-Skills/skills/kdd-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/kdd-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Kdd Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-workflow -a codex`. Or copy the skill folder (KDD-Skills/skills/kdd-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/kdd-workflow in your project. Codex loads it when a task matches its description.
Can I use Kdd Workflow 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-workflow -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-workflow, .gemini/skills/kdd-workflow, .github/skills/kdd-workflow and .opencode/skills/kdd-workflow in your project.
What does Kdd Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Kdd Workflow is instructions for the agent only.
Does Kdd Workflow 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 Workflow 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 Workflow use?
Kdd Workflow 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 Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Workflow?
Skills that share tags, products or a category with Kdd Workflow: Inference Autopilot (rednote-machine-learning/Inference-autopilot, 144 stars), Executing Distributed System Tests (shenli/distributed-system-testing, 231 stars), Alerting Irm (grafana/skills, 281 stars) and Slo Implementation (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kdd Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.