agentleFS
AngelCampa1AngelCampa1/decision-making-skills/.agents/skills/venue-templates/SKILL.md

venue-templates

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Use when selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.

15 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use latex-posters and scholar-evaluation.

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.
  • Hongyu-yuSkill

    latex-posters

    Create professional research posters in LaTeX using beamerposter, tikzposter, or baposter. Support for conference presentations, academic posters, and scientific communication. Includes layout design, color schemes, multi-column formats, figure integration, and poster-specific best practices for visual communication.

    Also in 3 projects that use this

  • garri333Skill

    scholar-evaluation

    Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and writing with quantitative scoring and actionable feedback.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

26 rules. 0 are common, 25 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 25

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat bundled files as scaffolds unless this skill explicitly says they are a copy of an official template.

    line 28
  2. Distinctive:

    Never infer a current style-file name by changing the year in an old filename.

    line 30
  3. Distinctive:

    Use this skill for:

    line 34
  4. Distinctive:

    Ask for or derive:

    line 48
  5. Distinctive:

    document type, such as research article, short paper, main track, R01, or R21.

    line 52
  6. Distinctive:

    Do not combine rules from similarly named venues or tracks.

    line 56
  7. Distinctive:

    Before editing, write a short note in the working document or task log:

    line 78
  8. Distinctive:

    Keep its class/style files unchanged.

    line 97
  9. Distinctive:

    Add content without overriding margins, font sizes, spacing, or headers.

    line 98
  10. Distinctive:

    Use a bundled scaffold only for drafting or when the official source explicitly permits it.

    line 99
  11. Distinctive:

    Use SciENcv and agency-provided common forms where required.

    line 141
  12. Distinctive:

    Follow the official link for the exact year and track.

    line 154
  13. Distinctive:

    Keep identifying information out of every submitted file when review is blind.

    line 157
  14. Distinctive:

    Check the paper checklist, supplement, rebuttal, and camera-ready rules separately.

    line 158
  15. Distinctive:

    Use the journal's official template or submission format when required.

    line 172
  16. Distinctive:

    Do not apply a publisher-wide template when the journal provides its own Guide for Authors.

    line 176
  17. Distinctive:

    Read the solicitation or NOFO before general agency guidance.

    line 180
  18. Distinctive:

    Use agency systems and common forms for biosketches and support disclosures.

    line 183
  19. Very specific:

    Use bundled .tex files only as drafting aids.

    line 184
  20. Distinctive:

    Read the event's presenter instructions.

    line 189
  21. Distinctive:

    Use readable type, high contrast, color-independent encodings, and a logical reading order.

    line 192
  22. Distinctive:

    Run scripts from the skill directory.

    line 197
  23. Distinctive:

    Use a verified preset:

    line 224
  24. Distinctive:

    avoid adding links to assets that are not bundled.

    line 266
  25. Distinctive:

    keep generic guidance separate from official requirements.

    line 267
  26. Distinctive:

    update helper presets and examples together.

    line 268

“Common” is measured: kept by at least 6 in 10 of the 15 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

Prepare publication and funding documents without treating stale formatting details as authoritative. This skill combines:

  • a verification-first workflow for current venue rules;
  • bundled LaTeX scaffolds for a small, explicit set of document types;
  • writing-style and reviewer-expectation guides; and
  • local helpers for discovering, copying, and inspecting templates.

Mandatory Currency Rule

Venue requirements are time-sensitive. Before giving exact page limits, deadlines, style-file names, anonymity rules, or required sections:

  1. Identify the exact venue, year or funding cycle, track, and article or proposal type.
  2. Open the official author instructions, call, solicitation, notice of funding opportunity (NOFO), or policy guide.
  3. Record the source URL and the date checked.
  4. Distinguish initial submission, revision/rebuttal, and camera-ready rules.
  5. Treat bundled files as scaffolds unless this skill explicitly says they are a copy of an official template.

