Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
A skill your agent uses when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current…
Install Usenixsec Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-camera-ready --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/USENIX-Security-Skills/skills/usenixsec-camera-ready .claude/skills/usenixsec-camera-ready && 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 "usenixsec-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-camera-ready into .claude/skills/usenixsec-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-camera-ready", 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/USENIX-Security-Skills/skills/usenixsec-camera-readyType 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 usenixsec-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-camera-ready --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/USENIX-Security-Skills/skills/usenixsec-camera-ready .agents/skills/usenixsec-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "usenixsec-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-camera-ready into .agents/skills/usenixsec-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-camera-ready", 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 usenixsec-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-camera-ready --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/USENIX-Security-Skills/skills/usenixsec-camera-ready .cursor/skills/usenixsec-camera-ready && 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 "usenixsec-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-camera-ready into .cursor/skills/usenixsec-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-camera-ready", 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 USENIX-Security-Skills/skills/usenixsec-camera-ready--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 usenixsec-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-camera-ready --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/USENIX-Security-Skills/skills/usenixsec-camera-ready .gemini/skills/usenixsec-camera-ready && 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 "usenixsec-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-camera-ready into .gemini/skills/usenixsec-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-camera-ready", 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 usenixsec-camera-readyInstalls 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 usenixsec-camera-ready -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/USENIX-Security-Skills/skills/usenixsec-camera-ready .github/skills/usenixsec-camera-ready && 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 "usenixsec-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-camera-ready into .github/skills/usenixsec-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-camera-ready", 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 usenixsec-camera-ready -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 usenixsec-camera-ready --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/USENIX-Security-Skills/skills/usenixsec-camera-ready .opencode/skills/usenixsec-camera-ready && 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 "usenixsec-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-camera-ready into .opencode/skills/usenixsec-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-camera-ready", 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
usenixsec-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 577 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current…
- Preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing
- SKILL.md covers What is actually conditional, De-anonymization done in the…, Mechanical pass before upload and Publication model: open…, plus 3 more sections
- Calls pdftotext
- Keeping the Ethical Considerations and Open Science appendices current
What it does
Usenixsec Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current, clearing the mandatory Phase-1 artifact availability check before finals are due, and meeting USENIX's open-access publication and presentation obligations.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Reproducible research. 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
- Preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing
- Keeping the Ethical Considerations and Open Science appendices current
- Clearing the mandatory Phase-1 artifact availability check before finals are due
- Meeting USENIXs open-access publication and presentation obligations
Example prompts
- “/usenixsec-camera-ready”
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
Shell commands in SKILL.md call:
pdftotext
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
Usenixsec Camera Ready loads about 1.3k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 577 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). 577 words, ~1,341 tokens.
Download SKILL.mdSave it as
.claude/skills/usenixsec-camera-ready/SKILL.md (or your agent's skills folder).- name
- usenixsec-camera-ready
- description
- Use when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current, clearing the mandatory Phase-1 artifact availability check before finals are due, and meeting USENIX's open-access publication and presentation obligations.
USENIX Security Camera-Ready
Acceptance at USENIX Security starts a short, condition-laden runway: in the '26 cycles, final papers were due about six weeks after notification (Cycle 1: notified Dec 4, 2025, finals Jan 15, 2026; Cycle 2: notified May 14, 2026, finals Jun 11, 2026), and during that same window the mandatory artifact-availability check had to pass. The camera-ready is therefore not a formatting chore — part of the acceptance itself is still pending.
What is actually conditional
Under the '26 Open Science policy, acceptance is conditional on the artifact evaluation committee verifying, before finals are due, that the artifacts named in the paper's Open Science appendix are genuinely available — or that the appendix carries a justified explanation for withholding them. Plan the runway backwards from that:
| Week after notification | Camera-ready lane | Artifact lane |
|---|---|---|
| 1 | Ingest decision + shepherd requests | Move artifacts from anonymous mirror to permanent home |
| 2–3 | Apply required edits; shepherd sign-off | Submit availability materials; respond to AE contact |
| 4 | De-anonymize; final template pass | Availability verified (Phase-1 complete) |
| 5–6 | Upload finals + metadata; presenter forms | Decide on optional Phase-2 (Functional / Reproduced) |
De-anonymization done in the right order
Restore identity everywhere it was stripped, and keep the pieces consistent:
- Author block and affiliations, matching the HotCRP metadata exactly — the proceedings entry is generated from what USENIX has on file.
- Acknowledgements and funding, which double-blind rules forced out of the submission.
- Self-citations rewritten back to natural first-person where that reads better.
- Artifact URLs: replace every anonymized mirror with the permanent, named location. A camera-ready pointing at a dead anonymous repository is the classic post-acceptance defect at this venue, because reviewers checked the anonymous one and nobody rechecks the swap.
The two named appendices — "Ethical Considerations" and "Open Science" — remain in the final paper, updated: disclosure timelines that were "in progress" at submission should state their current status (vendor response, CVE assignment, patch release).
Mechanical pass before upload
# Final-paper checks
pdftotext final.pdf - | grep -nEi 'anonym|under submission|double.blind' | head
pdftotext final.pdf - | grep -noE 'https?://[^ ]+' | sort -u > urls.txt
while read -r n url; do curl -sIL --max-time 10 "${url#*:}" -o /dev/null \
-w "%{http_code} ${url}\n"; done < <(tr ':' ' ' < urls.txt | head -40)
pdffonts final.pdf | awk 'NR>2 && $4!="yes"' # any non-embedded font lines = fixFollow the current "Instructions for Presenters and Authors of Accepted Papers" page for the cycle — title formatting, copyright/consent forms, and slide or poster requirements are set there, not in the CFP.
Show full SKILL.md (232 more words)Show less
Publication model: open access, no author fee
USENIX publishes Security proceedings open access; papers (and later, talk recordings) are freely available on usenix.org. There is no article charge. The author-side obligations run through the conference instead: presentation at the symposium in Baltimore (Aug 12–14, 2026 for the '26 program) per the current presenter instructions. Registration mechanics, speaker-registration rules, and any remote-presentation allowance are per-year decisions — 待核实 against the instructions page for your cycle before booking anything.
Cycle-1 authors get a bonus decision: finals are locked ~7 months before the symposium, so plan whether to post an extended version (arXiv or tech report) in the gap, and make the proceedings version state clearly which version is canonical.
Badge and visibility follow-through
- Optional Phase-2 artifact evaluation (Functional / Results Reproduced badges) happens after finals are due — the camera-ready must not overstate badge status it does not yet hold.
- Distinguished Paper Awards and the Internet Defense Prize are selected from the final program; nothing to do except have the final PDF be the strongest version.
- Add the paper's usenix.org proceedings URL to the artifact README once live, so artifact users land on the canonical version.
Reverify each cycle
- Final-paper deadline for your cycle and the shepherd-approval interaction.
- Whether Phase-1 availability verification remains a condition of acceptance.
- Presenter/registration requirements and any remote option (待核实 for '27).
- Formatting and form requirements on the current instructions page.
Output format
[Runway] notification → finals dates; days remaining
[Conditions open] shepherd sign-off / Phase-1 availability / forms
[De-anonymization] identity restored + artifact URLs swapped and re-tested
[Appendices] Ethical Considerations + Open Science updated to current status
[Presentation] presenter, registration status, travel constraints© 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 USENIX-Security-Skills/skills/usenixsec-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Usenixsec Camera Ready 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 |
|---|---|---|---|---|---|---|
| Usenixsec Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Bactopia Toolbactopia/bactopia | 522 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
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 Usenixsec Camera Ready
What does Usenixsec Camera Ready do?
A skill your agent uses when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current…. Usenixsec Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current, clearing the mandatory Phase-1 artifact availability check before finals are due, and meeting USENIX's open-access publication and presentation obligations.
When should I use Usenixsec Camera Ready?
Usenixsec Camera Ready fits situations like: preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing; keeping the Ethical Considerations and Open Science appendices current; clearing the mandatory Phase-1 artifact availability check before finals are due; meeting USENIXs open-access publication and presentation obligations.
How do I install Usenixsec Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-camera-ready -a claude-code`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/usenixsec-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Usenixsec Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-camera-ready -a codex`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/usenixsec-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Usenixsec Camera Ready 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 usenixsec-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/usenixsec-camera-ready, .gemini/skills/usenixsec-camera-ready, .github/skills/usenixsec-camera-ready and .opencode/skills/usenixsec-camera-ready in your project.
What does Usenixsec Camera Ready need to run?
Going by SKILL.md and its folder, Usenixsec Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Usenixsec Camera Ready 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 Usenixsec Camera Ready 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 Usenixsec Camera Ready use?
Usenixsec Camera Ready 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 Usenixsec Camera Ready use?
About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Usenixsec Camera Ready?
Skills that share tags, products or a category with Usenixsec Camera Ready: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usenixsec Camera Ready?
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.