Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
A skill your agent uses when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts…
Install Colm Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-related-work --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/COLM-Skills/skills/colm-related-work .claude/skills/colm-related-work && 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 "colm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-related-work into .claude/skills/colm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-related-work", 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/COLM-Skills/skills/colm-related-workType 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 colm-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-related-work --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/COLM-Skills/skills/colm-related-work .agents/skills/colm-related-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "colm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-related-work into .agents/skills/colm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-related-work", 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 colm-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-related-work --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/COLM-Skills/skills/colm-related-work .cursor/skills/colm-related-work && 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 "colm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-related-work into .cursor/skills/colm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-related-work", 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 COLM-Skills/skills/colm-related-work--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 colm-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-related-work --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/COLM-Skills/skills/colm-related-work .gemini/skills/colm-related-work && 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 "colm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-related-work into .gemini/skills/colm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-related-work", 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 colm-related-workInstalls 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 colm-related-work -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/COLM-Skills/skills/colm-related-work .github/skills/colm-related-work && 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 "colm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-related-work into .github/skills/colm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-related-work", 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 colm-related-work -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 colm-related-work --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/COLM-Skills/skills/colm-related-work .opencode/skills/colm-related-work && 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 "colm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-related-work into .opencode/skills/colm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-related-work", 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
colm-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 775 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts…
- Works in 3 steps: Sweep arXiv for the last ~3 months… → Give genuinely concurrent work its own… → Never bury a concurrent paper you know…
- Positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations
- SKILL.md covers Triage the literature into lanes, arXiv status honesty, Concurrent work: the protocol and Positioning moves that work here, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Colm Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.
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.
It sits in Research & Science, covering Citation management, Literature review and Academic paper search. It works with arXiv. 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
- Positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations
- Handling concurrent work fairly
- Citing model and dataset artifacts correctly
- Distinguishing COLMs three-edition archive from adjacent venues archives
Example prompts
- “s three-edition archive from adjacent venues”
- “/colm-related-work”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Sweep arXiv for the last ~3 months against your core claims in the final week
- Give genuinely concurrent work its own labeled paragraph: state the overlap and
- Never bury a concurrent paper you know about. A reviewer who finds it first
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
Colm Related Work loads about 1.6k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 775 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). 775 words, ~1,599 tokens.
Download SKILL.mdSave it as
.claude/skills/colm-related-work/SKILL.md (or your agent's skills folder).- name
- colm-related-work
- description
- Use when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.
COLM Related Work
The LM literature moves faster than any archival process: the work you must position against is substantially on arXiv, some of it appeared after your experiments finished, and some "well-known results" are blog posts. A COLM related-work section is therefore an exercise in versioned honesty — saying precisely what existed, where, and when, without pretending the field is tidier than it is.
Triage the literature into lanes
Cover each lane that touches your claim; reviewers at this venue are typically active in two or three of them and will notice a missing lane immediately:
| Lane | What to position against | Typical miss |
|---|---|---|
| Method lineage | The 2-4 papers your technique descends from | Citing a survey instead of the source |
| Phenomenon reports | Prior observations of the effect you study, incl. analysis papers | Ignoring negative or contradictory reports |
| Evaluation infrastructure | The benchmarks/harnesses you use or compete with | Treating a benchmark as neutral ground rather than citable, criticizable work |
| Model artifacts | The model families your claims are scoped to | Citing a company blog when a technical report exists (or vice versa — cite what actually exists) |
| Adjacent-venue archive | Related results at ICLR/NeurIPS/ACL/EMNLP and in COLM 2024-2025 | Assuming COLM reviewers only read COLM |
Checking the COLM 2024 and 2025 accepted lists for near neighbors is cheap and high-yield: citing the venue's own archive signals you know where you are submitting, and the archive is only two editions deep (checked 2026-07-08).
arXiv status honesty
State venue status accurately at citation time: published (venue, year), arXiv-only (cite the arXiv ID; do not launder it into a "publication"), or since-published (prefer the archival version, keep the arXiv date if chronology matters to your priority story). For results that exist only as blog posts or model cards, cite them as what they are, with access dates — at a venue that studies industry models, gray literature is unavoidable; disguising it is the sin.
Concurrent work: the protocol
With a March 31 deadline and a field publishing daily, concurrency is guaranteed. The credible pattern:
- Sweep arXiv for the last ~3 months against your core claims in the final week before submission (and again before the May rebuttal — reviewers will cite what appeared in April).
- Give genuinely concurrent work its own labeled paragraph: state the overlap and the delta in one factual sentence each, without defensive framing.
- Never bury a concurrent paper you know about. A reviewer who finds it first converts a neutral fact into a credibility wound.
Concurrent-work paragraph skeleton:
"Concurrent work [X, arXiv YYMM] also studies <shared object>.
They <their finding, one clause>; we <orthogonal axis: different
models / different measurement / different conclusion and why>.
Results were developed independently."Positioning moves that work here
- Against benchmark papers: engage their validity arguments, not just their difficulty numbers — evaluation critique is a first-class COLM genre.
- Against method papers: identify the assumption or budget under which they win, and place your contribution on that axis rather than claiming dominance.
- Against analysis papers: state whether you replicate, extend, or contradict each prior observation, model-by-model where findings disagree — disagreement across model families is a finding, not an embarrassment.
Show full SKILL.md (291 more words)Show less
A positioning micro-example
The difference between listing and positioning, on one fictional paragraph:
- Listing (weak): "Prior work has studied contamination [1,2,3], benchmarks [4,5], and knowledge cutoffs [6]. We also study contamination."
- Positioning (strong): "[1] detects verbatim overlap via n-gram matching, which [2] shows misses paraphrase leakage; [6] estimates effective cutoffs from model behavior but cannot separate exposure from difficulty drift. Our dated-item design closes exactly that gap: exposure becomes an experimental variable rather than an inference."
Every cited paper in the strong version does work — it carries a specific capability or limitation that motivates a design choice. A COLM reviewer reads related work as the paper's reasoning about its field, not as a bibliography compliance exercise; a paragraph where citations are interchangeable is a paragraph that is not yet written.
Double-blind self-citation
Cite your own prior work in the third person, exactly as you would a stranger's. The
LM-specific trap is artifact continuity: "we evaluate on the dataset of [7]" is
safe; "we extend our dataset [7]" is a leak; a Hugging Face link under your org
inside the related-work section is a hard violation of COLM's no-identifying-links
rule (colm-submission).
Pre-submission citation audit
- Every lane in the table above covered or consciously excluded.
- Every citation's venue status accurate as of the submission date.
- Concurrent-work paragraph present if the sweep found anything; sweep re-run in deadline week.
- No first-person self-reference; no author-resolving artifact links.
- Bibliography sanity pass: LLM-assisted writing has made fabricated references a named disclosure category in COLM's 2026 policy — verify that every entry resolves to a real document. A hallucinated citation found in review reads as an integrity problem, not a typo.
- Citation pages are unlimited under the 2026 format — never cut references to save space; cut prose.
Output format
[Lane coverage] method ▢ phenomenon ▢ eval-infra ▢ artifacts ▢ adjacent-archive ▢
[COLM-archive neighbors] <papers from 2024/2025 accepted lists, or "none — checked">
[arXiv honesty] clean / laundered citations at: <items>
[Concurrent work] handled: <papers> / sweep stale — rerun
[Self-citation risk] none / leaks at: <locations>
[Reference integrity] all resolve / unverified: <count>© 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 COLM-Skills/skills/colm-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Colm Related Work 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 |
|---|---|---|---|---|---|---|
| Colm Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Arxiv MCP Serverblazickjp/arxiv-mcp-server | 3.2k | — | ~353 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
Paper Research on arXiv
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Arxiv MCP Server
blazickjp/arxiv-mcp-server
A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…
Arxiv Paper Writer
appautomaton/latex-arxiv-SKILL
Write LaTeX ML/AI review articles for arXiv using the IEEEtran template and verified BibTeX citations.
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
Works with
Categories
Questions about Colm Related Work
What does Colm Related Work do?
A skill your agent uses when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts…. Colm Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.
When should I use Colm Related Work?
Colm Related Work fits situations like: positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations; handling concurrent work fairly; citing model and dataset artifacts correctly; distinguishing COLMs three-edition archive from adjacent venues archives.
How do I install Colm Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-related-work -a claude-code`. Or copy the skill folder (COLM-Skills/skills/colm-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colm-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Colm Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-related-work -a codex`. Or copy the skill folder (COLM-Skills/skills/colm-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colm-related-work in your project. Codex loads it when a task matches its description.
Can I use Colm Related Work 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 colm-related-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/colm-related-work, .gemini/skills/colm-related-work, .github/skills/colm-related-work and .opencode/skills/colm-related-work in your project.
What does Colm Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Colm Related Work is instructions for the agent only.
Does Colm Related Work 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 Colm Related Work 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 Colm Related Work use?
Colm Related Work 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 Colm Related Work 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 Colm Related Work?
Skills that share tags, products or a category with Colm Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars), Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars) and Literature Review Agent (Ar9av/PaperOrchestra, 679 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Colm Related Work?
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.