Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Agent skill
Itcs Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim…
Install Itcs Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-artifact-evaluation --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/ITCS-Skills/skills/itcs-artifact-evaluation .claude/skills/itcs-artifact-evaluation && 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 "itcs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-artifact-evaluation into .claude/skills/itcs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-artifact-evaluation", 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/ITCS-Skills/skills/itcs-artifact-evaluationType 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 itcs-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-artifact-evaluation --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/ITCS-Skills/skills/itcs-artifact-evaluation .agents/skills/itcs-artifact-evaluation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "itcs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-artifact-evaluation into .agents/skills/itcs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-artifact-evaluation", 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 itcs-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-artifact-evaluation --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/ITCS-Skills/skills/itcs-artifact-evaluation .cursor/skills/itcs-artifact-evaluation && 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 "itcs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-artifact-evaluation into .cursor/skills/itcs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-artifact-evaluation", 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 ITCS-Skills/skills/itcs-artifact-evaluation--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 itcs-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-artifact-evaluation --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/ITCS-Skills/skills/itcs-artifact-evaluation .gemini/skills/itcs-artifact-evaluation && 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 "itcs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-artifact-evaluation into .gemini/skills/itcs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-artifact-evaluation", 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 itcs-artifact-evaluationInstalls 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 itcs-artifact-evaluation -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/ITCS-Skills/skills/itcs-artifact-evaluation .github/skills/itcs-artifact-evaluation && 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 "itcs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-artifact-evaluation into .github/skills/itcs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-artifact-evaluation", 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 itcs-artifact-evaluation -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 itcs-artifact-evaluation --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/ITCS-Skills/skills/itcs-artifact-evaluation .opencode/skills/itcs-artifact-evaluation && 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 "itcs-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-artifact-evaluation into .opencode/skills/itcs-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-artifact-evaluation", 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
itcs-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 506 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim…
- Adapt the idea of an artifact to a pure-theory venue — at ITCS there is no artifact-evaluation track
- SKILL.md covers The ITCS "artifact" is the proof, The public full version as the…, When a paper does have… and What does NOT transfer from…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version
What it does
Itcs Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version, plus checkable finite objects for any computational content.
Its SKILL.md is about 1.3k 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, covering PDF. 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
- Adapt the idea of an artifact to a pure-theory venue — at ITCS there is no artifact-evaluation track
- The analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version
- Plus checkable finite objects for any computational content
Example prompts
- “artifact”
- “/itcs-artifact-evaluation”
Requirements
- Docker
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
Itcs Artifact Evaluation loads about 1.3k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 506 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). 506 words, ~1,254 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- itcs-artifact-evaluation
- description
- Use to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version, plus checkable finite objects for any computational content.
ITCS Artifact Evaluation
ITCS has no artifact-evaluation track. There are no ACM/IEEE artifact badges, no Available/Functional/Reusable/Reproduced tiers, no code submission, and no evaluation committee inspecting a package. It is a pure-theory venue: the thing that must be independently verifiable is the mathematics. This skill exists because authors arriving from empirical CS (where "artifact evaluation" is a real post-acceptance track) need to know what plays that role at ITCS — and what does not apply.
The ITCS "artifact" is the proof
The artifact that a reviewer inspects is the argument itself. Making it "evaluatable" means:
- Complete proofs of every central claim, inside the submitted PDF (body sketch + appendix
full proof). This is the single most important "artifact" obligation and it is enforced at
submission, not post-acceptance (see
itcs-submissionanditcs-reproducibility). - Self-contained definitions so the claims can be verified without your other papers open.
- Pinned dependencies — every borrowed theorem cited to a precise statement, so a reviewer can audit what you assume versus prove.
There is nothing to "install," nothing to "run," and no badge to earn. The equivalent of a reproduced result is a reviewer following the proof to the end and agreeing.
The public full version as the durable, verifiable record
The closest thing ITCS has to an "available artifact" is the full version on arXiv / ECCC / IACR ePrint, which authors are encouraged to post under lightweight double-blind:
- It is the permanent open record of the complete argument — the analogue of an archived, DOI-bearing artifact, except it is the paper itself, open access, mirrored by LIPIcs on acceptance.
- It does not substitute for proofs in the submitted PDF. During review the PC judges the
submission; a central proof that lives only in the preprint counts as absent (see
itcs-supplementary). - Keep the preprint and submission in sync so the "artifact" a later reader verifies matches the one the PC accepted.
Show full SKILL.md (198 more words)Show less
When a paper does have computational content
Occasionally an ITCS paper leans on a small computation — a search that found a gadget, a solver certifying a finite separation. Make that checkable, in the spirit of an artifact but without a track to submit it to:
- Include the finite object (the graph, code, certificate) so verification is a static check, not a re-run. A reviewer confirming that a supplied 12-vertex graph has the claimed property is the theory analogue of "reproduced."
- State the search space and the tool/version so the computation is auditable in principle.
- Do not host it on a personal repository during review — that is a lightweight-double-blind
leak; fold small objects into an appendix (see
itcs-experiments).
What does NOT transfer from empirical-CS artifact tracks
| Empirical-CS artifact concept | ITCS reality |
|---|---|
| Available / Functional / Reusable / Reproduced badges | None — no badges exist at ITCS |
| A separate artifact-evaluation committee & deadline | None — the PC judges the proofs at review time |
| Docker image / build script / environment pinning | Irrelevant — there is no code to build |
| "Reproduce the numbers" | Replaced by "follow the proof and agree" |
| Post-acceptance artifact submission | The post-acceptance task is the LIPIcs camera-ready (see itcs-camera-ready) |
Verifiability checklist (the ITCS "artifact" pass)
[Proofs-in-PDF] every central claim fully proved inside the submitted PDF? yes/no
[Self-contained] claims verifiable without the authors' other papers? yes/no
[Dependencies] borrowed results pinned to precise statements? yes/no
[Full version] posted (arXiv/ECCC/ePrint) and consistent with the submission? yes/no
[Compute objects] any finite computational witness included and statically checkable? yes/no/NA
[Anonymity] no personal-repo link exposing identity during review? yes/noOutput format
[ITCS verifiability status] independently-checkable / gaps
[Proof artifact] central claims proved in-PDF? self-contained? dependencies pinned? (yes/no)
[Durable record] full version posted and in sync? yes/no
[Computational witness] finite object included & checkable? yes/no/NA
[Note] there is no badge/track — the deliverable is a checkable proof, not a package
[Fix queue] <ordered; unproved central claims first>© 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 ITCS-Skills/skills/itcs-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs Artifact Evaluation 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 |
|---|---|---|---|---|---|---|
| Itcs Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Paper LensYSQ-boop/paper-lens | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Paper ReviewRapidAI/MaClaw | 147 | — | ~1k | Automated safety check: Pass | MIT | |
| Ma Fulltext Managementhtlin222/meta-pipe | 139 | — | ~1.7k | Automated safety check: Notes | Custom licence | |
| Paper Interpreterchujianyun/skills | 740 | — | ~810 | Automated safety check: Pass | Custom licence |
Similar skills
Paper Lens
YSQ-boop/paper-lens
Read and critically analyze one academic paper from an arXiv URL/ID or a local PDF, producing a source-grounded Markdown report that can grow from a quick read into a reviewer-level deep review.
Paper Review
RapidAI/MaClaw
论文深度解读 Skill — 下载论文PDF → LLM深度解读（问题/创新点/方法原理/实验分析）→ PDF图片提取 → 生成组会PPT → 生成解读音频MP3。端到端学术论文解读工具。
Ma Fulltext Management
htlin222/meta-pipe
Collect and manage full-text PDFs for included studies, track provenance, and prepare documents for extraction.
Paper Interpreter
chujianyun/skills
论文解读助手。适用于用户发送 arXiv 论文链接，并希望下载论文、解读论文、生成读书笔记、做论文拆解或输出详细报告时使用。会在工作目录创建论文文件夹、下载 PDF 与 TeX Source（如有）、生成中文 Markdown 报告。默认先交付初稿，不自动复查；如果用户明确同意，再安排后续复查。不适用于只要简短推荐语的情况。
Mindmap Render
ai4s-research/ai4s-skills
Generate beautiful, high-resolution mindmaps from Markdown unordered lists.
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 Itcs Artifact Evaluation
What does Itcs Artifact Evaluation do?
A skill your agent uses to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim…. Itcs Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version, plus checkable finite objects for any computational content.
When should I use Itcs Artifact Evaluation?
Itcs Artifact Evaluation fits situations like: adapt the idea of an artifact to a pure-theory venue — at ITCS there is no artifact-evaluation track; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version; plus checkable finite objects for any computational content.
How do I install Itcs Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-artifact-evaluation -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-artifact-evaluation -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Itcs Artifact Evaluation 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 itcs-artifact-evaluation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/itcs-artifact-evaluation, .gemini/skills/itcs-artifact-evaluation, .github/skills/itcs-artifact-evaluation and .opencode/skills/itcs-artifact-evaluation in your project.
What does Itcs Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Itcs Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Itcs Artifact Evaluation 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 Itcs Artifact Evaluation 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 Itcs Artifact Evaluation use?
Itcs Artifact Evaluation 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 Itcs Artifact Evaluation use?
About 1.3k tokens (SKILL.md is roughly 5k 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 Itcs Artifact Evaluation?
Skills that share tags, products or a category with Itcs Artifact Evaluation: Paper Interpretation (digoal/blog, 8.6k stars), Paper Lens (YSQ-boop/paper-lens, 101 stars), Paper Review (RapidAI/MaClaw, 147 stars) and Ma Fulltext Management (htlin222/meta-pipe, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itcs Artifact Evaluation?
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.