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 SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance…
MITAuto-check passed
Install Sigir Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-workflow .claude/skills/sigir-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 "sigir-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-workflow into .claude/skills/sigir-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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/SIGIR-Skills/skills/sigir-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 sigir-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-workflow .agents/skills/sigir-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 "sigir-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-workflow into .agents/skills/sigir-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 sigir-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-workflow .cursor/skills/sigir-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 "sigir-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-workflow into .cursor/skills/sigir-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 SIGIR-Skills/skills/sigir-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 sigir-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-workflow .gemini/skills/sigir-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 "sigir-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-workflow into .gemini/skills/sigir-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 sigir-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 sigir-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/SIGIR-Skills/skills/sigir-workflow .github/skills/sigir-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 "sigir-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-workflow into .github/skills/sigir-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 sigir-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 sigir-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/SIGIR-Skills/skills/sigir-workflow .opencode/skills/sigir-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 "sigir-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-workflow into .opencode/skills/sigir-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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
sigir-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 679 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 SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance…
- Planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference
- SKILL.md covers The annual shape, Backward plan from the paper…, Multi-track coordination and The fallback calendar, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Sequencing evidence freeze
What it does
Sigir Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance testing, and anonymization, coordinating multi-track decisions, and wiring the SIGIR/ECIR/CIKM/WSDM/SIGIR-AP fallback calendar into one pipeline.
Its SKILL.md is about 1.6k 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 SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference
- Sequencing evidence freeze
- Significance testing
- Coordinating multi-track decisions
Example prompts
- “/sigir-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
Sigir Workflow loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 679 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). 679 words, ~1,552 tokens.
Download SKILL.mdSave it as
.claude/skills/sigir-workflow/SKILL.md (or your agent's skills folder).- name
- sigir-workflow
- description
- Use when planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance testing, and anonymization, coordinating multi-track decisions, and wiring the SIGIR/ECIR/CIKM/WSDM/SIGIR-AP fallback calendar into one pipeline.
SIGIR Workflow
SIGIR is an annual single-cycle venue with a distinctive rhythm: recent editions put the full-paper deadline in mid-January (2025: abstract Jan 16, paper Jan 23; 2026 trackers reported Jan 15/22 — exact dates 待核实 on the current Key Dates page), notification in early spring, camera-ready in late April (Apr 29, 2026 verified for Resources/LRE), and the conference in July (2026: July 20-24, Melbourne). Secondary tracks stagger a few weeks behind the full-paper dates. Plan backward from the dates you verify, and treat every date in this file as a pattern anchor, not a promise.
SIGIR is a conference run by ACM SIGIR (the special interest group): there is no standing editor-in-chief — program leadership rotates per edition — and no journal-style APC; costs arrive as registration and travel, with ACM Open status determining any publication-fee exposure per institution (待核实).
The annual shape
| Phase (pattern) | Months (recent cycles) | Owner's job |
|---|---|---|
| Track decision + scoping | Aug-Oct | Pick full/short/resource/repro target; freeze claim |
| Evidence build | Oct-Dec | Collections, baselines, runs, ablations |
| Writing + audits | Dec-Jan | Style, related-work, submission audits |
| Abstract → paper deadlines | mid-Jan | Metadata frozen a week early; PDF last |
| Review window | Feb-Mar | Response prep if a channel opens; next-venue scouting |
| Notification → camera-ready | Mar-Apr | TAPS pipeline, artifacts public |
| Conference | Jul | Presentation, community work |
Backward plan from the paper deadline
| Weeks out | Milestone for a ranking/retrieval paper |
|---|---|
| 10+ | Claim frozen; collection lineup chosen against the claim's scope |
| 8 | Baselines reproduced at current strength, tuning protocol logged |
| 6 | Main results stable across seeds; ablation matrix running |
| 4 | Full draft in sigconf; significance script wired to run files |
| 3 | Internal mock review by an evaluation-minded reader |
| 2 | Repository mirror anonymized; PAPER_MAP written |
| 1 | Submission audit (sigir-submission); PC nominee confirmed; buffer |
| 0 | Abstract by its deadline, PDF by its deadline, both AoE |
The two-stage deadline is a real gate: the abstract registers title, authors, and track, and late abstracts close the door regardless of PDF readiness. Freeze the author list before the abstract — ACM authorship policy makes later changes painful.
Multi-track coordination
Groups often have several irons: a full paper, a short paper from a side finding, a resource from the data work. SIGIR's cross-track double-submission ban makes this a planning problem, not just an ethics one:
- Assign each contribution to exactly one track before the abstract deadline.
- Stagger risk: if the full paper is rejected, which parts return as a short paper or resource paper next cycle? Write the modular repo accordingly.
- The Resources track's own calendar (2026: abstract Feb 5, notify Apr 2, camera Apr 29) runs weeks behind full papers — a rejected-dataset-chapter salvage plan is sometimes executable in the same year. Verify each cycle.
Show full SKILL.md (244 more words)Show less
The fallback calendar
IR has a dense venue ring, so a SIGIR reject waits weeks, not a year:
Typical resubmission ring (verify each venue's current dates):
SIGIR (Jan deadline, Jul conf)
-> CIKM (~May/Jun deadline, Nov conf) broader IR+KM+DB scope
-> SIGIR-AP (~Jul deadline, Dec conf) regional; has advertised an R&R route
-> WSDM (~Aug deadline, Feb/Mar conf) web search + data mining angle
-> ECIR (~Sep/Oct deadline, Mar/Apr conf) European IR, full+repro tracks
-> back to SIGIR (Jan)
Journal exits: TOIS / TOIS-adjacent for work that outgrew 9 pages.Each hop costs a re-framing pass, not just a re-upload: CIKM wants the knowledge/ data-management angle sharpened, WSDM the web/user-data angle, ECIR welcomes reproducibility framing. Budget one week per hop for venue-fit revision.
Ownership map
Deadline collapses at SIGIR are usually ownership failures, not effort failures. Assign by name, once, in the scoping phase:
| Deliverable | Single owner's duty |
|---|---|
| Run files + significance script | One person regenerates every table end-to-end |
| Baseline tuning log | Proves symmetry claims during review |
| Anonymization sweep | Names, logs, leaderboards, metadata, repo history |
| OpenReview metadata + PC nominee | Abstract-deadline gate; nominee agreed in advance |
| Camera-ready/TAPS | Starts the week of notification, not the week of the deadline |
Shared ownership of the anonymization sweep is the classic failure: everyone assumes someone else checked the PDF metadata.
Failure modes by phase
- Claim still moving at week 6 → the collection lineup no longer matches the claim; scope-narrow now rather than during reviews.
- Baselines start in week 4 → tuning symmetry becomes unprovable; this is the most-cited fatal review at this venue.
- Anonymization at week 0 → leaderboard rows, repo history, and system names
leak under deadline pressure (see
sigir-submission). - Response window opens and nobody owns run files → coordinate-based replies become impossible; archive the exact submitted PDF + runs at upload time.
- Camera-ready collides with teaching/travel in April → TAPS proofs get rubber-stamped; schedule the proof check like a review, not a formality.
Output format
[Current phase] scoping / evidence / writing / submitted / responding / camera-ready
[Verified dates] <each from the live Key Dates page, with URL + check date>
[Backward plan] next three milestones with owners
[Track map] contribution -> track, cross-track conflicts: none / <list>
[Fallback route] <next two venues with verified deadlines>
[Risk register] <top risk from the failure-mode list>© 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 SIGIR-Skills/skills/sigir-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigir 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 |
|---|---|---|---|---|---|---|
| Sigir Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 | |
| Tabler Backward Compatibilitytabler/tabler | 42k | — | ~4k | Automated safety check: Pass | MIT | |
| Feishu Calendar Managerop7418/CodePilot | 6.5k | 1 repos | ~1.4k | Automated safety check: Pass | Custom licence |
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.
Tabler Backward Compatibility
tabler/tabler
Keeps changes to @tabler/core backward compatible so patch and minor releases never break projects, covering what counts as public API and how to alias renames.
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.
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 Sigir Workflow
What does Sigir Workflow do?
A skill your agent uses when planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance…. Sigir Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference, sequencing evidence freeze, significance testing, and anonymization, coordinating multi-track decisions, and wiring the SIGIR/ECIR/CIKM/WSDM/SIGIR-AP fallback calendar into one pipeline.
When should I use Sigir Workflow?
Sigir Workflow fits situations like: planning a SIGIR project calendar — backward-planning from the January-pattern abstract/paper deadlines to the July conference; sequencing evidence freeze; significance testing; coordinating multi-track decisions.
How do I install Sigir Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-workflow -a claude-code`. Or copy the skill folder (SIGIR-Skills/skills/sigir-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigir-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Sigir Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-workflow -a codex`. Or copy the skill folder (SIGIR-Skills/skills/sigir-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigir-workflow in your project. Codex loads it when a task matches its description.
Can I use Sigir 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 sigir-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/sigir-workflow, .gemini/skills/sigir-workflow, .github/skills/sigir-workflow and .opencode/skills/sigir-workflow in your project.
What does Sigir Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigir Workflow is instructions for the agent only.
Does Sigir 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 Sigir 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 Sigir Workflow use?
Sigir 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 Sigir Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 Sigir Workflow?
Skills that share tags, products or a category with Sigir Workflow: Google Calendar (codewhale-hq/Codewhale, 41k stars), Team Calendar (sickn33/agentic-awesome-skills, 47k stars), Gws Calendar Agenda (googleworkspace/cli, 31k stars) and Tabler Backward Compatibility (tabler/tabler, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigir 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.