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 ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR…
MITAuto-check passed
Install Acl Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill acl-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills acl-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/ACL-Skills/skills/acl-workflow .claude/skills/acl-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 "acl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACL-Skills/skills/acl-workflow into .claude/skills/acl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acl-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/ACL-Skills/skills/acl-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 acl-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills acl-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/ACL-Skills/skills/acl-workflow .agents/skills/acl-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 "acl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACL-Skills/skills/acl-workflow into .agents/skills/acl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acl-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 acl-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills acl-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/ACL-Skills/skills/acl-workflow .cursor/skills/acl-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 "acl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACL-Skills/skills/acl-workflow into .cursor/skills/acl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acl-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 ACL-Skills/skills/acl-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 acl-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills acl-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/ACL-Skills/skills/acl-workflow .gemini/skills/acl-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 "acl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACL-Skills/skills/acl-workflow into .gemini/skills/acl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acl-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 acl-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 acl-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/ACL-Skills/skills/acl-workflow .github/skills/acl-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 "acl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACL-Skills/skills/acl-workflow into .github/skills/acl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acl-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 acl-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 acl-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/ACL-Skills/skills/acl-workflow .opencode/skills/acl-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 "acl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACL-Skills/skills/acl-workflow into .opencode/skills/acl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acl-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
acl-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 850 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 ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR…
- Planning an ACL project calendar across ACL Rolling Review cycles
- SKILL.md covers The 2026 rhythm as a worked…, Which cycle reaches which…, Choosing a cycle and Backward plan from a cycle…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering cycle selection against conference commitment windows
What it does
Acl Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.
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 ACL project calendar across ACL Rolling Review cycles
- Covering cycle selection against conference commitment windows
- Backward planning from an ARR deadline
- The review-response-meta-review timeline
Example prompts
- “/acl-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
Acl Workflow loads about 1.7k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 850 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). 850 words, ~1,689 tokens.
Download SKILL.mdSave it as
.claude/skills/acl-workflow/SKILL.md (or your agent's skills folder).- name
- acl-workflow
- description
- Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.
ACL Workflow
Use this as the project-management layer for an ACL paper. Unlike one-deadline conferences, ACL runs on a cycle-and-commit rhythm: pick an ARR cycle, ride its ~10-week review train, then decide at the commitment window whether to send the package to the conference or loop back for another cycle.
ACL is a conference with rotating per-edition program committees, not a journal: there is no standing editor and no APC. Costs are registration-based, and Anthology publication is free and open access.
The 2026 rhythm as a worked anchor
ACL 2026 (64th edition, San Diego, July 2-7, 2026) drew from the ARR October 2025 and January 2026 cycles:
| Milestone | Date (verified for ACL 2026) |
|---|---|
| ARR January cycle submission | January 5, 2026 |
| Reviews + meta-reviews to authors | by March 9-10, 2026 |
| Commitment to ACL 2026 | March 14, 2026 |
| Acceptance notification | April 4, 2026 |
| Camera-ready | April 19, 2026 |
| Conference | July 2-7, 2026 |
Which cycle reaches which conference
The commitment table is the part authors get wrong, because it is set by ARR and not by
the conference: a cycle can only commit to the venues ARR lists against it, so "I will
aim for ACL" is a decision about which month to submit to ARR, often two or three
cycles ahead. As published on aclrollingreview.org/dates (re-read 2026-08-27):
| Venue | Final ARR submission | Commitment |
|---|---|---|
| EMNLP 2026 · AACL 2026 | May 25, 2026 | August 2, 2026 |
| EACL 2027 | August 3, 2026 | October 11, 2026 |
| NAACL 2027 · COLING 2027 | October 12, 2026 | December 20, 2026 |
| ACL 2027 (Kyoto, Aug 17-22, 2027) | January 2027 | not yet posted |
Two things follow that a reader working from the 2026 anchor above would get wrong. No 2026 cycle reaches ACL 2027 — the October 12 slot, the last one on the 2026 calendar, commits to NAACL and COLING. And the October 2026 cycle publishes only its submission date and its cycle end (December 20); every date in between is still TBA, so a plan that needs a known author-response window cannot use it yet.
Every date here is cycle-volatile, including the ones that are printed: re-read
aclrollingreview.org/dates before committing a team to any of them.
Choosing a cycle
- Work backward from the conference you want: each *ACL conference announces which cycles it accepts commitments from. The earlier eligible cycle buys a free resubmission shot at the same conference if reviews go badly.
- A cycle deadline you hit with a rushed paper is worse than the next cycle hit with a finished one — reviews persist and follow resubmissions.
- Mind the response window inside the cycle (a few days, roughly five weeks after submission): the team must be available then, not just at submission.
Backward plan from a cycle deadline
| Weeks out | Milestone for an experiments-heavy NLP paper |
|---|---|
| 8 | Claim fixed; datasets, baselines, and evaluation protocol frozen |
| 6 | Main results in; error-analysis sampling started |
| 4 | Human evaluation fielded; ablations running |
| 3 | Full draft in ACL style; internal red-team read |
| 2 | Responsible NLP checklist drafted against the real paper |
| 1 | Limitations written; anonymity sweep; supplement archive built |
| 0 | Submit early on deadline day (AoE) |
Show full SKILL.md (343 more words)Show less
The resubmission loop
cycle N reviews weak?
-> revise (new experiments, rescoped claims)
-> cycle N+1 submission WITH: link to prior submission,
change summary, point-by-point response to old weaknesses
-> commit the stronger package to the next eligible conferenceBudget one loop into any plan that matters: the modal strong ACL paper today has seen two cycles. Skipping the revision note is a desk reject; a floor meta-review score forbids quick resubmission without wholesale revision.
Post-decision branches
- Main conference: camera-ready sprint (see
acl-camera-ready), registration, presentation prep, artifact release. - Findings: same camera-ready track; decide early on the presentation option the edition offers and whether to present at an affiliated workshop.
- Reject: hold a post-mortem against the meta-review within a week while context is fresh; choose next cycle + venue deliberately, not reflexively.
Coordination rules that save cycles
- One owner for the checklist, one for anonymity, one for the supplement — the three most common last-day failures are all ownerless tasks.
- Freeze a "submitted" tag in the repo: the author response may only cite what that tag contains.
- Calendar the response window and the commitment deadline the day you submit; both are short and both are missable.
Running multiple papers through the machine
- Stagger sibling papers across cycles rather than stacking one deadline: the response windows will otherwise collide, and response quality is the highest-leverage hour-for-hour work in the pipeline.
- Track each paper as (cycle, state, target venue, fallback venue) — the fallback is a real decision because commitment windows do not wait.
- Reuse infrastructure deliberately: one anonymization script, one checklist template pre-filled with lab defaults, one supplement layout.
- Reviewer-duty obligations may attach to submissions in current cycles; budget senior-author reviewing time into the same calendar (verify the current cycle's policy — this has changed over the years).
Signals to re-plan immediately
- The dates page announces a cycle-structure change (it has happened multiple times; 10-week cycles arrived only in May 2025).
- Your target conference posts its eligible-cycle list and your intended cycle is not on it.
- Reviews arrive with a fixable core objection and the next cycle's deadline is within two weeks — a rushed loop beats a stale package only if the fix is genuinely small.
- A competing preprint lands mid-cycle: plan the response-window framing and the camera-ready citation now, not at notification.
Output format
[Stage] planning / cycle-N under review / response window / commit window / accepted / revising
[Target] <conference + eligible ARR cycles, with dates and source>
[Critical path] <three tasks gating the next deadline>
[Loop budget] <cycles remaining before target conference>
[Owner map] <checklist/anonymity/supplement/response owners>© 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 ACL-Skills/skills/acl-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Acl 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 |
|---|---|---|---|---|---|---|
| Acl 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.
Analyzing Active Directory Acl Abuse
mukul975/Anthropic-Cybersecurity-Skills
Detect dangerous ACL misconfigurations in Active Directory using ldap3 to identify GenericAll, WriteDACL, and WriteOwner abuse paths
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 Acl Workflow
What does Acl Workflow do?
A skill your agent uses when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR…. Acl Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.
When should I use Acl Workflow?
Acl Workflow fits situations like: planning an ACL project calendar across ACL Rolling Review cycles; covering cycle selection against conference commitment windows; backward planning from an ARR deadline; the review-response-meta-review timeline.
How do I install Acl Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill acl-workflow -a claude-code`. Or copy the skill folder (ACL-Skills/skills/acl-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/acl-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Acl Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill acl-workflow -a codex`. Or copy the skill folder (ACL-Skills/skills/acl-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/acl-workflow in your project. Codex loads it when a task matches its description.
Can I use Acl 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 acl-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/acl-workflow, .gemini/skills/acl-workflow, .github/skills/acl-workflow and .opencode/skills/acl-workflow in your project.
What does Acl Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Acl Workflow is instructions for the agent only.
Does Acl 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 Acl 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 Acl Workflow use?
Acl 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 Acl 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 Acl Workflow?
Skills that share tags, products or a category with Acl 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 Acl Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.