Google Calendar
codewhale-hq/Codewhale
Reads schedules, checks free and busy time, and creates or updates Google Calendar events through the Calendar API, with care around invites and recurring series.
A skill your agent uses when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR…
MITAuto-check passed
Install Emnlp Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/EMNLP-Skills/skills/emnlp-workflow .claude/skills/emnlp-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "emnlp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflow into .claude/skills/emnlp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/EMNLP-Skills/skills/emnlp-workflow .agents/skills/emnlp-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "emnlp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflow into .agents/skills/emnlp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/EMNLP-Skills/skills/emnlp-workflow .cursor/skills/emnlp-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "emnlp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflow into .cursor/skills/emnlp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path EMNLP-Skills/skills/emnlp-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/EMNLP-Skills/skills/emnlp-workflow .gemini/skills/emnlp-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "emnlp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflow into .gemini/skills/emnlp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/EMNLP-Skills/skills/emnlp-workflow .github/skills/emnlp-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "emnlp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflow into .github/skills/emnlp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/EMNLP-Skills/skills/emnlp-workflow .opencode/skills/emnlp-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "emnlp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-workflow into .opencode/skills/emnlp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
emnlp-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 830 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR…
- Planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference
- SKILL.md covers The 2026 spine, Backward plan from the ARR…, The commitment decision — the… and Coordination structure, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Backward-planning experiments and annotation to the ARR deadline
What it does
Emnlp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR deadline, scheduling the author response window, deciding commit versus revise-and-resubmit, and mapping camera-ready and Budapest presentation logistics.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference
- Backward-planning experiments and annotation to the ARR deadline
- Scheduling the author response window
- Deciding commit versus revise-and-resubmit
Example prompts
- “/emnlp-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Emnlp Workflow loads about 1.7k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 830 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 830 words, ~1,695 tokens.
Download SKILL.mdSave it as
.claude/skills/emnlp-workflow/SKILL.md (or your agent's skills folder).- name
- emnlp-workflow
- description
- Use when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR deadline, scheduling the author response window, deciding commit versus revise-and-resubmit, and mapping camera-ready and Budapest presentation logistics.
EMNLP Workflow
Use this as the project-management skill for an EMNLP paper. The defining fact: EMNLP has no direct paper deadline of its own. The clock that matters is the ARR cycle aligned with the conference, and missing it usually means committing from an earlier cycle or waiting for the next conference. All dates below are the 2026 configuration (checked 2026-07-08); re-anchor every one against the live calendar.
The 2026 spine
| Date (2026) | Event | Owner |
|---|---|---|
| May 25 | ARR May cycle submission deadline | ARR |
| May 27 | Author registration form (EoD AoE) | ARR |
| Jul 6 | Reviews due from reviewers | ARR |
| Jul 7-13 | Author response + author-reviewer discussion | ARR |
| Jul 30 | Meta-reviews released | ARR |
| Aug 2 | Commitment deadline for EMNLP | Conference |
| Aug 20 | Acceptance notification (Main / Findings / reject) | Conference |
| Sep 20 | Camera-ready | Conference |
| Oct 24-29 | EMNLP 2026, Budapest (hybrid) | Conference |
Parallel option: the Industry Track took direct OpenReview submissions until June 16,
2026 — a genuinely different pipeline (see emnlp-topic-selection for routing).
Backward plan from the ARR deadline
NLP papers die on data and annotation lead times more often than on modeling. Working back from a late-May deadline:
- 10+ weeks out — task definition frozen; annotation guidelines drafted and piloted; if human evaluation is planned, the protocol and pay budget approved now.
- 8 weeks — datasets licensed and downloaded; contamination check on every evaluation set you intend to use with pretrained or API models.
- 6 weeks — main experimental grid running; baselines reproduced first, because a baseline you cannot reproduce invalidates the comparison you were about to run.
- 4 weeks — error analysis begun on real outputs; this is content, not garnish, and it cannot be written the night before.
- 2 weeks — full draft in the ACL template; internal read by someone outside the project hunting for unscoped claims.
- 1 week — Responsible NLP checklist answered against the actual draft; anonymization sweep; citation-resolution pass.
- Deadline week — freeze, upload, calendar the author registration form.
The commitment decision — the step other venues do not have
Between meta-review (Jul 30) and commitment (Aug 2) sits a real strategic choice with a 72-hour fuse in 2026:
- Commit when the meta-review is positive or mixed-positive: SACs read the reviews, scores, and your response, and can accept to Main or Findings.
- Revise and resubmit to a later ARR cycle when reviews identify repairable gaps — the paper returns to the same reviewers where possible, so superficial edits are visible. But a later cycle means a later conference: check which venue the next cycle feeds before choosing patience.
- Withdraw and rework when reviewers rejected the framing, not the execution; resubmission with the same reviewers cannot fix a framing they already dislike.
Draft the commit/revise decision tree before July 30. Three days is enough to execute a decision, not to have the argument.
Coordination structure
Role map for a 4-author EMNLP submission
- Evidence owner: experiment grid, seeds, significance tests, error analysis
- Data owner: licenses, contamination checks, annotation pipeline, agreement stats
- Compliance owner: template, checklist, anonymization, citation resolution
- Response owner: drafts the July response, tracks each reviewer thread
(One person may hold two roles; no role may have zero owners.)Archive the exact submitted PDF and checklist on deadline day — the July response must quote them precisely, and the camera-ready diff will be audited against them.
Show full SKILL.md (348 more words)Show less
If May 25 slips
Because ARR runs continuously, missing the aligned cycle is a detour, not a year lost — but the detour has geometry worth knowing in advance:
- A paper reviewed in an earlier cycle can typically still be committed to EMNLP by August 2 — ACL-family conferences have historically accepted commitments of papers reviewed in preceding cycles. Confirm the eligible-cycle window in the current call; if it holds, this is the rescue path for a project that is review-ready in spring.
- A paper that misses May 25 entirely waits for the next cycle, which feeds whatever conference it is aligned with — possibly not EMNLP. Check the alignment table on the ARR dates page before promising the group "we'll just catch the next one."
- The Industry Track's June 16 direct deadline is not an overflow valve for main-track papers; it reviews against deployment criteria and will bounce a mis-routed research paper.
The week-of-deadline load profile
Plan for the fact that three distinct clocks tick in the same week: the paper PDF (May 25), the author registration form (May 27), and any reciprocal-reviewing qualification data the form demands. In the May 2026 cycle the reviewer pool ran at roughly one AC per twelve submissions, and ARR expanded reciprocal assignments to cope — meaning a multi-paper group could owe several reviews landing in June, exactly when the group planned to rest. Put the reviewing obligation on the same calendar as the submission, with a named owner per obligated author.
Failure modes by phase
- Annotation started at week 6 delivers labels at week 1 with no time to measure agreement — the reviewers will ask for kappa you cannot compute.
- Skipping baseline reproduction until late converts "our method wins" into "our method wins against a baseline we misconfigured," the most common EMNLP rebuttal disaster.
- Treating the July 7-13 window as vacation: it is the only synchronous contact with reviewers in the entire pipeline.
- Forgetting that Findings acceptance may carry no presentation slot — decide before commitment whether Findings satisfies the project's goals (funding reports, degree requirements, visibility) or whether a revise-and-resubmit aims higher.
Output format
[Current phase] scoping / data / experiments / writing / submitted / response / commitment / accepted
[Next hard deadline] <date + owner (ARR vs conference) + source URL>
[Critical path] <three tasks gating the next deadline>
[Commitment posture] commit / revise-resubmit / undecided — with rationale
[Role gaps] <unowned roles from the role map>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in EMNLP-Skills/skills/emnlp-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Emnlp Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Emnlp Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Google Calendarcodewhale-hq/Codewhale | 41k | — | ~512 | Automated safety check: Pass | MIT | |
| Team Calendarsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Gws Calendar Agendagoogleworkspace/cli | 31k | 1 repos | ~389 | Automated safety check: Pass | Apache-2.0 | |
| Feishu Calendar Managerop7418/CodePilot | 6.5k | 1 repos | ~1.4k | Automated safety check: Pass | Custom licence | |
| WeCom Calendar SchedulerWecomTeam/wecom-cli | 3.2k | 1 repos | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Team Calendar
sickn33/agentic-awesome-skills
Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module.
Gws Calendar Agenda
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
Feishu Calendar Manager
op7418/CodePilot
Tool guidance for Feishu calendars: creating, listing, updating and searching events, managing attendees and replies, and checking free and busy time.
WeCom Calendar Scheduler
WecomTeam/wecom-cli
Books, views, searches, updates, cancels or checks free/busy time on WeCom (Enterprise WeChat) calendars and meeting rooms, routed away from online-meeting creation.
Dingtalk Calendar
DingTalk-Real-AI/dingtalk-workspace-cli
钉钉日历与会议室。Use when 用户说 约会议/查日程/订会议室/查闲忙/加参会人/改期/取消会议/今天的日程/本周日程/共同空闲。不做视频会议发起/邀请入会/会中控制（走 dingtalk-misc）、AI 听记（走 dingtalk-minutes）、待办任务（走 dingtalk-todo）。命令前缀：dws calendar。
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Emnlp Workflow
What does Emnlp Workflow do?
A skill your agent uses when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR…. Emnlp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference, backward-planning experiments and annotation to the ARR deadline, scheduling the author response window, deciding commit versus revise-and-resubmit, and mapping camera-ready and Budapest presentation logistics.
When should I use Emnlp Workflow?
Emnlp Workflow fits situations like: planning an EMNLP project calendar end to end — choosing the ACL Rolling Review cycle that feeds the conference; backward-planning experiments and annotation to the ARR deadline; scheduling the author response window; deciding commit versus revise-and-resubmit.
How do I install Emnlp Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a claude-code`. Or copy the skill folder (EMNLP-Skills/skills/emnlp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/emnlp-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Emnlp Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a codex`. Or copy the skill folder (EMNLP-Skills/skills/emnlp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/emnlp-workflow in your project. Codex loads it when a task matches its description.
Can I use Emnlp Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/emnlp-workflow, .gemini/skills/emnlp-workflow, .github/skills/emnlp-workflow and .opencode/skills/emnlp-workflow in your project.
What does Emnlp Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Emnlp Workflow is instructions for the agent only.
Does Emnlp Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Emnlp Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Emnlp Workflow use?
Emnlp Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Emnlp Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Emnlp Workflow?
Skills that share tags, products or a category with Emnlp Workflow: Google Calendar (codewhale-hq/Codewhale, 41k stars), Team Calendar (sickn33/agentic-awesome-skills, 47k stars), Gws Calendar Agenda (googleworkspace/cli, 31k stars) and Feishu Calendar Manager (op7418/CodePilot, 6.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Emnlp Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.