emnlp-related-work
Use when positioning an EMNLP submission inside NLP's fast-moving literature — covering ACL Anthology lineages and arXiv concurrency, citing Findings and workshop papers correctly, tracing dataset and benchmark ancestry, verifying every reference resolves under the hallucinated-citation policy, and keeping self-citation double-blind.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-related-work --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.
# EMNLP Related Work Use this to audit positioning and citation hygiene. NLP's literature moves faster than any reviewing cycle: between your ARR submission and the meta-review, the arXiv neighborhood of your paper will visibly change. EMNLP reviewers know this and calibrate — what they do not forgive is missing the lineage that existed *before* you submitted, or citing papers that do not exist. ## The lineage obligations An EMNLP related-work section owes coverage on distinct axes: | Axis | The reviewer's question | Where to check | |---|---|---| | Task lineage | Who defined and reshaped this task? | ACL Anthology back through renamings | | Dataset ancestry | What data does your benchmark descend from or contain? | Dataset papers + their own provenance sections | | Method neighbors | Which current approaches would contest your comparison table? | Last 2-3 years of ACL-family venues + arXiv | | Evaluation critique | Has this metric or protocol been critiqued? | The methodology literature this venue itself publishes | | Adjacent fields | Does IR / speech / ML own part of this idea? | Cross-community search before claiming firsts | Dataset ancestry is the EMNLP-specific trap: benchma
- The lineage obligations
- Anthology-status literacy
- Concurrency etiquette
- The hallucination gate
- Positioning prose that works here
- Prior versions of your own work
- Freshness without churn-chasing
- Two vocabularies, one section
- Output format
Every entry must resolve to a real, checkable identifier grep -Eo 'doi\.org/[^ ,}]+|aclanthology\.org/[^ ,}]+|arxiv\.org/abs/[0-9.]+' refs.bib \ Red flags: plausible title + plausible authors + no findable venue = fabrication
What does the emnlp-related-work skill do?
Use when positioning an EMNLP submission inside NLP's fast-moving literature — covering ACL Anthology lineages and arXiv concurrency, citing Findings and workshop papers correctly, tracing dataset and benchmark ancestry, verifying every reference resolves under the hallucinated-citation policy, and keeping self-citation double-blind.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-related-work --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.