Never infer a current style-file name by changing the year in an old filename. Never present a generic scaffold as an official venue template.

When to Use

Use this skill for:

  • locating official journal or conference author instructions;
  • checking page limits, required sections, anonymity, supplemental-material rules, or citation style;
  • choosing and adapting a bundled LaTeX scaffold;
  • preparing NSF, NIH, DOE, DARPA, or foundation proposal documents;
  • designing a research poster after checking event-specific dimensions;
  • adapting prose to a venue's audience and reviewer expectations; or
  • inspecting a PDF's page count and embedded fonts.

Verification-First Workflow

1. Resolve the exact target

Ask for or derive:

  • venue or funding agency;
  • year/cycle and track;
  • document type, such as research article, short paper, main track, R01, or R21;
  • submission stage; and
  • authoring format, such as LaTeX or Word.

Do not combine rules from similarly named venues or tracks.

2. Consult the right reference

NeedReference
Journal submission and official publisher resourcesreferences/journals_formatting.md
Conference rules and 2026 verified snapshotsreferences/conferences_formatting.md
Poster sizes, layout, and accessibilityreferences/posters_guidelines.md
NSF, NIH, DOE, DARPA, and foundation proposalsreferences/grants_requirements.md
Cross-venue writing comparisonreferences/venue_writing_styles.md
Nature and Science writingreferences/nature_science_style.md
Cell Press writingreferences/cell_press_style.md
Medical journal writingreferences/medical_journal_styles.md
ML and computer-vision conference writingreferences/ml_conference_style.md
ACL, EMNLP, CHI, and other CS writingreferences/cs_conference_style.md
Review criteria and rebuttalsreferences/reviewer_expectations.md

Reference files summarize rules but do not override the current official source.

3. Capture a compliance note

Before editing, write a short note in the working document or task log:

Target: ICML 2026 main track, initial submission
Official source: https://icml.cc/Conferences/2026/AuthorInstructions
Checked: 2026-07-20
Main-text limit: 8 pages
References/appendices: additional pages allowed in the same PDF
Anonymity: required
Official template: ICML 2026 style package linked by the author instructions

This makes later validation reproducible.

4. Start from the official template

For annual conferences and publisher-managed workflows:

  1. Download the template from the official source.
  2. Keep its class/style files unchanged.
  3. Add content without overriding margins, font sizes, spacing, or headers.
  4. Use a bundled scaffold only for drafting or when the official source explicitly permits it.

For grants, many components are entered or uploaded separately. Do not submit a combined bundled .tex file as if it were an agency-issued form.

5. Validate manually and mechanically

Verify at least:

  • main-text and total-file page rules;
  • font, margin, line-spacing, and paper-size rules;
  • anonymity and metadata;
  • required sections, statements, checklists, and disclosures;
  • figure/table placement and accessibility;
  • reference and supplemental-material treatment; and
  • source-package and PDF requirements.

The helper can inspect page totals and embedded fonts, but it cannot prove that margins, font sizes, excluded sections, or hidden metadata comply.

Bundled Assets

The repository intentionally bundles only the following templates. Other venues listed in references require an official external template.

Journal and conference scaffolds

FileStatus
assets/journals/nature_article.texGeneric Nature-oriented writing scaffold; not an official Nature template
assets/journals/plos_one.texPLOS ONE-oriented scaffold; compare with the current official PLOS LaTeX package
assets/journals/neurips_article.texNeurIPS 2026 wrapper; requires the official neurips_2026.sty
assets/journals/elsarticle-template-num.texElsevier elsarticle numeric example
assets/journals/elsarticle-template-num-names.texElsevier elsarticle numbered/name example
assets/journals/elsarticle-template-harv.texElsevier elsarticle author-year example

The matching Elsevier .bst files are in assets/journals/.

Grant scaffolds

