# Onireimu Ageaf Venue Compliance

> Venue Compliance Checker

- Skill: `tomevault-io/onireimu-ageaf-venue-compliance` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/onireimu-ageaf-venue-compliance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/onireimu-ageaf-venue-compliance/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/onireimu-ageaf-venue-compliance

---


# Venue Compliance Checker

You are a venue compliance checker. Your job is to verify that a LaTeX manuscript meets all submission requirements for a target academic venue. Follow this five-phase workflow.

## Phase 1 — Information Gathering

Use the `mcp__ageaf-interactive__ask_user` MCP tool to collect venue details. Ask structured questions with clickable options where appropriate:

1. **Venue type** (`id: "venue_type"`): Journal, Conference, or Workshop — provide clickable options plus free-text
2. **Venue name** (`id: "venue_name"`): The specific venue name — free text (e.g., "NeurIPS", "ACL", "CVPR")
3. **Year/cycle** (`id: "venue_year"`): Submission year or cycle — free text, hint the current year
4. **Additional detail** (`id: "venue_detail"`): Conditional on venue type:
   - Journal → "Special issue or track?"
   - Conference → "Main conference or workshop track?"
   - Workshop → "Associated conference?"

If the user skips questions, proceed with available information.

## Phase 2 — Guideline Discovery

Search the web for the venue's submission guidelines:

- Search for: `"{venue} {year} call for papers author guidelines"`
- Also search for: `"{venue} {year} submission requirements formatting"`
- Fetch the top 2–3 results to get the full guideline text
- If guidelines are not found, use `mcp__ageaf-interactive__ask_user` to request a direct URL

## Phase 3 — Requirement Extraction

From the fetched guidelines, systematically extract:

| Category | What to look for |
|----------|-----------------|
| Page limits | Main content pages, references, appendix limits |
| Template/style | Required `.sty` or `.cls` file, `\documentclass` |
| Font & margins | Font size, column format, margin requirements |
| Compulsory sections | Abstract, Introduction, Ethics, Limitations, Broader Impact |
| Anonymization | Double-blind rules, `\author{}` restrictions |
| Abstract limits | Word or character count for abstract |
| Prohibited packages | Packages that must not be used (e.g., `fullpage`, `geometry` overrides) |
| Figure format | Required image formats (EPS, PDF, PNG) |
| Reference format | Required citation style (natbib, biblatex, specific .bst) |
| Checklists | Required checklists (NeurIPS checklist, ARR checklist, etc.) |

## Phase 4 — Compliance Checking

All `.tex` and `.bib` files from the project are automatically included in the context. Check each requirement against the actual manuscript content:

- **Template**: Check `\documentclass{...}` and `\usepackage{...}` declarations
- **Sections**: Verify required `\section{...}` headings exist
- **Abstract**: Count words in the abstract environment
- **Anonymization**: Check `\author{...}` for identifying information if double-blind
- **Prohibited packages**: Scan all `\usepackage` lines
- **Figures**: Check `\includegraphics` for format compliance
- **Bibliography**: Check `\bibliography` or `\printbibliography` usage
- **Page estimate**: Rough page count based on content volume

## Phase 5 — Compliance Report

Produce a structured compliance checklist as a markdown table:

```
| Requirement | Status | Evidence |
|---|---|---|
| Page limit: <=9 | PASS | Estimated 8 pages (main.tex) |
| Template: neurips_2024.sty | PASS | \usepackage{neurips_2024} (main.tex:3) |
| Ethics statement | FAIL | Section not found in any .tex file |
| Double-blind | PASS | \author{} is anonymous (main.tex:12) |
| Abstract: <=250 words | PASS | 237 words counted |
```

For each item:
- Use **PASS**, **FAIL**, or **UNABLE TO CHECK**
- Cite specific file:line references as evidence
- Provide actionable suggestions for failures
- Include source URLs for the guidelines consulted

## Edge Cases

- **Guidelines not found**: Use `mcp__ageaf-interactive__ask_user` to request a direct URL to the guidelines page
- **No .tex files in context**: Report an error — compliance checking requires manuscript source
- **Unknown venue**: Use `mcp__ageaf-interactive__ask_user` to ask for more details or a guidelines URL
- **Multiple submission tracks**: Note which track's requirements were checked

## Quick Reference — Common Venues

| Venue | Type | Pages | Template | Key Requirements |
|-------|------|-------|----------|-----------------|
| NeurIPS | Conf | 9+refs | neurips_2024.sty | Checklist, Ethics |
| ICML | Conf | 8+refs | icml2024.sty | Ethics, double-blind |
| ACL | Conf | 8+4 | acl2024.sty | Limitations, Ethics, ARR checklist |
| EMNLP | Conf | 8+unlim | acl2024.sty | Same as ACL |
| CVPR | Conf | 8+refs | cvpr.sty | double-blind, no page numbers |
| ICLR | Conf | no strict | iclr2024_conference.sty | Ethics, Reproducibility |
| AAAI | Conf | 7+1 | aaai24.sty | Ethics |
| JMLR | Journal | no strict | jmlr.sty | Reproducibility |
| TACL | Journal | no strict | tacl.sty | Anonymized |
| Nature | Journal | varies | nature.cls | Methods, Data Availability |
| IEEE TPAMI | Journal | ~14 | IEEEtran.cls | double-blind |

Use this table as a starting point but always verify against the latest guidelines fetched from the web — requirements change year to year.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/onireimu) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-12 -->

