Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
A skill your agent uses when planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April…
MITAuto-check passed
Install Rss Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-workflow .claude/skills/rss-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 "rss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-workflow into .claude/skills/rss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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/RSS-Skills/skills/rss-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 rss-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-workflow .agents/skills/rss-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 "rss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-workflow into .agents/skills/rss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-workflow .cursor/skills/rss-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 "rss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-workflow into .cursor/skills/rss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 RSS-Skills/skills/rss-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 rss-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-workflow .gemini/skills/rss-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 "rss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-workflow into .gemini/skills/rss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-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 rss-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/RSS-Skills/skills/rss-workflow .github/skills/rss-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 "rss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-workflow into .github/skills/rss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-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 rss-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/RSS-Skills/skills/rss-workflow .opencode/skills/rss-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 "rss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-workflow into .opencode/skills/rss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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
rss-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 744 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 RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April…
- Works in 4 steps: https://roboticsconference.org/ — the… → The RSS Foundation calendar page… → The OpenReview venue namespace for a… → …
- Planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade
- SKILL.md covers Where the cycle stands right…, The robotics year, seen from RSS, Backward plan to a… and Conference-week execution (the…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rss Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April decisions, July conference week — and when placing RSS inside the year-round ICRA/IROS/RSS/CoRL robotics deadline calendar.
Its SKILL.md is about 1.5k 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 RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade
- The invited-rebuttal window
- Late-April decisions
- July conference week — and when placing RSS inside the year-round ICRA/IROS/RSS/CoRL robotics deadline calendar
Example prompts
- “/rss-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- https://roboticsconference.org/ — the banner rebinds to the new edition.
- The RSS Foundation calendar page (roboticsfoundation.org).
- The OpenReview venue namespace for a RSS/2027 group appearing.
- The CFP page for the new deadline cascade and any format change — the 8-page
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
Links to these hosts (documentation or services it may open):
roboticsconference.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
Rss Workflow loads about 1.5k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 744 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). 744 words, ~1,494 tokens.
Download SKILL.mdSave it as
.claude/skills/rss-workflow/SKILL.md (or your agent's skills folder).- name
- rss-workflow
- description
- Use when planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April decisions, July conference week — and when placing RSS inside the year-round ICRA/IROS/RSS/CoRL robotics deadline calendar.
RSS Workflow
Project-manage an RSS submission against its real calendar. Anchor every date to the current edition's pages; the 2026 dates below are a verified historical snapshot (source map rows 1-3, checked 2026-07-08), not a promise about 2027.
Where the cycle stands right now (as of 2026-07-08)
- RSS 2026 (22nd edition, Sydney: UTS + ICC) runs July 13-17, 2026 — conference week starts in days. The submission funnel (abstract Jan 23 → paper Jan 30 → supplement Feb 6 → invited rebuttal Apr 3 → decisions Apr 27, all AoE) is closed.
- Accepted authors are in final-presentation mode: talk, poster, travel, and artifact
release (
rss-camera-ready,rss-artifact-evaluation). - Everyone else is planning RSS 2027, whose site, dates, and deadlines were unposted at check time (待核实). The recent pattern — late-January deadline, July conference — is a planning hypothesis only.
The robotics year, seen from RSS
RSS shares its authors with three siblings, so choosing RSS is also choosing a slot in an annual rotation. Approximate recent geometry (verify each venue's live pages):
| Venue | Typical deadline | Typical event | What slipping past RSS costs |
|---|---|---|---|
| RSS | late January | July | Next comparable single-track slot is a full year away |
| IROS | ~March | ~October | Natural catch for a paper 6 weeks short of RSS-ready |
| CoRL | ~June | ~November | Right jury if the learning story dominates |
| ICRA | ~September | ~May/June | Broadest program; absorbs systems breadth |
The practical use: a project that misses the January bar honestly should aim at IROS or CoRL rather than submit thin — RSS's selectivity makes weak submissions expensive in reviewer goodwill.
Backward plan to a late-January deadline
| Weeks out | Milestone for a claim-plus-hardware paper |
|---|---|
| 12+ | Scientific claim fixed in one sentence; evidence plan sized to it |
| 10 | Hardware trial campaign running; failure attribution logged from day one |
| 6 | Ablations that isolate the mechanism complete |
| 4 | Full draft; supplement storyboard; internal red-team read |
| 2 | Anonymity sweep of PDF and media; OpenReview metadata entered |
| 1 | Abstract registered; buffer for robot downtime already spent |
| 0 | Paper in; supplement due one week later — do not design it that week, only pack it |
The one-week paper→supplement gap (2026: Jan 30 → Feb 6) is packing time, not filming time; footage shot after the deadline cannot support claims already frozen in the PDF.
Conference-week execution (the stage that is live right now)
For teams presenting at the current edition, the final week has its own checklist:
- Confirm the talk slot, format, and timing against the official program page; a single-track schedule has no parallel-session slack for overruns.
- Load footage locally; conference-venue networks are not a playback plan.
- Push the public artifact release live before the talk — the single-track
audience is the largest referral event the repository will ever get
(
rss-artifact-evaluation). - Prepare the poster to carry the evidence detail (trial counts, failure distribution) that the talk compresses away.
- Assign one author to note every hallway objection; those are free previews of the journal-extension reviews.
Show full SKILL.md (273 more words)Show less
RSS 2027 monitoring plan
Nothing about 2027 was posted at check time. Watch these, in this order, starting early autumn 2026:
- https://roboticsconference.org/ — the banner rebinds to the new edition.
- The RSS Foundation calendar page (roboticsfoundation.org).
- The OpenReview venue namespace for a
RSS/2027group appearing. - The CFP page for the new deadline cascade and any format change — the 8-page ceiling and the two-stage rebuttal are both cycle policies, not fixtures.
Stage-specific traps
- February-March silence: first reviews are not public-scheduled; do not plan team availability assuming a known release date (待核实 each cycle).
- The rebuttal is conditional: only papers above a first-round threshold are
invited to respond. Plan an April window in calendars without assuming it will be
used (
rss-author-response). - April 27 → July is short: visa lead times for the host country can exceed the decision-to-conference gap; start paperwork at submission time for likely-accept projects.
- No standing editors: the Program Chair and Area Chairs rotate per edition (2026 PC chair: Matei Ciocarlie, Columbia — verified 2026-07-08); never carry a name or a policy across cycles.
Ownership map for a multi-person campaign
Robotics submissions fail at handoffs; name owners early:
| Workstream | Single owner for |
|---|---|
| Claim custody | The one-sentence claim; vetoes scope drift in any section |
| Trial campaign | Protocol document, ledger integrity, daily campaign log |
| Media | Footage banking from every session; the supplement cut |
| Anonymity | The sweep across PDF, video, archive, and OpenReview fields |
| Deadline mechanics | AoE conversions, form fields, upload confirmations |
Footage banking deserves emphasis: clips must be captured during the campaign, because the supplement freezes one week after the paper and reshoots after the paper deadline cannot support frozen claims.
Output format
[Cycle position] planning 2027 / drafting / submitted / rebuttal window / accepted / conference week
[Next hard date] <date + source URL, or 待核实>
[Critical path] <three tasks gating the next stage>
[Fallback venue] IROS / CoRL / ICRA + trigger condition
[Calendar risks] <robot downtime / visa / footage / rebuttal availability>© 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 RSS-Skills/skills/rss-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Rss 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 |
|---|---|---|---|---|---|---|
| Rss Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 275k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Robots Meta Conflictthedaviddias/Front-End-Checklist | 74k | — | ~555 | Automated safety check: Pass | MIT | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Campaign Cleaner AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| Robot Framework Skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Robots Meta Conflict
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to sites that use both robots.txt disallow rules and meta robots noindex tags.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Campaign Cleaner Automation
ComposioHQ/awesome-claude-skills
Automate Campaign Cleaner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Robot Framework Skill
sickn33/agentic-awesome-skills
Generates Robot Framework tests in keyword-driven syntax with Python.
Ad Campaign Analyzer
sickn33/agentic-awesome-skills
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
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 Rss Workflow
What does Rss Workflow do?
A skill your agent uses when planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April…. Rss Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade, the invited-rebuttal window, late-April decisions, July conference week — and when placing RSS inside the year-round ICRA/IROS/RSS/CoRL robotics deadline calendar.
When should I use Rss Workflow?
Rss Workflow fits situations like: planning an RSS (Robotics: Science and Systems) campaign end to end — the late-January abstract/paper/supplement cascade; the invited-rebuttal window; late-April decisions; july conference week — and when placing RSS inside the year-round ICRA/IROS/RSS/CoRL robotics deadline calendar.
How do I install Rss Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-workflow -a claude-code`. Or copy the skill folder (RSS-Skills/skills/rss-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/rss-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Rss Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-workflow -a codex`. Or copy the skill folder (RSS-Skills/skills/rss-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/rss-workflow in your project. Codex loads it when a task matches its description.
Can I use Rss 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 rss-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/rss-workflow, .gemini/skills/rss-workflow, .github/skills/rss-workflow and .opencode/skills/rss-workflow in your project.
What does Rss Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Rss Workflow is instructions for the agent only.
Does Rss Workflow access the network?
SKILL.md names 1 domain. As links in the text: roboticsconference.org. This is read from the text; nothing was executed.
Is Rss 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 Rss Workflow use?
Rss 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 Rss Workflow use?
About 1.5k tokens (SKILL.md is roughly 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 Rss Workflow?
Skills that share tags, products or a category with Rss Workflow: Marketing Campaign (affaan-m/ECC, 275k stars), Robots Meta Conflict (thedaviddias/Front-End-Checklist, 74k stars), Campaign Analytics (alirezarezvani/claude-skills, 28k stars) and Campaign Cleaner Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rss 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.