agentleFS
Sign inStart free
JunMA98JunMA98/Computer-science-claude-skills/skills/venue-templates/SKILL.md

venue-templates

Skill3 starsChanged 8 months agoMITView on GitHub

Adapt computer science papers, posters, rebuttals, and submission packages to venue-specific templates and style expectations. Use when targeting ACM, IEEE, USENIX, NeurIPS, ICML, ICLR, CVPR, ICCV, ECCV, EMNLP, ACL, NAACL, AAAI, IJCAI, KDD, WWW, CHI, UIST, ICSE, FSE, ASE, SOSP, OSDI, NSDI, or similar CS venues.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use hypothesis-generation.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • garri333Skill

    hypothesis-generation

    Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to make a submission fit a target computing venue.

    line 8
  2. Distinctive:

    If the user has an official template, treat that as the source of truth.

    line 20
  3. Distinctive:

    Read only what matches the venue:

    line 24
  4. Distinctive:

    Do not default to:

    line 41
  5. Distinctive:

    Use this skill when the user needs to:

    line 52
  6. Distinctive:

    When adapting content, work at two levels:

    line 62
  7. Distinctive:

    Use local scripts when they help with deterministic checks:

    line 78
  8. Distinctive:

    When the user asks for venue adaptation without a strict format, return:

    line 87

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Venue Templates

Use this skill to make a submission fit a target computing venue. Focus on official template compliance, section emphasis, reviewer expectations, and formatting risk.

Start With Exact Submission Context

Identify:

  • venue name and year
  • track or paper type
  • anonymous vs camera-ready stage
  • page limits and appendix policy
  • whether artifact, reproducibility, ethics, or broader-impact statements are required
  • whether the user needs paper, poster, rebuttal, or supplementary material support

If the user has an official template, treat that as the source of truth. Local assets in this skill are scaffolding and examples, not a substitute for the venue's current official package.

CS-Focused Reference Order

Read only what matches the venue:

  • references/cs_conference_style.md for general CS conference expectations
  • references/ml_conference_style.md for ML-heavy venues
  • references/conferences_formatting.md for page, figure, anonymity, and bibliography checks
  • references/reviewer_expectations.md for what reviewers usually look for
  • references/venue_writing_styles.md for tone and section emphasis
  • references/posters_guidelines.md for poster adaptation

Ignore medical, grant, and nature-style references unless the user explicitly asks for them.

Local Assets Worth Reusing

Useful CS-oriented assets include:

  • assets/journals/neurips_article.tex
  • assets/examples/neurips_introduction_example.md
  • assets/posters/beamerposter_academic.tex

Do not default to:

  • assets/grants/*
  • assets/examples/medical_structured_abstract.md
  • assets/examples/cell_summary_example.md
  • assets/journals/nature_article.tex
  • assets/journals/plos_one.tex

Those remain in the folder as inherited upstream material but are outside the core CS workflow.

Common Venue Adaptation Tasks

Use this skill when the user needs to:

  • reshape an introduction for a venue's expected framing
  • compress a draft to page limits without deleting core evidence
  • adjust figures, tables, or appendices for anonymity or space
  • convert a project report into conference-paper structure
  • prepare rebuttal or response formatting
  • turn a paper into a poster or short talk handout

Output Structure

When adapting content, work at two levels:

Structural fit

  • required sections present
  • contribution framing matches venue norms
  • evidence appears in the sections reviewers will scrutinize most
  • optional content moved to appendix or supplement when needed

Formatting fit

  • template file and bibliography style match
  • anonymity rules are respected
  • figure sizing, float behavior, and captions are compliant
  • page budget is spent on evidence, not throat-clearing

Local Scripts

Use local scripts when they help with deterministic checks:

  • scripts/query_template.py
  • scripts/validate_format.py
  • scripts/customize_template.py

Validate the draft after significant formatting edits rather than assuming compliance.

Default Deliverables

When the user asks for venue adaptation without a strict format, return:

  1. the inferred venue requirements
  2. a template or asset recommendation
  3. section-level revision advice
  4. formatting risks and compliance checks
  5. any open items that require the official venue package

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free