eacl-submission
Use when auditing an EACL submission before its single ACL Rolling Review cycle deadline, covering ACL-template compliance, the 8-page long / 4-page short content caps, the mandatory Limitations section, the Responsible NLP checklist, anonymization, preprint and resubmission declarations, and the no-fallback-cycle timing trap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eacl-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# EACL Submission Run this audit before uploading to the ACL Rolling Review (ARR) cycle that feeds your target EACL edition. EACL papers are never submitted to the conference directly: they enter an ARR cycle on OpenReview, collect reviews and a meta-review, and are later *committed* to EACL, which decides main / Findings / reject. Reopen the current EACL CFP and `aclrollingreview.org/cfp` before trusting any number below. ## The one-cycle reality (EACL's defining trap) - Confirm **which single ARR cycle feeds your edition, and treat it as unrepeatable.** For EACL 2027 the organizers named the **August 3, 2026 cycle the only viable cycle** — the conference sits early in the year, so there is **no later cycle to slip into**. Unlike ACL, a missed or wasted cycle here loses the whole edition. - The ARR deadline is the hard one. **Commitment is a separate, later step** (October 11, 2026 for EACL 2027) — see `eacl-workflow`. - With no fallback, a thin-but-submittable draft is a real dilemma: submitting burns the only cycle, skipping loses the year. Decide deliberately, not by deadline reflex. ## Format gate - Long papers: up to **8 content pages**. Short papers: up to **4**. Both get un
- The one-cycle reality (EACL's defining trap)
- Format gate
- Anonymity gate
- Declarations that gate the ARR form
- Long vs short
- Final-72-hours sequence for an NLP paper
- Frequently mishandled cases
- Output format
What does the eacl-submission skill do?
Use when auditing an EACL submission before its single ACL Rolling Review cycle deadline, covering ACL-template compliance, the 8-page long / 4-page short content caps, the mandatory Limitations section, the Responsible NLP checklist, anonymization, preprint and resubmission declarations, and the no-fallback-cycle timing trap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eacl-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.