Telemetry Standards
supabase/supabase
PostHog event tracking standards for Supabase Studio. An agent skill from supabase/supabase.
Agent skill
Amann Evidence Standards
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning…
MITAuto-check passed
Install Amann Evidence Standards
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-evidence-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-evidence-standards --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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards .claude/skills/amann-evidence-standards && 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 "amann-evidence-standards" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards into .claude/skills/amann-evidence-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-evidence-standards", 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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standardsType 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 amann-evidence-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-evidence-standards --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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards .agents/skills/amann-evidence-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "amann-evidence-standards" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards into .agents/skills/amann-evidence-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-evidence-standards", 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 amann-evidence-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-evidence-standards --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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards .cursor/skills/amann-evidence-standards && 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 "amann-evidence-standards" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards into .cursor/skills/amann-evidence-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-evidence-standards", 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 Academy-of-Management-Annals-Skills/skills/amann-evidence-standards--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 amann-evidence-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-evidence-standards --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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards .gemini/skills/amann-evidence-standards && 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 "amann-evidence-standards" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards into .gemini/skills/amann-evidence-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-evidence-standards", 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 amann-evidence-standardsInstalls 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 amann-evidence-standards -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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards .github/skills/amann-evidence-standards && 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 "amann-evidence-standards" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards into .github/skills/amann-evidence-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-evidence-standards", 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 amann-evidence-standards -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 amann-evidence-standards --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/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards .opencode/skills/amann-evidence-standards && 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 "amann-evidence-standards" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-evidence-standards into .opencode/skills/amann-evidence-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-evidence-standards", 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
amann-evidence-standards- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 763 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning…
- Steelmanning rival schools
- SKILL.md covers When to trigger, At Annals you are the field's…, Completeness vs. selectivity:… and Weighing conflicting evidence…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Handling the authors own work even-handedly
What it does
Amann Evidence Standards is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning rival schools, and handling the author's own work even-handedly. Audits evidence quality and fairness; it does not design the framework (amann-organizing-framework) or build exhibits (amann-tables-figures).
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Steelmanning rival schools
- Handling the authors own work even-handedly
Example prompts
- “/amann-evidence-standards”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Amann Evidence Standards loads about 1.7k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 763 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). 763 words, ~1,706 tokens.
Download SKILL.mdSave it as
.claude/skills/amann-evidence-standards/SKILL.md (or your agent's skills folder).- name
- amann-evidence-standards
- description
- Use when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning rival schools, and handling the author's own work even-handedly. Audits evidence quality and fairness; it does not design the framework (amann-organizing-framework) or build exhibits (amann-tables-figures).
Evidence Standards — Appraisal & Balance (amann-evidence-standards)
When to trigger
- The framework is set and you are filling cells with the literature
- The field has rival schools, a live controversy, or conflicting empirical results
- You must decide whether to cite everything or curate, and how to weigh disagreeing studies
- You are a contributor to this literature and worry the review tilts toward your own work
At Annals you are the field's reviewer-of-record
An Annals review carries no estimates of its own — but it is not therefore neutral. The "attitude" is disciplined critical appraisal: you judge how good the cumulative evidence is, reconcile conflicts by credibility, and state where the field's confidence is and is not warranted. This is the review-craft replacement for primary-research robustness checks: you are appraising other people's designs, not defending your own.
Completeness vs. selectivity: the Annals contract
A review must be comprehensive in coverage yet selective in emphasis — long (~50 pages) but not an inventory. Resolve the tension by tiering the corpus:
| Tier | Treatment |
|---|---|
| Foundational / field-defining | discussed in text — what it established and its limits |
| Important contributions | grouped and weighed within the framework's cells; cited with their finding |
| Confirmatory / incremental | cited in clusters ("see also …") to show coverage without bloating prose |
| Tangential | cited only where it bears on a specific claim |
Comprehensiveness is proven by the citation set (the saturation log from amann-literature-synthesis); selectivity is exercised in the prose. Equal-length summaries of every paper abdicate the editorial judgment that is the review's value.
Weighing conflicting evidence (not vote-counting)
Management findings conflict constantly. Reconcile them by why they differ, never by tally:
- Weigh by credibility. Design strength (causal vs. correlational), sample, measurement validity, replication, and publication-bias risk — not "9 studies positive, 4 negative."
- Separate by construct and context. Studies often disagree because they measure different constructs or run in different settings; surface that rather than forcing a false consensus.
- Flag the cumulative-evidence quality. State plainly where the evidence is strong, mixed, or thin — and where apparent consensus rests on a few non-independent studies.
- Name what would settle it. For a live debate, specify the study design that would resolve it (this seeds the agenda).
When appraisal needs an actual number (execution bridge)
Occasionally a credibility judgment cannot be settled by reading alone: the review's account of a controversy hinges on whether a staggered-adoption TWFE estimate survives modern corrections, or an apparent consensus may melt once publication bias is priced in. When a load-bearing magnitude comes with a replication package, audit it rather than adjudicate by prose — the shared playbook execution-with-mcp maps each design family to callable StatsPAI / Stata MCP tools (bacon_decomposition to expose bad-comparison weighting, callaway_santanna to re-estimate, honest_did_from_result for pre-trend fragility). Any number produced this way must come from an actual run and be labelled as the review's own re-analysis. This is the exception, not the Annals default: most appraisal here stays qualitative.
Show full SKILL.md (288 more words)Show less
Fairness across schools and the self-citation trap
Annals is the review-of-the-field: its account of a debate becomes the field's shared reference, and the surveyed authors often referee the review. Balance is therefore both ethical and strategic.
- Steelman every camp. State each school's strongest case in terms its proponents would accept before critiquing it. Refute positions at their best.
- Attribute ideas to originators, not popularizers — a recurring referee complaint.
- Audit self-citation. Your own work is cited at the tier its importance to the field warrants — no more. Rivals get their strongest statement. A reader who does not know who wrote the review cannot tell from the emphasis.
- Label your read as your read. Where you take a provocative position (the "attitude"), mark it as the author's judgment, not as settled consensus.
Checklist
- Corpus tiered (foundational / important / confirmatory / tangential); prose emphasis matches tier
- Comprehensiveness provable from the citation set + saturation log
- Conflicting findings reconciled by credibility, construct, and context — not vote-counting
- Cumulative-evidence quality stated (strong / mixed / thin) per claim
- Every rival school stated at its strongest before critique (steelman)
- Idea attribution traces to originators
- Self-citation audited: own work at field-warranted tier; emphasis identity-blind
- Provocative positions labelled as the author's read; what-would-settle-it named for live debates
- No important author/school an informed referee could say was slighted or omitted
Anti-patterns
- Comprehensiveness theatre: equal-length summaries of every paper (no editorial judgment)
- Vote-counting conflicting results instead of weighing credibility, construct, and context
- Treating all findings as equally credible regardless of design quality
- Strawmanning the camp the author disagrees with (the referee may be that camp)
- A review that doubles as the author's CV (the most-punished balance failure)
- Declaring a live controversy "resolved" by assertion rather than by laying out the evidentiary state
Output format
【Tiering】corpus split foundational/important/confirmatory/tangential? Y/N
【Comprehensiveness evidence】saturation log + citation set support "nothing important missing"? Y/N
【Conflict handling】reconciled by credibility + construct + context (not vote-count)? Y/N
【Evidence quality】strong/mixed/thin stated per claim? Y/N
【Steelman】each rival school stated at its strongest? Y/N
【Self-citation audit】own work at warranted tier; emphasis identity-blind? Y/N
【Attitude labelled】provocative reads marked as author's judgment? Y/N
【Next skill】→ amann-tables-figures (who-found-what tables + framework figure)© 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 Academy-of-Management-Annals-Skills/skills/amann-evidence-standards of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Amann Evidence Standards 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 |
|---|---|---|---|---|---|---|
| Amann Evidence Standards this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Telemetry Standardssupabase/supabase | 111k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Claude Academy Guideanthropics/skills | 180k | 3 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Cpp Coding Standardsaffaan-m/ECC | 277k | 4 repos | ~5.6k | Automated safety check: Pass | MIT | |
| Java Coding Standardsaffaan-m/ECC | 277k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Agent Load Balancerruvnet/ruflo | 74k | 2 repos | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Claude Academy Guide
anthropics/skills
Adds a matching Claude Academy course, tutorial or use case to the end of an answer about learning to use Claude, but only when the match is strong.
Cpp Coding Standards
affaan-m/ECC
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io).
Java Coding Standards
affaan-m/ECC
Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout.
Agent Load Balancer
ruvnet/ruflo
Agent skill for load-balancer - invoke with $agent-load-balancer
Coding Standards
affaan-m/ECC
适用于TypeScript、JavaScript、React和Node.js开发的通用编码标准、最佳实践和模式. An agent skill from affaan-m/ECC.
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 Amann Evidence Standards
What does Amann Evidence Standards do?
A skill your agent uses when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning…. Amann Evidence Standards is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning rival schools, and handling the author's own work even-handedly.
When should I use Amann Evidence Standards?
Amann Evidence Standards fits situations like: steelmanning rival schools; handling the authors own work even-handedly.
How do I install Amann Evidence Standards in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-evidence-standards -a claude-code`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-evidence-standards in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/amann-evidence-standards in your project. Claude Code loads it when a task matches its description.
How do I install Amann Evidence Standards in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-evidence-standards -a codex`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-evidence-standards in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/amann-evidence-standards in your project. Codex loads it when a task matches its description.
Can I use Amann Evidence Standards 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 amann-evidence-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amann-evidence-standards, .gemini/skills/amann-evidence-standards, .github/skills/amann-evidence-standards and .opencode/skills/amann-evidence-standards in your project.
What does Amann Evidence Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Amann Evidence Standards is instructions for the agent only.
Does Amann Evidence Standards 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 Amann Evidence Standards 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 Amann Evidence Standards use?
Amann Evidence Standards 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 Amann Evidence Standards use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Amann Evidence Standards?
Skills that share tags, products or a category with Amann Evidence Standards: Telemetry Standards (supabase/supabase, 111k stars), Claude Academy Guide (anthropics/skills, 180k stars), Cpp Coding Standards (affaan-m/ECC, 277k stars) and Java Coding Standards (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Amann Evidence Standards?
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.