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 a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the…
MITAuto-check passed
Install Webconf Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-workflow .claude/skills/webconf-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 "webconf-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-workflow into .claude/skills/webconf-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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/The-Web-Conference-Skills/skills/webconf-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 webconf-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-workflow .agents/skills/webconf-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 "webconf-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-workflow into .agents/skills/webconf-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-workflow .cursor/skills/webconf-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 "webconf-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-workflow into .cursor/skills/webconf-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 The-Web-Conference-Skills/skills/webconf-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 webconf-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-workflow .gemini/skills/webconf-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 "webconf-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-workflow into .gemini/skills/webconf-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-workflow .github/skills/webconf-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 "webconf-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-workflow into .github/skills/webconf-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-workflow .opencode/skills/webconf-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 "webconf-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-workflow into .opencode/skills/webconf-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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
webconf-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 769 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the…
- Works in 4 steps: Short papers (+6 weeks; 4 pages… → Web4Good (+8 weeks; main proceedings) —… → Workshops / companion venues… → …
- Planning a teams calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines
- SKILL.md covers The 2026 cycle as a planning…, Backward planning from the…, The intra-edition fallback tree and Capacity planning quirks, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Webconf Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the short-paper and Web4Good fallback windows inside the same edition, venue-volatility contingencies, and rerouting after rejection.
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 a teams calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines
- The holiday-week rebuttal
- January decisions
- The short-paper and Web4Good fallback windows inside the same edition
Example prompts
- “/webconf-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Short papers (+6 weeks; 4 pages including references; main proceedings) —
- Web4Good (+8 weeks; main proceedings) — right when the work's center is
- Workshops / companion venues (per-workshop deadlines, companion
- Hold for the next edition — WWW 2027 is announced for Dublin, Ireland, so
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
Webconf Workflow loads about 1.7k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 769 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). 769 words, ~1,677 tokens.
Download SKILL.mdSave it as
.claude/skills/webconf-workflow/SKILL.md (or your agent's skills folder).- name
- webconf-workflow
- description
- Use when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the short-paper and Web4Good fallback windows inside the same edition, venue-volatility contingencies, and rerouting after rejection.
Web Conference Workflow
The Web Conference runs one research-tracks cycle per year, anchored in early autumn, with the conference the following spring or summer. The 2026 edition adds two planning lessons no other pack in this collection teaches as vividly: the same edition offered later submission windows into the same proceedings (short papers, Web4Good), and the conference itself moved by ten weeks mid-cycle (April 13-17 → June 29 - July 3, 2026), so travel and money plans need slack.
The 2026 cycle as a planning template
| Milestone | 2026 edition date | Offset from abstract |
|---|---|---|
| Abstract (research/industry) | Sep 30, 2025 | 0 |
| Full paper | Oct 7, 2025 | +1 week |
| Short papers abstract / paper | Nov 10 / Nov 17, 2025 | +6 / +7 weeks |
| Web4Good abstract / paper | Nov 23 / Nov 30, 2025 | +8 / +9 weeks |
| Rebuttal window | Nov 24 - Dec 1, 2025 | +8 weeks |
| Notification | Jan 13, 2026 | +15 weeks |
| Camera-ready | Jan 25, 2026 | +17 weeks |
| Author registration (post-postponement) | Mar 30, 2026 | +26 weeks |
| Conference | Jun 29 - Jul 3, 2026 | +39 weeks |
Every date above is a 2026 anchor for shape, not a prediction: pull the current edition's important-dates page before committing the team.
Backward planning from the abstract deadline
T-12w Claim set frozen; datasets acquired; ethics/ToS posture settled
(data-access negotiations are the long pole for web papers)
T-8w Experiment matrix running (webconf-experiments); baselines reproduced
T-6w First full draft; web-native framing test (webconf-writing-style)
T-4w Internal review by someone from the track's *other* discipline
T-2w Freeze authors + track; sweep co-author EasyChair profiles;
count per-author submissions against the cap of 7
T-1w Page-zone audit, anonymity sweep (webconf-submission)
T+0 Abstract registered -- author list now immutable
T+1w Paper in, with hours of margin (deadlines are strict, AoE)Two locks distinguish this venue's timeline: the author-list freeze at T+0 and the track choice, both irreversible a week before the paper itself is due.
The intra-edition fallback tree
A miss or a weak draft at the research deadline is not a lost year here:
- Short papers (+6 weeks; 4 pages including references; main proceedings) — right when the core idea is sound but the full evidence program isn't. Compressing an 8-page draft to 4 is a rewrite, not a trim; decide by T+2w.
- Web4Good (+8 weeks; main proceedings) — right when the work's center is societal benefit; it is a distinct scope, not a consolation lane.
- Workshops / companion venues (per-workshop deadlines, companion proceedings) — visibility and feedback without burning the idea's archival slot.
- Hold for the next edition — WWW 2027 is announced for Dublin, Ireland, so the next cycle's deadlines will land in roughly the same autumn window.
Each fallback has different proceedings placement and prestige; choose by what the paper needs (archival main-proceedings status vs. fast feedback), not by sunk cost.
Capacity planning quirks
- The rebuttal week (late November in 2026's cycle) collided with a major US holiday; name the responding author at submission time and check their November calendar.
- Notification-to-camera-ready was twelve days; pre-draft the de-anonymized
version and the artifact deposit during the December quiet period
(
webconf-camera-ready). - Budget approvals for registration + travel should start at notification, not at the registration deadline — and the 2026 postponement shows dates can move after booking, so prefer refundable fares and watch official channels, not rumor.
Show full SKILL.md (322 more words)Show less
Portfolio planning under the cap
Groups submitting several papers per cycle hit constraints individuals never see. The 7-per-author cap binds on senior authors first: an advisor on nine drafts must drop off two before abstracts are registered, which is an authorship-integrity decision, not a bookkeeping one — being removed to dodge the cap while continuing to contribute violates the spirit of both the cap and the authorship policy. Rebuttal week is the second portfolio bottleneck: five papers times a one-week window means five simultaneous response drafts; assign one owning author per paper in September and let the PI review rather than write. Track collisions are the third: two similar papers from one group in one track invite the panel to compare them against each other — differentiate their framings deliberately or route one to a different track or venue.
After rejection
Route by the review packet's agreement structure (webconf-review-process): a
converged evidence objection means running the missing experiments and returning
next edition; a fit objection means the sibling circuit — WSDM (autumn deadline,
web mining methods), CIKM (spring, broad IR/KM), SIGIR (winter, retrieval), KDD
(winter/summer dual-cycle, mining) — inherits the paper with modest reframing.
Never resubmit unchanged into an overlapping reviewer pool; panels remember.
Cycle-shape volatility to plan around
Three shape changes the series has actually made, which a multi-year plan should treat as live possibilities rather than history:
- Conference month moves. Recent editions ran in late April/early May (Singapore 2024, Sydney 2025) while 2026 landed in late June/early July after its postponement — the submission window has stayed autumn-anchored, so plan research capacity around September-October and treat the conference date as the flexible end.
- Platform switches (OpenReview 2024-25 → EasyChair research tracks 2026) change co-author onboarding costs; budget a week for profile wrangling whenever a new edition's call names a different system.
- Special-track churn (Web4Good appeared for 2026) means the fallback tree must be rebuilt from the current edition's calls page each year, not reused.
Output format
[Cycle position] T<±n>w relative to current-edition abstract deadline
[Locks ahead] author freeze / track choice / cap count -- dates
[Fallback decision] research full / short / Web4Good / workshop / next edition
[Capacity flags] rebuttal-week owner, camera-ready pre-work, travel slack
[Next actions] <this week's moves, with owning author>© 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 The-Web-Conference-Skills/skills/webconf-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Webconf 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 |
|---|---|---|---|---|---|---|
| Webconf 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.
Ccfddl Conference Update
ccfddl/ccf-deadlines
Add the latest conference edition or newly announced deadline information to ccfddl/ccf-deadlines.
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 Webconf Workflow
What does Webconf Workflow do?
A skill your agent uses when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the…. Webconf Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a team's calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines, the holiday-week rebuttal, January decisions, the short-paper and Web4Good fallback windows inside the same edition, venue-volatility contingencies, and rerouting after rejection.
When should I use Webconf Workflow?
Webconf Workflow fits situations like: planning a teams calendar around the Web Conference (WWW) annual cycle — the autumn abstract/paper deadlines; the holiday-week rebuttal; january decisions; the short-paper and Web4Good fallback windows inside the same edition.
How do I install Webconf Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-workflow -a claude-code`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/webconf-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Webconf Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-workflow -a codex`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/webconf-workflow in your project. Codex loads it when a task matches its description.
Can I use Webconf 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 webconf-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/webconf-workflow, .gemini/skills/webconf-workflow, .github/skills/webconf-workflow and .opencode/skills/webconf-workflow in your project.
What does Webconf Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Webconf Workflow is instructions for the agent only.
Does Webconf 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 Webconf 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 Webconf Workflow use?
Webconf 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 Webconf Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Webconf Workflow?
Skills that share tags, products or a category with Webconf 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 Webconf Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.