Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
A skill your agent uses when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the…
Install Isca Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-submission --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/ISCA-Skills/skills/isca-submission .claude/skills/isca-submission && 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 "isca-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-submission into .claude/skills/isca-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-submission", 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/ISCA-Skills/skills/isca-submissionType 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 isca-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-submission --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/ISCA-Skills/skills/isca-submission .agents/skills/isca-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "isca-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-submission into .agents/skills/isca-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-submission", 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 isca-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-submission --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/ISCA-Skills/skills/isca-submission .cursor/skills/isca-submission && 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 "isca-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-submission into .cursor/skills/isca-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-submission", 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 ISCA-Skills/skills/isca-submission--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 isca-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-submission --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/ISCA-Skills/skills/isca-submission .gemini/skills/isca-submission && 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 "isca-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-submission into .gemini/skills/isca-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-submission", 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 isca-submissionInstalls 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 isca-submission -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/ISCA-Skills/skills/isca-submission .github/skills/isca-submission && 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 "isca-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-submission into .github/skills/isca-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-submission", 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 isca-submission -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 isca-submission --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/ISCA-Skills/skills/isca-submission .opencode/skills/isca-submission && 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 "isca-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-submission into .opencode/skills/isca-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-submission", 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
isca-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the…
- Works in 3 steps: No author names on any submitted… → PDF metadata must not give away authors.… → Artifact links must be fully anonymized…
- Running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart
- SKILL.md covers The two-step gate, Hard-format checklist, 2026…, Double-blind sweep — the three… and The HotCRP form is a second…, plus 3 more sections
- Calls pdftotext
What it does
Isca Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized artifact links, and HotCRP form completion before AoE.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering PDF. 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
- Running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart
- The 11-page text limit with unlimited references
- The template check
- The double-blind sweep including PDF metadata and anonymized artifact links
Example prompts
- “/isca-submission”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- No author names on any submitted document — they exist only in the HotCRP
- PDF metadata must not give away authors. LaTeX toolchains embed usernames
- Artifact links must be fully anonymized (an anonymized repository service,
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
Isca Submission loads about 1.6k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 704 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). 704 words, ~1,600 tokens.
Download SKILL.mdSave it as
.claude/skills/isca-submission/SKILL.md (or your agent's skills folder).- name
- isca-submission
- description
- Use when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized artifact links, and HotCRP form completion before AoE.
ISCA Submission
This audit assumes the deadline is days away and the PDF nearly final. Every hard
rule cited below is the verified ISCA 2026 record (checked 2026-07-08); the 2027
guidelines were not yet posted at check time, so confirm each line against the
live iscaconf.org pages before trusting it (待核实).
The two-step gate
ISCA 2026 collected abstracts November 10 and full papers November 17, 2025 — a seven-day gap with different stakes at each step:
- The abstract step registers title, abstract text, authors, topics, and conflicts in HotCRP. It is what reviewer assignment works from. Submitting a throwaway abstract and rewriting it at the paper step defeats its purpose and can misroute the paper to the wrong reviewers.
- The paper step uploads the reviewed PDF. New submissions cannot appear at this step — no abstract, no paper.
- Industry-track submissions ran on their own later pair (December 5 / December 12, 2025); confirm which track's dates govern you.
Treat the abstract deadline as the real deadline for decisions (title, claim, topic areas, author list, conflicts) and the paper deadline as the real deadline for evidence and prose.
Hard-format checklist, 2026 rules
| Item | 2026 rule | Check |
|---|---|---|
| Body length | ≤ 11 pages of single-spaced two-column text, references NOT counted | Count pages up to the bibliography start |
| References | Any number of pages | Never cut citations for space |
| Template | ISCA 2026 IEEE LaTeX template suggested for LaTeX users | Build from the official class, unmodified |
| File | Printable PDF | Fonts embedded; prints without errors |
| Portal | HotCRP (isca2026.hotcrp.com pattern) | Account, form, and upload confirmed — not just saved |
Page-limit recovery should come from cutting content, not squeezing geometry: committees can and do check formatting mechanically, and a paper that reads as crammed invites the question of what a revision could even absorb.
Double-blind sweep — the three 2026-specific rules
The verified guidelines make three demands that trip authors coming from other venues:
- No author names on any submitted document — they exist only in the HotCRP form fields.
- PDF metadata must not give away authors. LaTeX toolchains embed usernames and file paths; scrub and verify.
- Artifact links must be fully anonymized (an anonymized repository service,
not your lab's GitHub) — while references must not be anonymized or
omitted. Blind the voice and the links, never the bibliography (details in
isca-related-work).
# Mechanical anonymity + format pass on the final PDF
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # metadata fields
pdftotext paper.pdf - | grep -nEi \
'github\.com/(?!anonymous)|gitlab|acknowledg|funded by|grant' | head
pdftotext -f 1 -l 1 paper.pdf - | head -5 # no names under title
pdffonts paper.pdf | awk '$5=="no"' # non-embedded fonts
# body-page count: note the page where references begin, compare to 11
pdftotext paper.pdf - | grep -n 'REFERENCES\|References' | head -1Also sweep content-level identity: named internal clusters, institution-specific trace names, acknowledgment stubs, and "as we showed in [7]" phrasing.
Show full SKILL.md (307 more words)Show less
The HotCRP form is a second document
Draft every field at the abstract step and re-verify at the paper step:
- Title/abstract — must match the PDF exactly; mismatches confuse bidding and look careless at the PC meeting.
- Topics — choose for the reviewer pool you want; a memory-hierarchy paper tagged only "accelerators" gets accelerator reviewers.
- Authors and conflicts — complete conflict declaration for every author: advisors, recent coauthors, institutional conflicts. Missing conflicts discovered later are an integrity problem, not a typo. Over-declaring to dodge specific reviewers is likewise detectable and sanctionable.
- Declared coverage — any dual-submission, prior-workshop, or extended-abstract history the current cycle's form asks about, answered literally.
Final-72-hours run order
- Freeze experiments; tag the repo at the commit producing every number in the
PDF (
isca-reproducibility). - Full read-through by a coauthor against the self-check lists in
isca-writing-styleandisca-experiments. - Run the mechanical pass above on the final build, not a near-final one — metadata regenerates on every compile.
- Complete every HotCRP field; upload; confirm status shows submitted.
- Download the PDF back from HotCRP and open it cold on another machine. The uploaded artifact, not your local file, is the submission.
- Calendar the rebuttal/revision window now (mid-February to early March in the
2026 cycle) so the team is staffed when reviews land (
isca-author-response).
Common last-week failures, ranked by frequency
- Abstract step missed entirely — authors tracking only the paper date.
- Metadata leak from a coauthor's build environment (fixed by one designated build machine).
- Un-anonymized artifact URL in a footnote added late.
- Topics chosen in five seconds, misrouting review assignment.
- HotCRP "draft saved" mistaken for "submitted" at 11:58 PM AoE.
Audit output template
Fill this in and circulate to all coauthors before each of the two deadlines:
[Gate] abstract step / paper step [Deadline] <date, AoE-converted>
[Format] body pages: __ /11 · refs pages: __ (uncounted) · template: official
[Blinding] names=form-only · metadata=clean · artifact-links=anonymized ·
references=INTACT
[HotCRP] title/abstract match PDF · topics deliberate · conflicts complete ·
status=SUBMITTED
[Freeze] repo tagged at figure-producing commit · env image stored
[Open risks] <anything unresolved, with owner and hour-of-day plan>Every rule above is one edition's snapshot from
../../resources/official-source-map.md. If the live 2027 pages disagree with
this file, the live pages win.
© 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 ISCA-Skills/skills/isca-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Isca Submission 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 |
|---|---|---|---|---|---|---|
| Isca Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9.2k | — | ~19k | Automated safety check: Pass | Apache-2.0 | |
| Harness Book Best Practicewquguru/harness-books | 3.2k | — | ~4.1k | Automated safety check: Pass | None | |
| Bookforge Korean Ebook PDF Makergongnyang/bookforge | 316 | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
Harness Book Best Practice
wquguru/harness-books
Best practices for working on the Harness books repo. An agent skill from wquguru/harness-books.
Bookforge Korean Ebook PDF Maker
gongnyang/bookforge
Produces book-style Korean ebook PDFs from a topic or finished manuscript, with six design styles, real book parts and quality-check gates before output.
- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
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 Isca Submission
What does Isca Submission do?
A skill your agent uses when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the…. Isca Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized artifact links, and HotCRP form completion before AoE.
When should I use Isca Submission?
Isca Submission fits situations like: running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart; the 11-page text limit with unlimited references; the template check; the double-blind sweep including PDF metadata and anonymized artifact links.
How do I install Isca Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-submission -a claude-code`. Or copy the skill folder (ISCA-Skills/skills/isca-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/isca-submission in your project. Claude Code loads it when a task matches its description.
How do I install Isca Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-submission -a codex`. Or copy the skill folder (ISCA-Skills/skills/isca-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/isca-submission in your project. Codex loads it when a task matches its description.
Can I use Isca Submission 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 isca-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/isca-submission, .gemini/skills/isca-submission, .github/skills/isca-submission and .opencode/skills/isca-submission in your project.
What does Isca Submission need to run?
Going by SKILL.md and its folder, Isca Submission needs the command-line tools its instructions call (pdftotext).
Does Isca Submission 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 Isca Submission 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 Isca Submission use?
Isca Submission 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 Isca Submission use?
About 1.6k tokens (SKILL.md is roughly 6.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 Isca Submission?
Skills that share tags, products or a category with Isca Submission: Markitdown (ImCa0/just-laws, 781 stars), Gzh Design (isjiamu/gzh-design-skill, 4k stars), GenOffice Document CLI (genspark-ai/genoffice, 9.2k stars) and Harness Book Best Practice (wquguru/harness-books, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Isca Submission?
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.