Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section…
MITAuto-check passed
Install Ieeesp Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-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/IEEE-SP-Skills/skills/ieeesp-camera-ready .claude/skills/ieeesp-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 "ieeesp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-camera-ready into .claude/skills/ieeesp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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/IEEE-SP-Skills/skills/ieeesp-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 ieeesp-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-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/IEEE-SP-Skills/skills/ieeesp-camera-ready .agents/skills/ieeesp-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 "ieeesp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-camera-ready into .agents/skills/ieeesp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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 ieeesp-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-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/IEEE-SP-Skills/skills/ieeesp-camera-ready .cursor/skills/ieeesp-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 "ieeesp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-camera-ready into .cursor/skills/ieeesp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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 IEEE-SP-Skills/skills/ieeesp-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 ieeesp-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-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/IEEE-SP-Skills/skills/ieeesp-camera-ready .gemini/skills/ieeesp-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 "ieeesp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-camera-ready into .gemini/skills/ieeesp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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 ieeesp-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 ieeesp-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/IEEE-SP-Skills/skills/ieeesp-camera-ready .github/skills/ieeesp-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 "ieeesp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-camera-ready into .github/skills/ieeesp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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 ieeesp-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 ieeesp-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/IEEE-SP-Skills/skills/ieeesp-camera-ready .opencode/skills/ieeesp-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 "ieeesp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-camera-ready into .opencode/skills/ieeesp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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
ieeesp-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 554 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section…
- Works in 5 steps: Convert the draft meta-review into a… → For each concern, agree internally on:… → Ask the shepherd early about any concern… → …
- Converting an IEEE S&P (Oakland) acceptance into a final paper
- SKILL.md covers Working the shepherding loop, The ethics section is added…, De-anonymization with… and IEEE mechanics, plus 3 more sections
- Calls pdftotext
What it does
Ieeesp Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section, de-anonymizing and restoring disclosure specifics, IEEE compsoc and Xplore requirements, and coordinating artifact submission.
Its SKILL.md is about 1.2k 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
- Converting an IEEE S&P (Oakland) acceptance into a final paper
- Including working the shepherd against the draft meta-reviews concern list
- Adding the ethics section
- De-anonymizing and restoring disclosure specifics
Example prompts
- “/ieeesp-camera-ready”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Convert the draft meta-review into a numbered concern ledger on day one.
- For each concern, agree internally on: the change, its location, and the
- Ask the shepherd early about any concern you believe is out of scope or
- Submit the revision with a concern → change → location map; make the
- Nothing in the shepherding loop authorizes new claims: the accepted
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
Ieeesp Camera Ready loads about 1.2k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 554 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). 554 words, ~1,240 tokens.
Download SKILL.mdSave it as
.claude/skills/ieeesp-camera-ready/SKILL.md (or your agent's skills folder).- name
- ieeesp-camera-ready
- description
- Use when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section, de-anonymizing and restoring disclosure specifics, IEEE compsoc and Xplore requirements, and coordinating artifact submission.
IEEE S&P Camera-Ready
Use this after an Accept decision. S&P's camera-ready is not a formatting pass: acceptance arrives with a draft meta-review listing remaining concerns and a shepherd who strikes each concern only when the revision resolves it (2027 CFP, checked 2026-07-08). The camera-ready is the last reviewed artifact of the cycle.
Working the shepherding loop
- Convert the draft meta-review into a numbered concern ledger on day one.
- For each concern, agree internally on: the change, its location, and the one-line evidence the shepherd can check.
- Ask the shepherd early about any concern you believe is out of scope or wrong — negotiation happens at the start, not at the deadline.
- Submit the revision with a concern → change → location map; make the strike-through decision mechanical for the shepherd.
- Nothing in the shepherding loop authorizes new claims: the accepted contribution is the contribution.
| Shepherd asks for | Right-sized response |
|---|---|
| Tone down claim X | Rewrite the claim to the evaluated boundary; show old/new text |
| Add limitation discussion | A titled paragraph, referenced from the intro |
| Clarify threat model edge | Amend §2 with the explicit assumption |
| Missing related system | Cite + one-line technical delta, not a new section |
| Ethics wording | Coordinate with the ethics section below |
The ethics section is added now — and does not count
Accepted papers add a dedicated, well-marked ethics section without it counting against page limits (2026 CFP wording, checked 2026-07-08). Write it as a record, not a disclaimer:
- What could cause harm, to whom, and what you did about it.
- Responsible disclosure: who was notified, when, what they responded, current fix status — with the real names and dates now that anonymity has lifted.
- IRB approval or waiver, by institution and protocol ID, where applicable.
- Data handling: what PII existed, minimization, retention, who had access.
De-anonymization with security-specific restorations
Beyond names, affiliations, acknowledgments, and first-person citations, restore what anonymity forced you to blur:
- Vendor names and CVE identifiers in the disclosure narrative.
- Artifact URLs (repository, DOI deposit) replacing anonymized placeholders.
- Funding and infrastructure acknowledgments (measurement platforms often contractually require attribution).
# Residue sweep after de-anonymization
pdftotext final.pdf - | grep -inE 'anonym|redacted|omitted for (review|anonymity)|Vendor [A-Z]\b'
pdfinfo final.pdf | grep -iE 'title|author' # metadata now correct, not blank
grep -rn 'REPLACE-AFTER-ACCEPT' . || trueShow full SKILL.md (212 more words)Show less
IEEE mechanics
The proceedings are published by IEEE (Xplore); the compsoc template remains mandatory. Verify on the current year's author page — all 待核实 at this pack's check date for 2027: the exact camera-ready deadline, the final page allowance and any purchasable extra pages, the IEEE copyright/eCF step, PDF-compliance checking, and whether registration or in-person presentation by an author is required for publication. Reported by aggregators (unverified officially): recent S&P papers appear open access in the Computer Society Digital Library — do not promise open access until confirmed.
Sequence to the deadline
- Concern ledger agreed with shepherd (week 1).
- Content revisions + ethics section drafted (weeks 1–2).
- De-anonymization and restoration sweep.
- Artifact evaluation submission if opting in — its schedule runs off the
acceptance date, in parallel (
ieeesp-artifact-evaluation). - Final compsoc compile, IEEE PDF check, copyright form, upload.
- Re-download and verify the archived PDF; Xplore keeps what you upload.
Common failures at this stage
- Treating the meta-review as advisory — an unresolved concern is a shepherd-level blocker, not a style note.
- An ethics section written as legal boilerplate; reviewers approved a specific record and expect it stated.
- Disclosure narrative updated in the ethics section but not in the introduction, leaving contradictory timelines.
- Missing the artifact-evaluation registration window while polishing prose.
Output format
[Concern ledger] <n> total: resolved <n> · negotiating <n> · open <n>
[Ethics section] disclosure record ✓/✗ · IRB/waiver ✓/✗ · data handling ✓/✗
[De-anon sweep] names/CVEs/URLs restored ✓/✗ · residue found: <items>
[IEEE mechanics 待核实] deadline / page allowance / copyright / attendance
[Artifact track] opted in? deadline <date>; badge targets <list>© 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 IEEE-SP-Skills/skills/ieeesp-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ieeesp 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 |
|---|---|---|---|---|---|---|
| Ieeesp Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| QA Acceptancepaperclipai/paperclip | 100k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Word to Markdown Convertergithub/awesome-copilot | 40k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
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 Ieeesp Camera Ready
What does Ieeesp Camera Ready do?
A skill your agent uses when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section…. Ieeesp Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section, de-anonymizing and restoring disclosure specifics, IEEE compsoc and Xplore requirements, and coordinating artifact submission.
When should I use Ieeesp Camera Ready?
Ieeesp Camera Ready fits situations like: converting an IEEE S&P (Oakland) acceptance into a final paper; including working the shepherd against the draft meta-reviews concern list; adding the ethics section; de-anonymizing and restoring disclosure specifics.
How do I install Ieeesp Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-camera-ready -a claude-code`. Or copy the skill folder (IEEE-SP-Skills/skills/ieeesp-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ieeesp-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Ieeesp Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-camera-ready -a codex`. Or copy the skill folder (IEEE-SP-Skills/skills/ieeesp-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ieeesp-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Ieeesp 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 ieeesp-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/ieeesp-camera-ready, .gemini/skills/ieeesp-camera-ready, .github/skills/ieeesp-camera-ready and .opencode/skills/ieeesp-camera-ready in your project.
What does Ieeesp Camera Ready need to run?
Going by SKILL.md and its folder, Ieeesp Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Ieeesp 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 Ieeesp 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 Ieeesp Camera Ready use?
Ieeesp 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 Ieeesp Camera Ready use?
About 1.2k tokens (SKILL.md is roughly 5k 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 Ieeesp Camera Ready?
Skills that share tags, products or a category with Ieeesp Camera Ready: Convert (remotion-dev/remotion, 63k stars), QA Acceptance (paperclipai/paperclip, 100k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ieeesp 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.