venue-templates
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.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- venue-templates
- license
- MIT
- metadata
- { "tags": "journal templates, LaTeX templates, conference papers, academic formatting, posters", "version": "1.3", "category": "journal-formats", "maintainer": "Kalaris Labs" }
- description
- 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.
- compatibility
- Requires Python 3.11+ for helper scripts; LaTeX and Poppler command-line tools are optional for compilation and PDF inspection.
02 资源文件 30
- 资产文件assets/examples/cell_summary_example.md8.7 KB
- 资产文件assets/examples/medical_structured_abstract.md11.8 KB
- 资产文件assets/examples/nature_abstract_examples.md8.7 KB
- 资产文件assets/examples/neurips_introduction_example.md8.6 KB
- 资产文件assets/grants/nih_specific_aims.tex9.0 KB
- 资产文件assets/grants/nsf_proposal_template.tex13.6 KB
- 资产文件assets/journals/elsarticle-harv.bst29.3 KB
- 资产文件assets/journals/elsarticle-num-names.bst28.2 KB
- 资产文件assets/journals/elsarticle-num.bst28.8 KB
- 资产文件assets/journals/elsarticle-template-harv.tex8.3 KB
- 资产文件assets/journals/elsarticle-template-num-names.tex8.2 KB
- 资产文件assets/journals/elsarticle-template-num.tex8.2 KB
- 资产文件assets/journals/nature_article.tex6.3 KB
- 资产文件assets/journals/neurips_article.tex9.1 KB
- 资产文件assets/journals/plos_one.tex11.6 KB
- 资产文件assets/posters/beamerposter_academic.tex8.4 KB
- 参考文档references/cell_press_style.md14.4 KB
- 参考文档references/conferences_formatting.md7.6 KB
- 参考文档references/cs_conference_style.md15.8 KB
- 参考文档references/grants_requirements.md9.9 KB
- 参考文档references/journals_formatting.md9.0 KB
- 参考文档references/medical_journal_styles.md15.9 KB
- 参考文档references/ml_conference_style.md18.3 KB
- 参考文档references/nature_science_style.md13.5 KB
- 参考文档references/posters_guidelines.md17.1 KB
- 参考文档references/reviewer_expectations.md15.9 KB
- 参考文档references/venue_writing_styles.md12.7 KB
- 脚本scripts/customize_template.py6.9 KB
- 脚本scripts/query_template.py7.8 KB
- 脚本scripts/validate_format.py10.4 KB
03 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:
- Identify the exact venue, year or funding cycle, track, and article or proposal type.
- Open the official author instructions, call, solicitation, notice of funding opportunity (NOFO), or policy guide.
- Record the source URL and the date checked.
- Distinguish initial submission, revision/rebuttal, and camera-ready rules.
- 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
| Need | Reference |
|---|---|
| Journal submission and official publisher resources | references/journals_formatting.md |
| Conference rules and 2026 verified snapshots | references/conferences_formatting.md |
| Poster sizes, layout, and accessibility | references/posters_guidelines.md |
| NSF, NIH, DOE, DARPA, and foundation proposals | references/grants_requirements.md |
| Cross-venue writing comparison | references/venue_writing_styles.md |
| Nature and Science writing | references/nature_science_style.md |
| Cell Press writing | references/cell_press_style.md |
| Medical journal writing | references/medical_journal_styles.md |
| ML and computer-vision conference writing | references/ml_conference_style.md |
| ACL, EMNLP, CHI, and other CS writing | references/cs_conference_style.md |
| Review criteria and rebuttals | references/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:
- Download the template from the official source.
- Keep its class/style files unchanged.
- Add content without overriding margins, font sizes, spacing, or headers.
- 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
| File | Status |
|---|---|
assets/journals/nature_article.tex |
Generic Nature-oriented writing scaffold; not an official Nature template |
assets/journals/plos_one.tex |
PLOS ONE-oriented scaffold; compare with the current official PLOS LaTeX package |
assets/journals/neurips_article.tex |
NeurIPS 2026 wrapper; requires the official neurips_2026.sty |
assets/journals/elsarticle-template-num.tex |
Elsevier elsarticle numeric example |
assets/journals/elsarticle-template-num-names.tex |
Elsevier elsarticle numbered/name example |
assets/journals/elsarticle-template-harv.tex |
Elsevier elsarticle author-year example |
The matching Elsevier .bst files are in assets/journals/.
Grant scaffolds
| File | Status |
|---|---|
assets/grants/nsf_proposal_template.tex |
Planning scaffold for common NSF narrative components; upload components separately |
assets/grants/nih_specific_aims.tex |
Writing 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
| File | Status |
|---|---|
assets/posters/beamerposter_academic.tex |
Venue-agnostic beamerposter scaffold; set dimensions from the event's current presenter instructions |
Common Workflows
Annual conference paper
- Open
references/conferences_formatting.md. - Follow the official link for the exact year and track.
- Download the official author kit.
- Draft in the official template.
- Keep identifying information out of every submitted file when review is blind.
- 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
- Resolve the exact journal and article type.
- Determine whether initial submission is format-flexible.
- Use the journal's official template or submission format when required.
- Apply the appropriate writing-style reference.
- 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
- Read the solicitation or NOFO before general agency guidance.
- Confirm the effective policy guide and form set.
- Map every required component to its page limit and upload field.
- Use agency systems and common forms for biosketches and support disclosures.
- Use bundled
.texfiles only as drafting aids. - Have the institution's sponsored-research office review the final package.
Research poster
- Read the event's presenter instructions.
- Confirm physical dimensions, orientation, file format, and upload deadline.
- Set the poster dimensions in the scaffold.
- Use readable type, high contrast, color-independent encodings, and a logical reading order.
- 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:
- replace year-specific claims only after checking official sources;
- avoid adding links to assets that are not bundled;
- keep generic guidance separate from official requirements;
- update helper presets and examples together; and
- increment
metadata.version.
Related skills
latex-posters: Creates research posters in LaTeX with beamerposter, tikzposter, or baposter, covering page sizes (A0, A1, 36x48 inch), multi-column layout…ieee-transactions: Format and submit papers to IEEE journals (Transactions, Journals, Letters, IEEE Access) and IEEE conferences using the IEEEtran LaTeX clas…systems-paper-writing: Provides paragraph-level structural blueprints for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys.
04 同仓库更多 Skills
migrate-to-e2e
Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.
e2e
Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.
create-verification-skill
Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.
revid
Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.