Writing Livekit Scenarios
livekit-examples/agent-starter-python
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.
A skill your agent uses when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters…
Install Lang Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-review-process --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/Language-Linguistic-Society-Skills/skills/lang-review-process .claude/skills/lang-review-process && 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 "lang-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-review-process into .claude/skills/lang-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-review-process", 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/Language-Linguistic-Society-Skills/skills/lang-review-processType 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 lang-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-review-process --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/Language-Linguistic-Society-Skills/skills/lang-review-process .agents/skills/lang-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lang-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-review-process into .agents/skills/lang-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-review-process", 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 lang-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-review-process --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/Language-Linguistic-Society-Skills/skills/lang-review-process .cursor/skills/lang-review-process && 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 "lang-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-review-process into .cursor/skills/lang-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-review-process", 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 Language-Linguistic-Society-Skills/skills/lang-review-process--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 lang-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-review-process --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/Language-Linguistic-Society-Skills/skills/lang-review-process .gemini/skills/lang-review-process && 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 "lang-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-review-process into .gemini/skills/lang-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-review-process", 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 lang-review-processInstalls 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 lang-review-process -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/Language-Linguistic-Society-Skills/skills/lang-review-process .github/skills/lang-review-process && 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 "lang-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-review-process into .github/skills/lang-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-review-process", 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 lang-review-process -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 lang-review-process --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/Language-Linguistic-Society-Skills/skills/lang-review-process .opencode/skills/lang-review-process && 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 "lang-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-review-process into .opencode/skills/lang-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-review-process", 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
lang-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 560 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters…
- Anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review
- SKILL.md covers When to trigger, What the process looks like…, What reviewers are asked to… and Desk-return filters (the…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The general-audience and cross-framework bar
What it does
Lang Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters (descriptive data dump, single-framework parochialism, undocumented data), and the decision categories. Sets expectations and stress-tests before submission; it does not write the paper.
Its SKILL.md is about 1.4k 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 Testing & QA, covering Load testing. 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
- Anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review
- The general-audience and cross-framework bar
- The desk-return filters (descriptive data dump
- Single-framework parochialism
Example prompts
- “/lang-review-process”
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
Lang Review Process loads about 1.4k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 560 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). 560 words, ~1,373 tokens.
Download SKILL.mdSave it as
.claude/skills/lang-review-process/SKILL.md (or your agent's skills folder).- name
- lang-review-process
- description
- Use when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters (descriptive data dump, single-framework parochialism, undocumented data), and the decision categories. Sets expectations and stress-tests before submission; it does not write the paper.
Review Process (lang-review-process)
Knowing how Language actually evaluates a manuscript lets you pre-empt the objections before you submit. Language runs double-anonymous review under co-editors and an editorial team, drawing referees from across subfields, and it screens hard at intake: a paper that is a descriptive data dump, that lives inside one framework, or that rests on undocumented data may be returned before external review. This skill maps the process and stress-tests the paper against it.
When to trigger
- Before submission, to predict reviewer objections and the likely outcome
- After a decision letter, to read the outcome category correctly (then route to
lang-rebuttal) - Deciding whether the piece fits a full article or a shorter/online section
- Calibrating expectations for a first-round outcome
What the process looks like (verify on the author pages)
- Intake screen. Editors check fit, section, anonymization, and whether the paper makes a theoretically grounded claim for a general audience. Data dumps and framework-internal exercises can be returned without review.
- Double-anonymous external review. Referees from the relevant subfields — and often one from outside it — assess the generalization, the analysis, the evidence, engagement across frameworks, and the transparency of data and glossing.
- Decision. Typical categories: accept (rare on first pass), minor revisions, major revisions / revise-and-resubmit, reject. A substantive R&R is the normal good outcome.
- Perspectives track. A Perspectives target article is reviewed, then paired with invited Commentaries and an author Rejoinder — a different rhythm from the standard article.
What reviewers are asked to weigh (anticipate each)
| Reviewer question | Pre-empt it with… |
|---|---|
| Is there a real theoretical claim, not just description? | lang-theory-building — state the general claim + predictions |
| Does it engage rival frameworks fairly? | lang-literature-positioning — adjudicate, don't ignore |
| Can the data bear the generalization? | lang-research-design — scope the claim to the evidence |
| Are the statistics appropriate? | lang-data-analysis — mixed-effects, effect sizes, no pseudoreplication |
| Can I check the data and glosses? | lang-data-and-transparency — share data/code, source glosses |
| Is it readable outside the subfield? | lang-writing-style — theory-neutral statement, glossed jargon |
Show full SKILL.md (239 more words)Show less
Desk-return filters (the intake traps)
| Intake trap | Why it triggers a return | Fix before submitting |
|---|---|---|
| Descriptive data dump | no theoretical stakes | frame what the data are a case of |
| Single-framework parochialism | ignores rival analyses | make the adjudicating prediction explicit |
| Undocumented data | reviewers cannot check it | source glosses; share analysis data/code |
| Wrong venue | belongs at a subfield journal | re-route, or broaden the claim |
| Anonymization break | double-anonymous integrity | strip identifiers and metadata |
Calibration (Language review culture, hedged)
Orienting heuristics, not guarantees; confirm process details on the current author pages. Language review rewards a grounded, framework-fluent, checkable paper and is patient with careful revision: the realistic first-round outcome for a promising submission is a major revision, not acceptance, and the revision often asks you to broaden the framework engagement or firm up the statistics. Illustrative: a phonetics paper returns with "revise and resubmit — strengthen the model and engage the exemplar-theoretic alternative"; the productive response refits a mixed-effects model, adds the rival's prediction and tests it, and documents the measurement pipeline, rather than defending the original as-is.
Anti-patterns
- Submitting without pre-empting the obvious cross-framework objection
- Reading a major-revision letter as a rejection (or a rejection as negotiable)
- Assuming a subfield-journal analysis will clear the general-audience bar unchanged
- Ignoring the intake filters and getting returned before review
- Treating a Perspectives Commentary like a standard referee report
Output format
【Predicted intake risk】data-dump / parochial / undocumented / wrong-venue / anon-break / none
【Top reviewer objections】the 2–3 most likely, with the pre-empting skill
【Likely first-round outcome】accept / minor / major-R&R / reject (hedged)
【Section fit】full article / research report / online section / Perspectives
【Action】fixes to make before submission
【Next】lang-submission (pre-decision) or lang-rebuttal (post-decision)Supplementary resources
../../resources/external_tools.md— tooling to close the gaps reviewers flag../../resources/official-source-map.md— Language editorial and review-process sources
© 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 Language-Linguistic-Society-Skills/skills/lang-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Lang Review Process 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 |
|---|---|---|---|---|---|---|
| Lang Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Writing Livekit Scenarioslivekit-examples/agent-starter-python | 264 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Go Testingcxuu/golang-skills | 173 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Goalcraftgrp06/goalcraft | 102 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Thinking Partnermattnowdev/thinking-partner | 206 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Visionkunchenguid/vision | 331 | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Go Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
Goalcraft
grp06/goalcraft
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.
Thinking Partner
mattnowdev/thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
Vision
kunchenguid/vision
Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.
Volt Load Testing
owenHochwald/volt
Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.
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 Lang Review Process
What does Lang Review Process do?
A skill your agent uses when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters…. Lang Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters (descriptive data dump, single-framework parochialism, undocumented data), and the decision categories.
When should I use Lang Review Process?
Lang Review Process fits situations like: anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review; the general-audience and cross-framework bar; the desk-return filters (descriptive data dump; single-framework parochialism.
How do I install Lang Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-review-process -a claude-code`. Or copy the skill folder (Language-Linguistic-Society-Skills/skills/lang-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/lang-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Lang Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-review-process -a codex`. Or copy the skill folder (Language-Linguistic-Society-Skills/skills/lang-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/lang-review-process in your project. Codex loads it when a task matches its description.
Can I use Lang Review Process 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 lang-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lang-review-process, .gemini/skills/lang-review-process, .github/skills/lang-review-process and .opencode/skills/lang-review-process in your project.
What does Lang Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Lang Review Process is instructions for the agent only.
Does Lang Review Process 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 Lang Review Process 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 Lang Review Process use?
Lang Review Process 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 Lang Review Process use?
About 1.4k tokens (SKILL.md is roughly 5.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 Lang Review Process?
Skills that share tags, products or a category with Lang Review Process: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 173 stars), Goalcraft (grp06/goalcraft, 102 stars) and Thinking Partner (mattnowdev/thinking-partner, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lang Review Process?
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.