Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
A skill your agent uses when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page…
MITAuto-check passed
Install Sigmod Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-author-response --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-author-response .claude/skills/sigmod-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-author-response into .claude/skills/sigmod-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-author-response --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-author-response .agents/skills/sigmod-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-author-response into .agents/skills/sigmod-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-author-response --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-author-response .cursor/skills/sigmod-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-author-response into .cursor/skills/sigmod-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-author-response --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-author-response .gemini/skills/sigmod-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-author-response into .gemini/skills/sigmod-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/sigmod-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-author-response into .github/skills/sigmod-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/sigmod-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-author-response into .opencode/skills/sigmod-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 660 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page…
- Works in 5 steps: Extract every sentence in the… → Classify each as: run new experiment /… → Budget the single extra page before… → …
- Writing SIGMOD author feedback during a PACMMOD round
- SKILL.md covers Turn 1: the feedback phase, Turn 2: the revision letter, Revision triage order and Skeleton letter, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sigmod Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page letter limit, per-reviewer change highlighting, the extra content page, and anonymity that must hold through resubmission.
Its SKILL.md is about 1.5k 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
- Writing SIGMOD author feedback during a PACMMOD round
- The revision letter after a major/minor-revision verdict
- Covering the mid-round feedback window
- The four-page letter limit
Example prompts
- “/sigmod-author-response”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Extract every sentence in the meta-review and reviews that states a
- Classify each as: run new experiment / rewrite / clarify / decline.
- Budget the single extra page before writing — decide which requirement
- Draft edits in the paper first, the letter second; a letter written before
- Re-run the anonymity sweep on everything new: fresh plots, new repo
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
Sigmod Author Response loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 660 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). 660 words, ~1,462 tokens.
Download SKILL.mdSave it as
.claude/skills/sigmod-author-response/SKILL.md (or your agent's skills folder).- name
- sigmod-author-response
- description
- Use when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page letter limit, per-reviewer change highlighting, the extra content page, and anonymity that must hold through resubmission.
SIGMOD Author Response
SIGMOD gives authors two distinct speaking turns per round, and they play by different rules. The mid-round author feedback phase (about a week, two months after submission — e.g., Sep 10–17, 2026 for Round 3 of SIGMOD 2027) is a short clarification exchange before first verdicts. The revision letter accompanies a resubmission after a major or minor revision decision and is a full engineering document. Confirm the current round's mechanics in the live CFP before drafting either.
Turn 1: the feedback phase
- Correct factual review errors first: a misread experiment, a baseline the reviewer missed, a theorem condition quoted wrong.
- Answer direct reviewer questions with pointers into the submitted PDF — section, table, and figure numbers, not paraphrase.
- Do not promise future experiments as if they were done; the revision phase exists precisely so that promised work can be delivered and re-checked.
- Preserve anonymity absolutely: no institutional context, no "in our
production deployment at
<company>" slips. - Stay inside whatever length box CMT enforces this cycle; verify it live.
Turn 2: the revision letter
A revision verdict at SIGMOD is an offer with a contract. For SIGMOD 2027: the revised paper may add one extra content page, the letter runs up to four pages, and every change must be highlighted in a different color per reviewer, cross-referenced by section and page (line numbers when possible).
| Letter component | What reviewers expect | Frequent failure |
|---|---|---|
| Change inventory | Requirement-by-requirement table, each mapped to an edit | Narrative essay with no map |
| Color key | One color per reviewer, stated up front | Uniform highlighting nobody can attribute |
| New evidence | Requested experiments actually run, numbers in the paper | Results only in the letter, not the paper |
| Declined requests | Explicit, reasoned, respectful refusal | Silent omission discovered on re-review |
| Locators | Section/page/line for every edit | "See revised Section 5" with no page |
Revision triage order
- Extract every sentence in the meta-review and reviews that states a requirement; number them R1.1, R2.1, and so on.
- Classify each as: run new experiment / rewrite / clarify / decline.
- Budget the single extra page before writing — decide which requirement owns it, because two half-answers waste it.
- Draft edits in the paper first, the letter second; a letter written before the edits describes intentions, not changes.
- Re-run the anonymity sweep on everything new: fresh plots, new repo snapshots, and added acknowledg— no, still none allowed.
Skeleton letter
Revision letter — Submission #NNN (Round k)
Color key: R1 = blue, R2 = orange, R3 = green.
R1.1 (required) "Compare against <baseline> on skewed workloads."
Done. New Sec 6.4, Fig 9 (p. 11, blue). <Baseline> tuned per its
authors' guidance; config in Appendix B.
R1.2 (suggested) "Discuss recovery cost."
Added one paragraph, Sec 5.2 (p. 8, blue).
R2.1 (required) "Clarify the consistency guarantee under partition."
Rewrote Sec 4.1 (p. 6, orange); the guarantee is unchanged, the prose
overstated it. We now state exactly what is and is not guaranteed.
R3.1 (declined) "Port the engine to <other system>."
We explain in Sec 7 (p. 12, green) why the design is engine-agnostic;
a full port exceeds a revision cycle and does not test the claim.Show full SKILL.md (266 more words)Show less
Deadline geometry
The revision window is one month (e.g., verdict Oct 19 → revised paper Nov 19 for Round 3 of SIGMOD 2027), with the final accept/reject about three weeks later. Reviewers evaluate only whether the stated requirements were met — a revision is not an invitation to add a new contribution, and scope creep reads as instability. Withdrawing instead of revising counts as a rejection for the 12-month embargo, so price that before walking away.
Feedback-phase micro-example
Reviewer question: "Figure 7 shows your system slower than Baseline B at low thread counts — this seems to contradict the Section 3 claim."
Weak reply: "Thank you for the careful reading. Our system is designed for high concurrency, and we believe the low-thread regime is less relevant in practice."
Strong reply: "Sec 3's claim is scoped to contended workloads (p. 4, lines 12-14): under 8 threads there is no contention to remove, so we pay our bookkeeping overhead (quantified at 4-7% in Tab 3) without benefit. Fig 7 is consistent with that scoping; we will make the boundary explicit in the Fig 7 caption."
The strong version concedes the measured fact, cites its own scoping, and prices the overhead — three moves in four sentences, no adjectives.
Tone calibration for a systems audience
- Concede real bugs plainly and show the corrected numbers; database reviewers forgive errors faster than they forgive spin.
- Quantify every "we clarified" with what a reader can now compute or verify that they could not before.
- Never argue that a requirement is unreasonable in the feedback phase; argue it, if ever, in the letter with evidence.
Output format
[Phase] feedback window / revision letter
[Requirement ledger] Rk.n -> done / partial / declined, with locator
[Extra-page plan] which requirement owns the added page
[New-evidence risk] experiments promised vs. actually landed
[Anonymity re-check] pass or leak found in new material
[Send-readiness] ready / blocked on <item>© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigmod Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Feedbackcodewhale-hq/Codewhale | 41k | — | ~272 | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Aaai Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~924 | Automated safety check: Pass | MIT | |
| Socc Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Feedback
codewhale-hq/Codewhale
Report a Codewhale bug or idea as a GitHub issue. An agent skill from codewhale-hq/Codewhale.
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
Aaai Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance…
Socc Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ACM SoCC author response (rebuttal) during a round's response window, covering the single written turn, answering both the systems and the data/measurement…
Edbt Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting EDBT author responses across the two turns of a cycle — the short author-feedback reply on the initial reviews, and the in-cycle revise-and-resubmit change…
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 Author Response
What does Sigmod Author Response do?
A skill your agent uses when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page…. Sigmod Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing SIGMOD author feedback during a PACMMOD round or the revision letter after a major/minor-revision verdict, covering the mid-round feedback window, the four-page letter limit, per-reviewer change highlighting, the extra content page, and anonymity that must hold through resubmission.
When should I use Sigmod Author Response?
Sigmod Author Response fits situations like: writing SIGMOD author feedback during a PACMMOD round; the revision letter after a major/minor-revision verdict; covering the mid-round feedback window; the four-page letter limit.
How do I install Sigmod Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-author-response -a claude-code`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigmod-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Sigmod Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-author-response -a codex`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigmod-author-response in your project. Codex loads it when a task matches its description.
Can I use Sigmod Author Response 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-author-response -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-author-response, .gemini/skills/sigmod-author-response, .github/skills/sigmod-author-response and .opencode/skills/sigmod-author-response in your project.
What does Sigmod Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigmod Author Response is instructions for the agent only.
Does Sigmod Author Response 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 Sigmod Author Response 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 Author Response use?
Sigmod Author Response 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 Author Response use?
About 1.5k tokens (SKILL.md is roughly 5.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 Sigmod Author Response?
Skills that share tags, products or a category with Sigmod Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Feedback (codewhale-hq/Codewhale, 41k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars) and Aaai Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigmod Author Response?
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.