Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between…
Install Soda Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-workflow .claude/skills/soda-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 "soda-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-workflow into .claude/skills/soda-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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/SODA-Skills/skills/soda-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 soda-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-workflow .agents/skills/soda-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 "soda-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-workflow into .agents/skills/soda-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 soda-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-workflow .cursor/skills/soda-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 "soda-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-workflow into .cursor/skills/soda-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 SODA-Skills/skills/soda-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 soda-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-workflow .gemini/skills/soda-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 "soda-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-workflow into .gemini/skills/soda-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 soda-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 soda-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/SODA-Skills/skills/soda-workflow .github/skills/soda-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 "soda-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-workflow into .github/skills/soda-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 soda-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 soda-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/SODA-Skills/skills/soda-workflow .opencode/skills/soda-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 "soda-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-workflow into .opencode/skills/soda-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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
soda-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 784 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 SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between…
- Planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline
- SKILL.md covers SODA's seat in the theory year, Backward plan to July 9, If the deadline is this week and The quiet phases and their jobs, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- SODAs seat in the theory calendar between STOC and FOCS deadlines
What it does
Soda Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. 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 SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline
- SODAs seat in the theory calendar between STOC and FOCS deadlines
- The September rebuttal and October decision
- Satellite deadlines (ALENEX
Example prompts
- “/soda-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
Soda Workflow loads about 1.7k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 784 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). 784 words, ~1,659 tokens.
Download SKILL.mdSave it as
.claude/skills/soda-workflow/SKILL.md (or your agent's skills folder).- name
- soda-workflow
- description
- Use when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.
SODA Workflow
The 2027 anchor calendar, checked 2026-07-08 (SIAM SODA27/ALENEX27/SOSA27 pages
via search renderings; siam.org blocked direct fetches): papers due July 9,
2026 (AoE) on soda27.hotcrp.com; reviews to authors by September 1; responses
due September 4; decisions October 2026; conference January 24-27, 2027,
Philadelphia, co-located with ALENEX (papers due July 20, 2026) and SOSA
(papers due August 6, 2026). SODA appoints a new PC every cycle under joint
SIAM/ACM SIGACT sponsorship — every date here is a 2027-cycle snapshot, void for
any other year until re-checked.
SODA's seat in the theory year
Theory groups plan around three rotating deadlines, and SODA's is the summer one:
| Beat | Deadline season | Conference season | 2026-27 anchors |
|---|---|---|---|
| SODA | early-mid July | January | July 9, 2026 → January 24-27, 2027 |
| STOC | early November | June | pattern; 2027 dates 待核实 |
| FOCS | early April | October-November | pattern; 2027 dates 待核实 |
Sitting in SODA's seat, the planning consequences are:
- A result finished in spring has a natural July home at SODA; pushing to the November STOC deadline buys four months you may not need and delays the talk by five.
- A SODA rejection lands in October — about a month before STOC's deadline. That is enough time for presentation surgery and review-driven repairs, not for new mathematics. Decide within a week of the decision.
- A result that misses July 9 waits four months (STOC), nine months (FOCS), or twelve (next SODA). Theory culture never punishes a year's delay; it always punishes a broken lemma. When in doubt, wait.
- January is also ITCS season: a conceptual paper rejected from SODA often fits ITCS's early-September deadline pattern (2027 dates: 待核实).
Backward plan to July 9
| Checkpoint | State of the project |
|---|---|
| T-12 weeks (mid-April) | Result proved to the group's satisfaction; claims ledger opened (soda-reproducibility) |
| T-8 weeks (mid-May) | Full proofs written as prose — writing is the verification |
| T-6 weeks (late May) | Blind proof-check pass: each proof verified by a non-author of that proof |
| T-4 weeks (June) | Front matter built: title-page abstract, overview, prior-bound table (soda-writing-style); final arXiv sweep for concurrent work |
| T-2 weeks | Format and anonymity audit (soda-submission); HotCRP record created; conflicts entered |
| T-1 week | Full-document read by the least-involved coauthor; freeze |
| July 9, AoE | Upload confirmed by re-downloading the stored PDF |
The classic failure is proving through June: theorem-finishing scheduled inside the writing window converts both into deadline-night work.
If the deadline is this week
This pack's anchor deadline (July 9, 2026) sits in early July — so a reader in the first week of July 2026 is not planning, but triaging. Honest triage:
| State of the paper today | Verdict |
|---|---|
| Proofs complete, front matter rough | Submit: polish the abstract and overview first, in that order — they carry triage review |
| One proof "almost works" | Do not submit the claim. Either weaken the theorem to what is proved, or hold the paper for STOC |
| Complete but nobody re-checked the proofs | Submit only with a same-week blind check of the main theorem; a withdrawn SODA paper costs less than a refuted one |
| Result strong, writing chaotic | Submit if the first ten pages can be made honest by Thursday; the back matter is verified, not enjoyed |
| Waiting on an experiment | Cut it; experiments are optional evidence at SODA (soda-experiments) and never worth a missed AoE cutoff |
The one thing not to do in deadline week: broaden claims to justify the rush. Reviewers arrive in August with time you did not have.
Show full SKILL.md (226 more words)Show less
The quiet phases and their jobs
- July-August (refereeing): do not idle. Maintain the claims ledger, pre-draft the two predictable rebuttal paragraphs, post/refresh the arXiv version, and decide whether an ALENEX (July 20) or SOSA (August 6) companion is real.
- September 1-4 (rebuttal): the three-day sprint; all-hands availability
arranged in advance (
soda-author-response). - September-October (PC deliberation): silence is structural, not informative. Prepare both branches: camera-ready plan and re-route plan.
- October-January (accepted branch): condensation, SIAM forms, arXiv sync,
talk build (
soda-camera-ready); registration logistics for Philadelphia.
Owner discipline for a group submission
Every deadline on this page needs exactly one named owner, decided in June:
- Deadline owner — watches the SIAM page for changes, does the final upload, holds the HotCRP credentials, converts AoE to local time correctly.
- Ledger owner — maintains the claims ledger from
soda-reproducibilitythrough submission and into rebuttal week. - Rebuttal owner — pre-books the September 1-4 window across all coauthor calendars in July, when calendars are still empty.
- Satellite owner — if an ALENEX or SOSA companion exists, it gets its own three owners; shared ownership across sibling submissions is how one deadline eats another.
Multi-paper and satellite choreography
Decision tree for a group with theory + implementation results in June 2026:
1. Theory result stands alone? -> SODA by July 9
2. Implementation contribution disjoint? -> ALENEX by July 20 (AE follows)
3. Simplification of a known result? -> SOSA by August 6
4. Same claims in two of the above? -> pick one; overlap risks both
Each paper needs its own contribution sentence that mentions no sibling.One calendar per paper, one owner per deadline. Shared-author papers at SODA and a satellite also share the January trip — one registration decision, one talk rehearsal block, and no scheduling collision (satellites run January 24-26, inside the SODA window).
Output format
[Cycle verdict] Submit July 9 / hold for STOC / re-route
[Backward plan] <checkpoint dates with owners, from today>
[Quiet-phase tasks] <ledger, rebuttal prep, arXiv, satellite decisions>
[Contingency] <October rejection branch: repair-for-STOC or wait>
[Satellite calendar] <ALENEX/SOSA/ITCS deadlines in play, if any>© 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 SODA-Skills/skills/soda-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Soda 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 |
|---|---|---|---|---|---|---|
| Soda Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 Soda Workflow
What does Soda Workflow do?
A skill your agent uses when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between…. Soda Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.
When should I use Soda Workflow?
Soda Workflow fits situations like: planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline; SODAs seat in the theory calendar between STOC and FOCS deadlines; the September rebuttal and October decision; satellite deadlines (ALENEX.
How do I install Soda Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-workflow -a claude-code`. Or copy the skill folder (SODA-Skills/skills/soda-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/soda-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Soda Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-workflow -a codex`. Or copy the skill folder (SODA-Skills/skills/soda-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/soda-workflow in your project. Codex loads it when a task matches its description.
Can I use Soda 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 soda-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/soda-workflow, .gemini/skills/soda-workflow, .github/skills/soda-workflow and .opencode/skills/soda-workflow in your project.
What does Soda Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Soda Workflow is instructions for the agent only.
Does Soda 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 Soda 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 Soda Workflow use?
Soda 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 Soda Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Soda Workflow?
Skills that share tags, products or a category with Soda Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Soda 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.