Homelab Network Readiness
affaan-m/ECC
Readiness checklist for homelab VLAN segmentation, local DNS filtering (Pi-hole, AdGuard Home), and WireGuard-style remote access.
A skill your agent uses when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit…
MITAuto-check passed
Install Sigmod Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-submission --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/SIGMOD-Skills/skills/sigmod-submission .claude/skills/sigmod-submission && 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 "sigmod-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-submission into .claude/skills/sigmod-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-submission", 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/SIGMOD-Skills/skills/sigmod-submissionType 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 sigmod-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-submission --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/SIGMOD-Skills/skills/sigmod-submission .agents/skills/sigmod-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sigmod-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-submission into .agents/skills/sigmod-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-submission", 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 sigmod-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-submission --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/SIGMOD-Skills/skills/sigmod-submission .cursor/skills/sigmod-submission && 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 "sigmod-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-submission into .cursor/skills/sigmod-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-submission", 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 SIGMOD-Skills/skills/sigmod-submission--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 sigmod-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-submission --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/SIGMOD-Skills/skills/sigmod-submission .gemini/skills/sigmod-submission && 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 "sigmod-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-submission into .gemini/skills/sigmod-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-submission", 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 sigmod-submissionInstalls 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 sigmod-submission -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/SIGMOD-Skills/skills/sigmod-submission .github/skills/sigmod-submission && 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 "sigmod-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-submission into .github/skills/sigmod-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-submission", 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 sigmod-submission -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 sigmod-submission --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/SIGMOD-Skills/skills/sigmod-submission .opencode/skills/sigmod-submission && 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 "sigmod-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-submission into .opencode/skills/sigmod-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-submission", 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
sigmod-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 766 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit…
- Readying a SIGMOD research-track submission for a PACMMOD round
- SKILL.md covers What must be true a week early, Format and anonymity gate, Exclusivity and overlap and Round-selection judgment, plus 6 more sections
- Reaches 2027.sigmod.org
- Covering the abstract-plus-COI pre-deadline
What it does
Sigmod Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit, double-anonymous rules, the 10-paper author cap, the 12-month rejection embargo, and desk-reject hazards.
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
- Readying a SIGMOD research-track submission for a PACMMOD round
- Covering the abstract-plus-COI pre-deadline
- Microsoft CMT mechanics
- The 12-page ACM-template limit
Example prompts
- “/sigmod-submission”
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
Hosts in commands or code, which the agent is likely to contact:
2027.sigmod.org
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
Sigmod Submission loads about 1.6k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 766 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). 766 words, ~1,612 tokens.
Download SKILL.mdSave it as
.claude/skills/sigmod-submission/SKILL.md (or your agent's skills folder).- name
- sigmod-submission
- description
- Use when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit, double-anonymous rules, the 10-paper author cap, the 12-month rejection embargo, and desk-reject hazards.
SIGMOD Submission
Run this audit before a round deadline. SIGMOD research papers are journal submissions to PACMMOD (Proceedings of the ACM on Management of Data), reviewed in year-round batches rather than one annual cutoff, so the first question is always "which round," not "which year." Reopen the live CFP for the cycle you target before trusting any number quoted here.
What must be true a week early
SIGMOD front-loads part of the deadline: the abstract and the declaration of conflicts of interest are due roughly one week before the paper itself (SIGMOD 2027: the 10th vs. the 17th of the round month, 11:59 PM AoE). Missing the abstract stage closes the round entirely — there is no PDF-only entry.
- Register the submission in Microsoft CMT with final title, abstract, topic areas, and the complete author list.
- Declare COIs honestly and completely; PC assignment happens off this data.
- Count your load: SIGMOD 2027 caps each author at ten research-track submissions across all four rounds combined.
- Decide now whether a weak draft should wait a round; a rejection triggers a 12-month embargo, and a late withdrawal is treated as a rejection too.
Format and anonymity gate
| Check | SIGMOD 2027 rule (verify per cycle) | Failure mode |
|---|---|---|
| Length | 12 pages max, unlimited pages for references | Desk reject |
| Template | Current ACM template, fonts/margins untouched | Desk reject |
| PACMMOD format | Only for final publication, never for submission | Confused reviewers, chair flag |
| Author identity | No names, affiliations, or funding acknowledgements | Desk reject |
| Colleague thanks | No research-group or collaborator acknowledgements | Anonymity violation |
| Self-references | Third person, no "our prior system" giveaways | Reviewer discount or flag |
| Artifacts | Links must not expose authorship or institution | Anonymity violation |
Note the asymmetry with one-shot conferences: because reviewing is double-anonymous across the full round — including any revision phase — the anonymity discipline must survive months, not weeks. Plan artifact hosting accordingly.
Exclusivity and overlap
PACMMOD requires substantial novel content and exclusive consideration: once submitted, the paper (or anything with substantial overlap in results) stays out of every other venue until PACMMOD rejects it or you withdraw. Rolling PVLDB submissions of a sibling paper are the classic accidental violation — map the overlap between your group's pipelines before the abstract stage.
Round-selection judgment
- Submit to the earliest round the evidence genuinely supports; a revision verdict already builds in one more month of runway.
- Do not burn a round on a draft whose experiments are still moving — the embargo prices failure at three skipped rounds, not one.
- If a companion paper is in PVLDB's monthly queue, stagger topics so neither submission poisons the other's novelty claim.
- Check whether the industrial track fits better before defaulting to research; its calendar and rules are separate and single-shot.
Ten-day countdown
D-10 Freeze contribution claims; stop adding experiments
D-9 Abstract, author list, topics, and COIs into CMT
D-7 Anonymity sweep: PDF metadata, repo URLs, funding lines, cluster names
D-5 Rebuild every plot from committed scripts; diff against paper numbers
D-3 Full ACM-template compliance pass; reference pages excluded from count
D-2 Fresh-eyes read of pages 1-2 by someone outside the project
D-1 Upload final PDF; confirm CMT shows the intended file version
D-0 Re-download from CMT and open the PDF you actually submittedShow full SKILL.md (319 more words)Show less
Round calendar snapshot (SIGMOD 2027, verified 2026-07-08)
| Round | Abstract + COIs | Paper due | First verdict |
|---|---|---|---|
| 1 | Jan 10, 2026 | Jan 17, 2026 | Apr 19, 2026 |
| 2 | Apr 10, 2026 | Apr 17, 2026 | Jul 19, 2026 |
| 3 | Jul 10, 2026 | Jul 17, 2026 | Oct 19, 2026 |
| 4 | Oct 10, 2026 | Oct 17, 2026 | Jan 19, 2027 |
All cutoffs 11:59 PM AoE. Source:
https://2027.sigmod.org/calls_papers_important_dates.shtml. Future cycles
will shift these dates; treat the pattern (quarterly rounds, abstract a week
early) as the durable part and the dates as perishable.
Common desk-reject and triage patterns
- Page 13 of content because an appendix crept ahead of the references.
- A GitHub link whose organization name is the authors' lab.
- Abstract registered under a placeholder title that never got updated.
- The same experimental core simultaneously sitting in a PVLDB revision.
- An acknowledgements section pasted in from a camera-ready of prior work.
None of these are recoverable after the round deadline; all of them are findable in an afternoon before it.
PODS co-location caution
SIGMOD ships with PODS, the theory symposium, under one registration and one week — but they are separate venues with separate CFPs, PCs, deadlines, and publication series. Concretely:
- A theory-leaning paper does not "fall through" to PODS if SIGMOD rejects it; it must be submitted to PODS on PODS's own calendar.
- Do not cite SIGMOD round dates when planning a PODS submission, and vice versa; the calendars are unrelated.
- The exclusivity rule still applies across the pair — the same results cannot sit in both queues at once.
Final self-audit, one minute each
- Open the uploaded PDF from CMT and read the title, author-block area, and page count with fresh eyes.
- Search the PDF text for your surnames, institution, and grant numbers.
- Click every URL in the paper from an incognito window.
- Confirm the abstract in CMT matches the PDF abstract verbatim.
- Confirm the round you think you entered is the round CMT shows.
Output format
[Round verdict] submit this round / hold one round / reroute track
[CMT gate] abstract+COI status, author cap headroom
[Format gate] pages / template / reference handling
[Anonymity gate] pass or the specific leak found
[Overlap gate] PVLDB or other-venue conflicts, embargo exposure
[Ordered fixes] <what to repair before the abstract stage>© 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 SIGMOD-Skills/skills/sigmod-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigmod Submission 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 |
|---|---|---|---|---|---|---|
| Sigmod Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Homelab Network Readinessaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Readyremotion-dev/remotion | 63k | — | ~344 | Automated safety check: Pass | Custom licence | |
| AI Readygithub/awesome-copilot | 40k | 1 repos | ~364 | Automated safety check: Pass | MIT | |
| PR Review Readinesspytorch/pytorch | 104k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Compliance Readinessalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
PR Ready
remotion-dev/remotion
Resolve CI failures, merge conflicts, or local branch changes to get a PR ready
- Official
AI Ready
github/awesome-copilot
Make any repo AI-ready — analyzes your codebase and generates AGENTS.md, copilot-instructions.md, CI workflows, issue templates, and more.
PR Review Readiness
pytorch/pytorch
Non-interactive wrapper over pr-review that emits JSON assessing whether a PR is ready for a human maintainer's time.
Compliance Readiness
alirezarezvani/claude-skills
/cs:compliance-readiness <program — Multi-framework compliance officer 6-question forcing interrogation of any compliance program.
Story Readiness
Donchitos/Claude-Code-Game-Studios
Is a story implementation-ready?. An agent skill from Donchitos/Claude-Code-Game-Studios.
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 Sigmod Submission
What does Sigmod Submission do?
A skill your agent uses when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit…. Sigmod Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when readying a SIGMOD research-track submission for a PACMMOD round, covering the abstract-plus-COI pre-deadline, Microsoft CMT mechanics, the 12-page ACM-template limit, double-anonymous rules, the 10-paper author cap, the 12-month rejection embargo, and desk-reject hazards.
When should I use Sigmod Submission?
Sigmod Submission fits situations like: readying a SIGMOD research-track submission for a PACMMOD round; covering the abstract-plus-COI pre-deadline; microsoft CMT mechanics; the 12-page ACM-template limit.
How do I install Sigmod Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-submission -a claude-code`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigmod-submission in your project. Claude Code loads it when a task matches its description.
How do I install Sigmod Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-submission -a codex`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigmod-submission in your project. Codex loads it when a task matches its description.
Can I use Sigmod Submission 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 sigmod-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sigmod-submission, .gemini/skills/sigmod-submission, .github/skills/sigmod-submission and .opencode/skills/sigmod-submission in your project.
What does Sigmod Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigmod Submission is instructions for the agent only.
Does Sigmod Submission access the network?
SKILL.md names 1 domain. In commands or code: 2027.sigmod.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Sigmod Submission 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 Sigmod Submission use?
Sigmod Submission 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 Sigmod Submission use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Sigmod Submission?
Skills that share tags, products or a category with Sigmod Submission: Homelab Network Readiness (affaan-m/ECC, 277k stars), PR Ready (remotion-dev/remotion, 63k stars), AI Ready (github/awesome-copilot, 40k stars) and PR Review Readiness (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigmod Submission?
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.