Sandbox Bench
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
A skill your agent uses when turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions, observable predictions, and…
Install Lang Theory Building
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-theory-building -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-theory-building --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-theory-building .claude/skills/lang-theory-building && 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-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-theory-building into .claude/skills/lang-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-theory-building", 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-theory-buildingType 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-theory-building -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-theory-building --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-theory-building .agents/skills/lang-theory-building && 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-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-theory-building into .agents/skills/lang-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-theory-building", 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-theory-building -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-theory-building --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-theory-building .cursor/skills/lang-theory-building && 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-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-theory-building into .cursor/skills/lang-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-theory-building", 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-theory-building--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-theory-building -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-theory-building --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-theory-building .gemini/skills/lang-theory-building && 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-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-theory-building into .gemini/skills/lang-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-theory-building", 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-theory-buildingInstalls 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-theory-building -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-theory-building .github/skills/lang-theory-building && 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-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-theory-building into .github/skills/lang-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-theory-building", 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-theory-building -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-theory-building --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-theory-building .opencode/skills/lang-theory-building && 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-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-theory-building into .opencode/skills/lang-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-theory-building", 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-theory-building- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 665 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions, observable predictions, and…
- Works in 4 steps: Generalization — state the empirical… → Analysis — give the account (e.g., a… → Predictions — what should and should not… → …
- Turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions
- SKILL.md covers When to trigger, Build the analysis (by mode of…, The cross-framework test… and The analytic-depth ladder…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lang Theory Building is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions, observable predictions, and engagement across competing frameworks rather than inside one formalism. Structures the argument; it does not gloss data or run the statistics.
Its SKILL.md is about 1.5k 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 Data & Analytics, covering Statistics. 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
- Turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions
- Observable predictions
- Engagement across competing frameworks rather than inside one formalism
Example prompts
- “/lang-theory-building”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Generalization — state the empirical generalization crisply, in theory-neutral terms first, so
- Analysis — give the account (e.g., a constraint ranking, a feature geometry, a derivation, a
- Predictions — what should and should not occur if the analysis is right; these become the
- Adjudication — show where a leading rival framework makes a different prediction, and which the
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 Theory Building loads about 1.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 665 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). 665 words, ~1,513 tokens.
Download SKILL.mdSave it as
.claude/skills/lang-theory-building/SKILL.md (or your agent's skills folder).- name
- lang-theory-building
- description
- Use when turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions, observable predictions, and engagement across competing frameworks rather than inside one formalism. Structures the argument; it does not gloss data or run the statistics.
Theory & Analysis Building (lang-theory-building)
At Language the analysis is the contribution. A glossed pattern, a corpus trend, or an experimental effect is not a Language paper until it is attached to an explicit account — what the data are a case of, what the analysis predicts, and how it fares against rival analyses. The journal's defining demand is theoretical grounding without framework parochialism: state your assumptions, but engage the alternatives a reader from another tradition would raise.
When to trigger
- The data are solid but the "so what for linguistic theory" is thin
- A reader called the paper "descriptive," "stipulative," or "framework-internal"
- You need to make the analysis's predictions explicit and testable
- Fieldwork or corpus work whose theoretical claim is implicit and needs surfacing
Build the analysis (by mode of work)
Formal (phonology / syntax / semantics / morphology)
- Generalization — state the empirical generalization crisply, in theory-neutral terms first, so any reader can see the pattern before any formalism.
- Analysis — give the account (e.g., a constraint ranking, a feature geometry, a derivation, a type-driven composition); make each assumption explicit and non-vacuous.
- Predictions — what should and should not occur if the analysis is right; these become the
probes in
lang-research-design. - Adjudication — show where a leading rival framework makes a different prediction, and which the data support.
Variationist / sociolinguistic
- Name the linguistic and social constraints and the mechanism of change or variation; connect the variable to a general model, not just a local correlation.
Historical / typological
- State the generalization across languages and the diachronic or structural mechanism behind it; say what the sample is a sample of.
Psycholinguistic / computational
- Tie the model or experiment to a claim about grammar or processing; distinguish what the result shows about the representation from what it shows about the task or architecture.
The cross-framework test (Language-specific)
Ask: Would a linguist working in a different framework accept the generalization and see why my analysis is a contender? If the argument only makes sense once your formalism is granted, you have a framework-internal exercise, not a Language contribution. Restate the generalization framework-neutrally and let the analysis compete on predictions.
The analytic-depth ladder (calibration, hedged)
An orienting heuristic, not an editorial rubric; confirm expectations against the current author pages.
| Rung | What the paper offers | Likely Language verdict |
|---|---|---|
| 0 | Glossed data, no analysis | desk-returned as description |
| 1 | Data + an analysis in one framework | promising but parochial |
| 2 | Analysis with explicit predictions, tested | the modal strong submission |
| 3 | Predictions that adjudicate between rival frameworks | the Language target |
Aim for rung 2 minimum; rung 3 wins. This premium on adjudication distinguishes Language from a subfield venue that accepts a clean derivation inside the house framework.
Show full SKILL.md (222 more words)Show less
Engaging the tradition (a Language expectation)
Reviewers expect the analysis located against foundational work — the relevant classic account (structuralist, generative, functionalist, Optimality-theoretic, usage-based) used, not name-dropped. If your account revises a standard analysis, say exactly what it keeps and what it overturns.
Referee-pushback patterns and the venue-specific fix
| Referee writes… | The Language-specific fix |
|---|---|
| "Descriptively adequate, theoretically thin." | climb to rung 2–3; state the general claim + predictions |
| "Stipulative / analysis does no work." | show the analysis rules out attested-but-unwanted patterns |
| "Ignores the [rival] account." | make the adjudicating prediction explicit and test it |
| "Reads as framework-internal." | restate the generalization framework-neutrally |
Illustrative: a study of a reduplication pattern draws "competent description, thin analysis." Climbing the ladder, the author states a general claim (an illustrative constraint interaction at the morphology–phonology interface), derives a prediction about which bases block reduplication, and shows a rival prosodic-template account predicts the opposite — moving from rung 1 to rung 3.
Anti-patterns
- Presenting a gloss table or a corpus trend as the contribution, analysis left implicit
- "Analysis" that merely restates the data in formal notation (does no predictive work)
- Assuming one framework and never engaging the alternatives (parochialism)
- Predictions stated so loosely nothing could falsify them
- Ignoring the foundational account the reviewer will expect you to build on
Output format
【Generalization】the pattern, stated theory-neutrally
【Analysis】the account + its explicit assumptions
【Predictions】what should / should not occur → research-design
【Rival adjudicated】the competing framework + the deciding prediction
【Scope】languages / constructions where the claim holds
【Cross-framework legibility】would an outsider accept the generalization? [Y/N]
【Next】lang-literature-positioningSupplementary resources
../../resources/external_tools.md— analysis tooling across subfields../../resources/official-source-map.md— Language theory-grounding and general-audience expectations
© 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-theory-building of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Lang Theory Building 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 Theory Building this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Sandbox Benchvercel/next.js | 143k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Statistical Analysisspacering-net/codeg | 3.9k | 3 repos | ~5k | Automated safety check: Pass | MIT | |
| StatsmodelszLanqing/codex-claude-academic-skills | 4.7k | 15 repos | ~4.9k | Automated safety check: Pass | BSD-3-Clause | |
| AI Daily DigestvigorX777/ai-daily-digest | 1.6k | — | ~1.3k | Automated safety check: Pass | None | |
| Statistical Powerspacering-net/codeg | 3.9k | 1 repos | ~3.6k | Automated safety check: Notes | MIT |
Similar skills
- Official
Statistical Analysis
spacering-net/codeg
Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting.
Statsmodels
zLanqing/codex-claude-academic-skills
Statistical models library for Python. An agent skill from zLanqing/codex-claude-academic-skills.
AI Daily Digest
vigorX777/ai-daily-digest
Fetches RSS feeds from 90 top Hacker News blogs (curated by Karpathy), uses AI to score and filter articles, and generates a daily digest in Markdown with Chinese-translated titles, category…
Statistical Power
spacering-net/codeg
Sample-size and statistical power calculations for planning studies.
Agent Session Monitor
higress-group/higress
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage.
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 Theory Building
What does Lang Theory Building do?
A skill your agent uses when turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions, observable predictions, and…. Lang Theory Building is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions, observable predictions, and engagement across competing frameworks rather than inside one formalism.
When should I use Lang Theory Building?
Lang Theory Building fits situations like: turning a linguistic pattern into a theoretically grounded claim for a Language (LSA) manuscript — an analysis with explicit assumptions; observable predictions; engagement across competing frameworks rather than inside one formalism.
How do I install Lang Theory Building in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-theory-building -a claude-code`. Or copy the skill folder (Language-Linguistic-Society-Skills/skills/lang-theory-building in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/lang-theory-building in your project. Claude Code loads it when a task matches its description.
How do I install Lang Theory Building in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-theory-building -a codex`. Or copy the skill folder (Language-Linguistic-Society-Skills/skills/lang-theory-building in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/lang-theory-building in your project. Codex loads it when a task matches its description.
Can I use Lang Theory Building 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-theory-building -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-theory-building, .gemini/skills/lang-theory-building, .github/skills/lang-theory-building and .opencode/skills/lang-theory-building in your project.
What does Lang Theory Building need to run?
SKILL.md names no scripts, command-line tools or credentials: Lang Theory Building is instructions for the agent only.
Does Lang Theory Building 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 Theory Building 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 Theory Building use?
Lang Theory Building 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 Theory Building use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Theory Building?
Skills that share tags, products or a category with Lang Theory Building: Sandbox Bench (vercel/next.js, 143k stars), Statistical Analysis (spacering-net/codeg, 3.9k stars), Statsmodels (zLanqing/codex-claude-academic-skills, 4.7k stars) and AI Daily Digest (vigorX777/ai-daily-digest, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lang Theory Building?
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.