Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
A skill your agent uses when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and…
Install Isca Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-author-response .claude/skills/isca-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 "isca-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-author-response into .claude/skills/isca-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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/ISCA-Skills/skills/isca-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 isca-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-author-response .agents/skills/isca-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 "isca-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-author-response into .agents/skills/isca-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-author-response .cursor/skills/isca-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 "isca-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-author-response into .cursor/skills/isca-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 ISCA-Skills/skills/isca-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 isca-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-author-response .gemini/skills/isca-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 "isca-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-author-response into .gemini/skills/isca-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-author-response .github/skills/isca-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 "isca-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-author-response into .github/skills/isca-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-author-response .opencode/skills/isca-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 "isca-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-author-response into .opencode/skills/isca-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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
isca-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 815 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and…
- Works in 3 steps: Opening block (5-6 lines): thank, then… → Per-objection sections keyed to review… → Shared-objection consolidation: answer…
- ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix
- SKILL.md covers Day 1-2: triage before any…, Day 2: freeze the experiment…, Writing the response document and Using the revision half of the…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Isca Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and a revised PDF with new experiments, structuring responses that arm a champion at the PC meeting, and avoiding window-burning mistakes.
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.
It sits in Documents & Office. 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
- ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix
- Deciding between textual rebuttal and a revised PDF with new experiments
- Structuring responses that arm a champion at the PC meeting
- Avoiding window-burning mistakes
Example prompts
- “/isca-author-response”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Opening block (5-6 lines): thank, then list the concrete changes/results
- Per-objection sections keyed to review IDs, highest-leverage first.
- Shared-objection consolidation: answer once, cross-reference the copies —
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
Isca Author Response loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 815 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). 815 words, ~1,677 tokens.
Download SKILL.mdSave it as
.claude/skills/isca-author-response/SKILL.md (or your agent's skills folder).- name
- isca-author-response
- description
- Use when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and a revised PDF with new experiments, structuring responses that arm a champion at the PC meeting, and avoiding window-burning mistakes.
ISCA Author Response
ISCA 2026 gave authors a combined rebuttal/revision period, February 16 to March 6 — three weeks in which the team could both argue and change the paper. That design rewards teams that treat the window as an engineering sprint with a triage phase, and punishes teams that spend it composing indignation. Everything here assumes that verified 2026 structure; the 2027 window's existence, length, and rules are 待核实 until the new CFP posts.
Day 1-2: triage before any writing or computing
Read all reviews twice: once fast for temperature, once slow building the objection ledger. Classify every distinct point:
| Class | Definition | Window response |
|---|---|---|
| F — factual error | Reviewer misread something present in the PDF | Quote page/section/figure; one sentence; zero new work |
| E — evidence gap, closable | Missing experiment your infrastructure can run in days | Run it; report in response; fold into revision if permitted |
| E∞ — evidence gap, not closable | Needs silicon, months, or data you lack | Concede scope honestly; state what the existing evidence does cover |
| D — design objection | "This breaks under X" / "cost is understated" | Analyze X concretely; if real, add the limitation; if not, show why |
| P — premise objection | "This problem doesn't matter" | Strongest countermeasure is motivation data; if you have none beyond the paper, one calm paragraph and move on |
| T — taste | "I'd have designed it differently" | Acknowledge once; do not redesign the paper |
Then rank by leverage: an F held by two reviewers outranks an E held by one;
anything a likely champion needs to defend the paper outranks everything else
(isca-review-process explains why the champion is the audience).
Day 2: freeze the experiment plan
Pick at most three new experiments — the ones that convert the highest-leverage E-class objections into numbers. Assign owners and a hard finish date one week before window close, leaving prose time. The classic window failure is five half-finished experiments and a response that promises rather than shows.
window-plan.md
R2.O3 (E, leverage=high) "no comparison vs LazyMerge at equal storage"
-> run: lazymerge @ 18KB/core, full suite; owner: MK; due Feb 27
R1.O1 (F, leverage=high) "warm-up unstated"
-> answer: §5.1 para 2, 50M inst; also add to config table in revision
R3.O2 (D, leverage=med) "decay threshold fragile"
-> run: sweep T in {2K..64K}; expect plateau; owner: JL; due Feb 25
R3.O5 (T, leverage=low) "why not epoch-based?"
-> one paragraph, cite §4.2 rationale; no experimentWriting the response document
Structure for committee reading, not reviewer combat:
- Opening block (5-6 lines): thank, then list the concrete changes/results produced during the window — the things a champion can repeat in the room.
- Per-objection sections keyed to review IDs, highest-leverage first. Each: restate the objection in one neutral line, answer with evidence (number, table row, or PDF pointer), stop.
- Shared-objection consolidation: answer once, cross-reference the copies — it shows the committee the objection set is smaller than it looks.
Tone rules that survive contact with real committees: concede real limitations in plain declarative sentences (concessions buy credibility that transfers to your rebuttals); never speculate about reviewer expertise or identity; never claim "all reviewers agree" about anything they don't.
Show full SKILL.md (379 more words)Show less
Using the revision half of the window
If the cycle permits an updated PDF (2026's window was named rebuttal/revision):
- Make surgical edits keyed to objections: the missing baseline column, the config-table row, the limitation paragraph, the clarified walk-through.
- Do not restructure the paper — reviewers re-reading diff mentally against their memory, and a rewritten paper resets their evaluation instead of repairing it.
- Maintain a change log mapping edit → objection; if the process provides no place to submit it, embed the mapping in the response document.
- Keep the paper inside all format rules; a revision that breaks the 11-page
budget converts goodwill into a violation. This is what the half-page of slack
from
isca-writing-stylewas for.
What not to spend the window on
- New contributions. Results beyond the paper's claimed scope read as a different paper and invite "needs another round of review" — the phrase that kills borderline papers.
- Rebutting every sentence. A 15-point response to a 3-objection review buries your leverage. Committees skim; make the skim land the top three.
- Premise litigation at length. One paragraph of motivation defense with data; more looks defensive and reads worse each repetition.
- Simulator relitigating. If a reviewer distrusts your instrument globally, the fix is the validation anchor you either have (point to it) or don't (concede and scope) — not an essay on simulation philosophy.
Window-close checklist
- Every review ID answered or explicitly consolidated
- Top-3 objections answered with numbers produced this window
- All F-class errors corrected with pointers, tone neutral
- Revision (if permitted) diff-minimal, format-legal, change-mapped
- A colleague outside the project read the response cold and could state your three key answers back to you
- Submitted with margin — the window closes AoE like everything else
The three weeks on a calendar
Using the 2026 window (Feb 16 - Mar 6) as the shape:
| Days | Activity |
|---|---|
| 1-2 | Triage; objection ledger; leverage ranking; no computing yet |
| 2 | Experiment plan frozen: ≤3 runs, owners, due dates |
| 3-12 | Experiments execute; response skeleton drafted in parallel |
| 13-15 | Results in; response written against real numbers |
| 16-18 | Revision edits (if permitted), diff-minimal, format-checked |
| 19-20 | Cold read by an outside colleague; tone pass; consolidation pass |
| 21 | Submit with hours to spare, AoE-checked |
After the window, silence until decisions; outcome handling branches in
isca-review-process, and calendar context lives in isca-workflow. Verified
dates: ../../resources/official-source-map.md (2026-07-08).
© 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 ISCA-Skills/skills/isca-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Isca 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 |
|---|---|---|---|---|---|---|
| Isca Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
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…
Related
Categories
Questions about Isca Author Response
What does Isca Author Response do?
A skill your agent uses when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and…. Isca Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and a revised PDF with new experiments, structuring responses that arm a champion at the PC meeting, and avoiding window-burning mistakes.
When should I use Isca Author Response?
Isca Author Response fits situations like: ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix; deciding between textual rebuttal and a revised PDF with new experiments; structuring responses that arm a champion at the PC meeting; avoiding window-burning mistakes.
How do I install Isca Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-author-response -a claude-code`. Or copy the skill folder (ISCA-Skills/skills/isca-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/isca-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Isca Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-author-response -a codex`. Or copy the skill folder (ISCA-Skills/skills/isca-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/isca-author-response in your project. Codex loads it when a task matches its description.
Can I use Isca 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 isca-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/isca-author-response, .gemini/skills/isca-author-response, .github/skills/isca-author-response and .opencode/skills/isca-author-response in your project.
What does Isca Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Isca Author Response is instructions for the agent only.
Does Isca 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 Isca 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 Isca Author Response use?
Isca 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 Isca Author Response 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 Isca Author Response?
Skills that share tags, products or a category with Isca Author Response: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Isca 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.