FileStatus
assets/grants/nsf_proposal_template.texPlanning scaffold for common NSF narrative components; upload components separately
assets/grants/nih_specific_aims.texWriting scaffold for a one-page NIH Specific Aims attachment

Use SciENcv and agency-provided common forms where required. Do not recreate biosketch or current-support forms in LaTeX.

Poster scaffold

FileStatus
assets/posters/beamerposter_academic.texVenue-agnostic beamerposter scaffold; set dimensions from the event's current presenter instructions

Common Workflows

Annual conference paper

  1. Open references/conferences_formatting.md.
  2. Follow the official link for the exact year and track.
  3. Download the official author kit.
  4. Draft in the official template.
  5. Keep identifying information out of every submitted file when review is blind.
  6. Check the paper checklist, supplement, rebuttal, and camera-ready rules separately.

For NeurIPS 2026, the bundled wrapper can be copied after downloading the official style file:

python scripts/customize_template.py \
  --template neurips_article.tex \
  --output my_neurips_2026_paper.tex

Journal manuscript

  1. Resolve the exact journal and article type.
  2. Determine whether initial submission is format-flexible.
  3. Use the journal's official template or submission format when required.
  4. Apply the appropriate writing-style reference.
  5. Recheck final-production instructions only after acceptance or revision.

Do not apply a publisher-wide template when the journal provides its own Guide for Authors.

Grant proposal

  1. Read the solicitation or NOFO before general agency guidance.
  2. Confirm the effective policy guide and form set.
  3. Map every required component to its page limit and upload field.
  4. Use agency systems and common forms for biosketches and support disclosures.
  5. Use bundled .tex files only as drafting aids.
  6. Have the institution's sponsored-research office review the final package.

Research poster

  1. Read the event's presenter instructions.
  2. Confirm physical dimensions, orientation, file format, and upload deadline.
  3. Set the poster dimensions in the scaffold.
  4. Use readable type, high contrast, color-independent encodings, and a logical reading order.
  5. Export and inspect the PDF at final size.

Helper Scripts

Run scripts from the skill directory.

List bundled templates

python scripts/query_template.py --list-all
python scripts/query_template.py --venue NeurIPS --requirements
python scripts/query_template.py --type grants

The query helper reports only assets that exist in this skill and includes source/currency notes.

Copy and customize a scaffold

python scripts/customize_template.py \
  --template nature_article.tex \
  --title "Your Paper Title" \
  --authors "First Author, Second Author" \
  --affiliations "Institution Name" \
  --output my_paper.tex

Review every replacement and compile before adding substantial content. User-provided text may need LaTeX escaping.

Inspect a PDF

Use a verified preset:

python scripts/validate_format.py \
  --file paper.pdf \
  --venue icml-2026 \
  --content-pages 8 \
  --check page-count,fonts

Or provide an explicit limit and source:

python scripts/validate_format.py \
  --file proposal.pdf \
  --max-pages 15 \
  --content-pages 15 \
  --source-url "https://www.nsf.gov/policies/pappg" \
  --check page-count,fonts \
  --report validation.txt

--content-pages must be counted according to the official rule. The script does not infer where references or appendices begin.

Final Compliance Checklist

  • Exact venue, year/cycle, track, article type, and stage identified
  • Official source URL recorded with date checked
  • Official template or form used where required
  • Page-limit scope understood, including excluded sections
  • Required statements, checklists, and disclosures present
  • Blind-review files and PDF metadata checked for identity leaks
  • Figures and tables are legible and accessible
  • References, appendices, and supplements follow current rules
  • PDF and source package compile cleanly
  • Submission portal preview reviewed before final submission

Maintenance

This skill was reviewed on 2026-07-20. Annual conference snapshots are labeled with their year. When updating:

  1. replace year-specific claims only after checking official sources;
  2. avoid adding links to assets that are not bundled;
  3. keep generic guidance separate from official requirements;
  4. update helper presets and examples together; and
  5. increment metadata.version.

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.