CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
A skill your agent uses when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page…
Install Corl Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills corl-workflow --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/CoRL-Skills/skills/corl-workflow .claude/skills/corl-workflow && 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 "corl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoRL-Skills/skills/corl-workflow into .claude/skills/corl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corl-workflow", 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/CoRL-Skills/skills/corl-workflowType 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 corl-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills corl-workflow --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/CoRL-Skills/skills/corl-workflow .agents/skills/corl-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "corl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoRL-Skills/skills/corl-workflow into .agents/skills/corl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corl-workflow", 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 corl-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills corl-workflow --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/CoRL-Skills/skills/corl-workflow .cursor/skills/corl-workflow && 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 "corl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoRL-Skills/skills/corl-workflow into .cursor/skills/corl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corl-workflow", 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 CoRL-Skills/skills/corl-workflow--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 corl-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills corl-workflow --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/CoRL-Skills/skills/corl-workflow .gemini/skills/corl-workflow && 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 "corl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoRL-Skills/skills/corl-workflow into .gemini/skills/corl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corl-workflow", 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 corl-workflowInstalls 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 corl-workflow -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/CoRL-Skills/skills/corl-workflow .github/skills/corl-workflow && 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 "corl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoRL-Skills/skills/corl-workflow into .github/skills/corl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corl-workflow", 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 corl-workflow -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 corl-workflow --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/CoRL-Skills/skills/corl-workflow .opencode/skills/corl-workflow && 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 "corl-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoRL-Skills/skills/corl-workflow into .opencode/skills/corl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corl-workflow", 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
corl-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 732 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page…
- Works in 5 steps: T minus 9–12 months — lock the task… → T minus 6 months — baselines running end… → T minus 3 months — full evaluation… → …
- Planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines
- SKILL.md covers The 2026 cycle as a reference…, Phase playbooks, Team calendar template and Planning a CoRL 2027…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Corl Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.
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 Product & Project Management, covering Project management. 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
- Planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines
- The summer review window
- First-round rejection risk
- The August one-page rebuttal and discussion period
Example prompts
- “/corl-workflow”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- T minus 9–12 months — lock the task suite and data-collection plan; hardware
- T minus 6 months — baselines running end to end; if a claim needs
- T minus 3 months — full evaluation protocol frozen (seeds, episodes, task
- T minus 1 month — supplementary video storyboarded and shot
- Deadline week — abstract registration a few days before the paper deadline
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 (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
corl.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Corl Workflow loads about 1.6k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 732 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). 732 words, ~1,584 tokens.
Download SKILL.mdSave it as
.claude/skills/corl-workflow/SKILL.md (or your agent's skills folder).- name
- corl-workflow
- description
- Use when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.
CoRL Workflow
CoRL runs one cycle per year on a spring-submit / autumn-decide / November-meet rhythm. This skill turns the 2026 calendar (verified 2026-07-08 via corl.org, OpenReview, and the conference's public timeline) into a working plan, including what a team should be doing right now in each phase.
The 2026 cycle as a reference timeline
| Milestone | CoRL 2026 date | Status on 2026-07-08 |
|---|---|---|
| Abstract registration | May 26, 2026 | passed |
| Paper + supplementary deadline | May 29, 2026 | passed |
| Review period (reviewers, ACs, SACs) | June – early August 2026 | in progress |
| Reviews released / first-round rejections | early August 2026 [exact date 待核实] | upcoming |
| One-page PDF rebuttal due | August 11, 2026, 11:59 PM AoE | upcoming |
| Reviewer–AC discussion window | August 12–19, 2026 | upcoming |
| Decision notification | September 2026 [exact date 待核实] | upcoming |
| Camera-ready to PMLR pipeline | October 12, 2026, 23:59 AoE | upcoming |
| Conference (JW Marriott, Austin, TX) | November 9–12, 2026 (workshops Nov 9) | upcoming |
Every date above is a single cycle's snapshot. The 2027 cycle will publish its own timeline at the corl.org year-site; nothing here transfers automatically.
Phase playbooks
Now: the submitted-paper quiet period (June–July)
- Do not update the OpenReview PDF — the submission is frozen; focus energy on experiments you may need for the rebuttal instead.
- Pre-build rebuttal ammunition: the most predictable reviewer asks at CoRL are more seeds, more evaluation episodes, a missing robot-learning baseline, and a real-robot check for a sim-heavy paper. Run these before reviews land; the window between reviews and the August 11 rebuttal deadline is days, not weeks.
- Keep the anonymized project site (if any) untouched and unlinked from any identity; review is double-anonymous until decisions.
- Decide the fallback venue now (see
corl-topic-selection), so a first-round rejection in early August converts to a resubmission plan the same week.
Reviews land (early August)
- Triage against the first-round rejection rule first: in the 2026 process, a paper
with no score of weak-accept-or-above from any reviewer or the AC is a candidate
for rejection without rebuttal. If you are past that gate, the rebuttal is
live — switch to
corl-author-responseimmediately. - Map each concern to: (a) already answered in the paper, (b) answerable with a prepared experiment, (c) requires concession. One page forces this triage anyway.
Rebuttal through decision (mid-August – September)
- Submit the one-page PDF by August 11, 11:59 PM AoE; then remain reachable — the reviewer–AC discussion (Aug 12–19) can surface follow-ups, and reviewers are asked to update scores when a rebuttal warrants it.
- Decisions are finalized in SAC–AC meetings and a final SACs–PCs meeting; there is no author-visible activity in that stage, so use September for the camera-ready or resubmission branch prep.
Show full SKILL.md (308 more words)Show less
Acceptance branch (September – November)
- Camera-ready: 9-page main text (one page more than submission, explicitly to
absorb review feedback),
\usepackage[final]{corl_2026}, appendix merged into the same PDF, due October 12, 23:59 AoE — seecorl-camera-ready. - Remember that reviews and rebuttals of accepted papers are made public: write the camera-ready knowing the exchange will be readable next to it.
- Book Austin early; plan the poster/talk material and the public code release
(
corl-artifact-evaluation) in parallel, not sequentially.
Team calendar template
# corl-cycle-plan.yaml — assign an owner and a date to every row
paper_id: ""
phase_now: post-submission # update as the cycle advances
rebuttal_prep:
extra_seeds_run: {owner: , status: } # started before reviews arrive
missing_baseline: {owner: , status: }
real_robot_spotcheck: {owner: , status: }
one_page_template_ready: {owner: , status: } # LaTeX skeleton compiled
dates_to_watch:
reviews_released: "early Aug 2026 (待核实 — watch OpenReview + corl.org)"
rebuttal_due: "2026-08-11 23:59 AoE"
discussion: "2026-08-12..19"
decision: "Sep 2026 (待核实)"
camera_ready: "2026-10-12 23:59 AoE"
fallback:
venue: "" # decided BEFORE decisions arrive
required_rework: ""Planning a CoRL 2027 submission from scratch
Working backward from a late-May deadline (the 2026 pattern; 2027 dates 待核实):
- T minus 9–12 months — lock the task suite and data-collection plan; hardware time and teleop data are the long poles in robot-learning projects.
- T minus 6 months — baselines running end to end; if a claim needs sim-to-real evidence, the real-robot rig must exist by now, not in April.
- T minus 3 months — full evaluation protocol frozen (seeds, episodes, task
splits —
corl-experiments); start the paper with the Limitations section drafted early, since it is mandatory and counts inside the 8 pages. - T minus 1 month — supplementary video storyboarded and shot
(
corl-supplementary); anonymization sweep of paper, video, and any site. - Deadline week — abstract registration a few days before the paper deadline
(2026 spacing: May 26 vs May 29); final OpenReview form checks per
corl-submission.
Risks specific to this venue's shape
- The rebuttal window is short and fixed; teams that start experiments after reviews arrive routinely miss it. Prepare in the quiet period.
- The single annual deadline means a miss costs a full year — hold the routing
discussion (
corl-topic-selection) before investing deadline-week effort. - Hardware fails on deadline schedules: keep one robot-day of slack per claimed real-robot table in the final month.
Reconfirm every date at https://www.corl.org/ (2026 cycle) or the 2027 year-site before acting; this file records the 2026-07-08 state of knowledge.
© 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 CoRL-Skills/skills/corl-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Corl Workflow 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 |
|---|---|---|---|---|---|---|
| Corl Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Ichartjswanghetommy/ichartjs | 352 | — | ~4.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals in Hivemind via the hivemind CLI.
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 Corl Workflow
What does Corl Workflow do?
A skill your agent uses when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page…. Corl Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.
When should I use Corl Workflow?
Corl Workflow fits situations like: planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines; the summer review window; first-round rejection risk; the August one-page rebuttal and discussion period.
How do I install Corl Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-workflow -a claude-code`. Or copy the skill folder (CoRL-Skills/skills/corl-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/corl-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Corl Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-workflow -a codex`. Or copy the skill folder (CoRL-Skills/skills/corl-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/corl-workflow in your project. Codex loads it when a task matches its description.
Can I use Corl Workflow 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 corl-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/corl-workflow, .gemini/skills/corl-workflow, .github/skills/corl-workflow and .opencode/skills/corl-workflow in your project.
What does Corl Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Corl Workflow is instructions for the agent only.
Does Corl Workflow access the network?
SKILL.md names 1 domain. As links in the text: corl.org. This is read from the text; nothing was executed.
Is Corl Workflow 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 Corl Workflow use?
Corl Workflow 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 Corl Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Corl Workflow?
Skills that share tags, products or a category with Corl Workflow: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.8k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Corl Workflow?
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.