agentsclimarketplace

Top cs writing

Skill zhiming33416/top-cs-paper-skills/skills/top-cs-writing

Evidence-grounded Codex skills for writing, polishing, reviewing, reviewer responses, and figures for top CS conferences.

Install
npx -y skills add zhiming33416/top-cs-paper-skills --skill top-cs-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft, restructure, or plan evidence-grounded computer-science conference papers for WWW, ICLR, ICML, or a generic venue. Use for paper outlines, titles, abstracts, introductions, related work, methods, experiments, discussions, limitations, conclusions, full manuscript arguments, Chinese research notes to English drafting, and LaTeX or Markdown section writing. Do not use for sentence-only polishing of a finished draft, reviewer-style auditing, or rebuttal writing.

SKILL.md

2.3 KB, as published. Nobody here has run it

Top CS Paper Writing

Use the skill's static/dynamic layers; do not reconstruct venue rules or section logic from memory.

Route the request

  1. Read manifest.yaml and every path under always_load.
  2. Detect venue, paper_type, section, and language; resolve artifact scope, evidence state, submission stage, citation verification, and figure handoff as runtime parameters.
  3. State the detected values and any generic fallback in one short line so the user can correct them cheaply.
  4. Load only the files mapped to the selected values. Load every selected section fragment.
  5. Open references/ only when an on_demand condition applies.
  6. If the named venue/year is unsupported, use generic and tell the user to verify the current official guide.

Execute

  • Follow static/core/workflow.md in order.
  • For a long section, load the rhetorical-moves reference and validate the topic-sentence scaffold before expanding prose.
  • For full-manuscript work, build the argument graph and audit claim wording across sections before prose.
  • Build the claim–evidence–boundary table before prose.
  • Use explicit citation, figure/table, and appendix placeholders when artifacts are missing.
  • Treat bibliographic verification and claim entailment as separate states. If a figure must be produced, return a figure brief; do not render it.
  • Structure experiment prose around supplied claims and results; do not launch, monitor, or imply completion of experiments.
  • Use placeholders for missing facts and list them under 缺失输入 / Missing inputs.
  • Default to Chinese diagnostics and English manuscript text.
  • Preserve LaTeX commands, labels, citations, equations, and comments unless changing them is necessary and explicitly reported.
  • Return a directly usable draft, not only advice.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.