Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
A skill your agent uses when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the…
MITAuto-check passed
Install Edbt Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-workflow .claude/skills/edbt-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 "edbt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-workflow into .claude/skills/edbt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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/EDBT-Skills/skills/edbt-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 edbt-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-workflow .agents/skills/edbt-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 "edbt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-workflow into .agents/skills/edbt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 edbt-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-workflow .cursor/skills/edbt-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 "edbt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-workflow into .cursor/skills/edbt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 EDBT-Skills/skills/edbt-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 edbt-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-workflow .gemini/skills/edbt-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 "edbt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-workflow into .gemini/skills/edbt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 edbt-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 edbt-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/EDBT-Skills/skills/edbt-workflow .github/skills/edbt-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 "edbt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-workflow into .github/skills/edbt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 edbt-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 edbt-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/EDBT-Skills/skills/edbt-workflow .opencode/skills/edbt-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 "edbt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-workflow into .opencode/skills/edbt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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
edbt-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 727 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the…
- Planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle
- SKILL.md covers The cycle structure (one…, Choosing a cycle, Milestones and Backward plan from a cycle…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window
What it does
Edbt Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.
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.
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 an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle
- Backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window
- Handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings
Example prompts
- “/edbt-workflow”
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
Edbt Workflow loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 727 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). 727 words, ~1,568 tokens.
Download SKILL.mdSave it as
.claude/skills/edbt-workflow/SKILL.md (or your agent's skills folder).- name
- edbt-workflow
- description
- Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.
EDBT Workflow
Use this as the project-management skill for an EDBT submission. EDBT's defining rhythm is the multiple-cycle rolling model (three cycles a year since 2022), so the first planning act is not "hit the deadline" but "choose the cycle my evidence is ready for." Replace every date with the current host-site timetable; the per-cycle author-feedback and revision windows are decided per edition.
EDBT is a conference whose proceedings are open access on OpenProceedings.org (CC-BY-NC-ND, no APC): it has no standing editor-in-chief, the rotating leadership is the per-edition General and Program Chairs appointed with the EDBT Association, and the host site moves each year (Barcelona 2025, Tampere 2026). Re-check the current host page rather than carrying a name or URL forward.
The cycle structure (one cycle, end to end)
Each EDBT cycle runs the same five-step arc (EDBT 2022 timeline; reverify dates per edition):
[1] Submission upload PDF + artifact to Microsoft CMT by the cycle deadline
[2] Author feedback phase a short window to respond to initial reviews
[3] Notification #1 accept / REVISE / reject
[4] Revised submission if REVISE: upload the revised paper + change letter
[5] Notification #2 accept / reject on the revisionThe revise branch is a genuine in-cycle revise-and-resubmit re-read by the same reviewers — plan for it, do not treat it as a formality. Papers accepted in the earlier cycles present at that year's conference; papers accepted in the last cycle roll to the next edition.
Choosing a cycle
| Situation | Cycle choice |
|---|---|
| Evidence complete, artifact built, writing solid | The nearest cycle — do not wait a full third of a year for polish |
| One key experiment still running | The next cycle — a rushed submission burns a revise chance you could earn |
| You want to present at this specific edition | An earlier cycle of that year; the last cycle rolls forward |
| Just rejected from an EDBT track in this format | None for 12 months — the resubmission ban applies (edbt-submission) |
Milestones
- Venue fit + shape: confirm EDBT over SIGMOD/VLDB/ICDE/ICDT and pick Regular / Experiments-&-
Analysis / Vision (
edbt-topic-selection). - Evidence lock: freeze workloads, datasets, baselines, measurements, and the artifact contents.
- Cycle choice: commit to a cycle and back-plan from its deadline.
- Submission: upload the PDF and artifact to Microsoft CMT.
- Author feedback: answer the initial reviews concisely in the feedback window
(
edbt-author-response). - Revise (if issued): execute the revised paper plus a point-by-point change letter within the in-cycle window, re-read by the original reviewers.
- Decision: archive reviews, responses, and every submitted version.
- Acceptance: prepare the OpenProceedings camera-ready, finalize the artifact and its DOI archive, register, and present at the edition your cycle feeds.
Backward plan from a cycle deadline
| Weeks out (heuristic) | Database-systems milestone |
|---|---|
| 10+ | Problem and claims fixed; workloads, datasets, and baselines chosen |
| 8 | System/prototype stable; measurement harness and provenance logging in place |
| 6 | Full evaluation run; results and scope drafted alongside them |
| 4 | Full draft in the host/OpenProceedings template; artifact assembled |
| 3 | Internal mock review by a DB-systems reader; baseline fairness challenged |
| 2 | Scope hardened, related-work delta sharpened, page budget met for the shape |
| 1 | Artifact re-run clean; availability/reproducibility statement final |
| 0 | CMT fields complete; PDF + artifact uploaded before the cycle cutoff |
These offsets are planning heuristics only — anchor every one to the current host-site timetable, never to a previous cycle's calendar.
Show full SKILL.md (238 more words)Show less
Cycle-hopping: the honest calendar reality
- A revise you cannot finish in the in-cycle window is not automatically portable to the next cycle — the revision is scored within the cycle. Budget the revision window like a hard deadline rather than assuming a rollover.
- Missing a cycle costs roughly a third of a year, not a whole one — EDBT's biggest scheduling advantage over single-deadline venues. But a rejected paper still owes the 12-month same-format resubmission ban, so a rushed reject is expensive.
- The cycle-to-conference roll is real: a last-cycle acceptance presents at the following edition. If presenting at a specific city/year matters (travel, graduation, funding), target an earlier cycle of that year.
Failure modes by stage
- Submitting into an early cycle with evidence still moving forfeits the revise opportunity you could have earned with two more weeks of measurement.
- Treating the revise as a formality and under-budgeting the in-cycle window turns a winnable revise-and-resubmit into a reject.
- Skipping the mock review forfeits the one chance to hear "your baseline is unfair" or "this scale is unrealistic" from a friend instead of a reviewer.
- Assuming the last cycle presents this year — it rolls to the next edition; plan travel accordingly.
Coordination notes
- Assign one owner for the artifact/reproducibility package and another for the measurement harness; shared ownership is how provenance slips.
- Archive the exact submitted PDF and artifact — the revision round and the change letter must quote them precisely.
Output format
[Current stage] idea / evidence / cycle-chosen / submitted / author-feedback / revise / accepted
[Target cycle] cycle N, deadline <date and source>, presents at <edition/year>
[Critical path] <three tasks that determine readiness>
[Revise risk] <can the likely revision be finished inside the in-cycle window?>
[Owner map] <task -> person or role>© 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 EDBT-Skills/skills/edbt-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Edbt 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 |
|---|---|---|---|---|---|---|
| Edbt Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 98k | 1 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Credit Cycle Analysissickn33/agentic-awesome-skills | 47k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Credit Cycle Analysis
sickn33/agentic-awesome-skills
Debtor and creditor credit-cycle analysis: weighted collection or payment days, ageing buckets, credit limit utilisation and gap against benchmark.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Edbt Workflow
What does Edbt Workflow do?
A skill your agent uses when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the…. Edbt Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.
When should I use Edbt Workflow?
Edbt Workflow fits situations like: planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle; backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window; handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.
How do I install Edbt Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-workflow -a claude-code`. Or copy the skill folder (EDBT-Skills/skills/edbt-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/edbt-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Edbt Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-workflow -a codex`. Or copy the skill folder (EDBT-Skills/skills/edbt-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/edbt-workflow in your project. Codex loads it when a task matches its description.
Can I use Edbt 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 edbt-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/edbt-workflow, .gemini/skills/edbt-workflow, .github/skills/edbt-workflow and .opencode/skills/edbt-workflow in your project.
What does Edbt Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Edbt Workflow is instructions for the agent only.
Does Edbt Workflow 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 Edbt 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 Edbt Workflow use?
Edbt 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 Edbt 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 Edbt Workflow?
Skills that share tags, products or a category with Edbt Workflow: Project Timeline Report (thedotmack/claude-mem, 98k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Credit Cycle Analysis (sickn33/agentic-awesome-skills, 47k stars) and Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Edbt Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.