Lang Attribute
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to all HTML documents. An agent skill from thedaviddias/Front-End-Checklist.
A skill your agent uses when running the final pre-submission preflight for Language (LSA) via the Cambridge University Press ScholarOne portal — double-anonymous anonymization, the section and…
MITAuto-check passed
Install Lang Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-submission --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Language-Linguistic-Society-Skills/skills/lang-submission .claude/skills/lang-submission && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lang-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submission into .claude/skills/lang-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-submission", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submissionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-submission --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Language-Linguistic-Society-Skills/skills/lang-submission .agents/skills/lang-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lang-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submission into .agents/skills/lang-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-submission", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-submission --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Language-Linguistic-Society-Skills/skills/lang-submission .cursor/skills/lang-submission && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lang-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submission into .cursor/skills/lang-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-submission", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Language-Linguistic-Society-Skills/skills/lang-submission--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-submission --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Language-Linguistic-Society-Skills/skills/lang-submission .gemini/skills/lang-submission && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lang-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submission into .gemini/skills/lang-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-submission", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-submissionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Language-Linguistic-Society-Skills/skills/lang-submission .github/skills/lang-submission && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lang-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submission into .github/skills/lang-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-submission", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills lang-submission --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Language-Linguistic-Society-Skills/skills/lang-submission .opencode/skills/lang-submission && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lang-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Language-Linguistic-Society-Skills/skills/lang-submission into .opencode/skills/lang-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lang-submission", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lang-submission- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 722 words
- Files
- 3
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-submission preflight for Language (LSA) via the Cambridge University Press ScholarOne portal — double-anonymous anonymization, the section and…
- The section and word-limit rules (General Research Article ≤18
- SKILL.md covers When to trigger, Process facts (verify volatile…, Preflight checklist and Avoidable-failure triage (what…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Review Article ≤5
What it does
Lang Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for Language (LSA) via the Cambridge University Press ScholarOne portal — double-anonymous anonymization, the section and word-limit rules (General Research Article ≤18,000 words; Review Article ≤5,000), the abstract, Leipzig glossing, IPA, the Language Style Sheet, figure alt text, and open-access status. Final checks; it does not draft content.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `templates/checklist.md` and `templates/manuscript_template.md`).
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
- The section and word-limit rules (General Research Article ≤18
- Review Article ≤5
- Leipzig glossing
- The Language Style Sheet
Example prompts
- “/lang-submission”
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 Submission loads about 1.8k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 722 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). 722 words, ~1,757 tokens.
Download SKILL.mdSave it as
.claude/skills/lang-submission/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- lang-submission
- description
- Use when running the final pre-submission preflight for Language (LSA) via the Cambridge University Press ScholarOne portal — double-anonymous anonymization, the section and word-limit rules (General Research Article ≤18,000 words; Review Article ≤5,000), the abstract, Leipzig glossing, IPA, the Language Style Sheet, figure alt text, and open-access status. Final checks; it does not draft content.
Submission Preflight (lang-submission)
The last check before you press submit on Cambridge University Press ScholarOne — the portal for Language since January 2026, when the journal moved to CUP and became fully open access from Volume 102. Language is double-anonymous, so the most common avoidable failures are an under-anonymized manuscript and self-citations that unmask the author. Also verify the section and word limits, the Language Style Sheet citations, and the Leipzig glossing / IPA before upload. Verify all volatile items on the live CUP/LSA author pages immediately before submission.
When to trigger
- "Submitting tomorrow" — last pass before upload
- Unsure which section, files, or metadata ScholarOne expects
- Confirming anonymization, word count, abstract, glossing, style, and alt text are all handled
Process facts (verify volatile items on the official page)
- Publisher / portal: Cambridge University Press; submit via ScholarOne (since Jan 2026). An Overleaf template is available; ScholarOne accepts LaTeX and Word workflows — confirm current accepted formats.
- Access: fully open access from Volume 102 (2026); check the current APC / waiver and any read-and-publish agreement on the CUP page.
- Review model: double-anonymous — remove author names, affiliations, acknowledgments, and identifying self-references; every effort must prevent authors and reviewers from identifying each other.
- Editors: Shelome Gooden and Michael Putnam (verify the current masthead before naming an editor in any submission-facing document; editorship rotates).
- Sections & limits:
- General Research Article — up to 18,000 words inclusive of notes, charts, tables, and appendices but excluding references; submissions over 12,000 words are assessed for appropriateness and may face more stringent review.
- Research Report — a smaller, targeted contribution (shorter; confirm the current cap).
- Review Article — up to 5,000 words (excluding references).
- Discussion Notes, Reviews/Book Notices, and the four online-only sections (Perspectives, Phonological Analysis, Language and Public Policy, Teaching Linguistics).
- Abstract: required; short (target ~150 words — confirm the current limit on the author page).
- House style: the Language Style Sheet / Unified Style Sheet for Linguistics (author-date); not APA or Chicago.
- Examples: numbered; Leipzig interlinear glossing; IPA in a Unicode font.
- Figures: provide alt text / descriptive captions; vector where possible.
- Data: include a data-availability statement; share analysis data/code where ethical (see
lang-data-and-transparency).
Preflight checklist
Section & length
- Correct section selected (General Research Article / Research Report / Review Article / other)
- Within the section's word limit; General Research Article word count computed on the inclusive rule
- Over 12,000 words only if the length is genuinely earned
Anonymity (double-anonymous)
- No author names, affiliations, or acknowledgments in the manuscript
- Self-citations worded to avoid unmasking ("Author 2020", neutral phrasing)
- Identifying file metadata stripped; a separate title page if the portal requires it
Show full SKILL.md (303 more words)Show less
Content & format
- Abstract present, within the current word target, states question + data + finding
- Language Style Sheet citations and reference list (NOT APA/Chicago)
- Numbered examples, aligned Leipzig glosses, abbreviations listed, correct IPA
- Figure alt text / descriptive captions
- Data-availability statement accurate (no over-stated mandate)
- Not under review elsewhere (concurrent submission violates publishing ethics)
Avoidable-failure triage (what bounces a submission, and the fix)
| Failure at submission | Fix before upload |
|---|---|
| Author identity leaks (names, acknowledgments, metadata, unmasking self-cites) | anonymize text + strip metadata + neutralize self-references |
| Over the word limit / unearned length past 12,000 | cut to the section cap; earn every page |
| APA/Chicago references | convert to the Language/Unified Style Sheet |
| Misaligned glosses / faked IPA | fix Leipzig alignment; use a Unicode IPA font |
| Descriptive data dump, no theoretical stakes | frame the general claim (route to lang-theory-building) |
Calibration (Language-specific posture, hedged)
Reflects Language's house and culture, not universal rules; confirm on the live pages. The most common avoidable failure is an under-anonymized file under double-anonymous review; the second is a word count that misreads the inclusive General Research Article rule (notes and tables count; references do not). Illustrative: a 12,800-word General Research Article catches three triage issues at preflight — an acknowledgments footnote naming a grant and a collaborator, references still in APA from a prior subfield-journal attempt, and two figures with no alt text — and after fixes the file is anonymous, Style-Sheet-conformant, and within a defensible length.
Anti-patterns
- Leaving author identifiers in the text, acknowledgments, or file metadata (breaks double-anonymous)
- Miscomputing the inclusive word limit or pushing past 12,000 without earning it
- APA/Chicago references instead of the Language/Unified Style Sheet
- Submitting a descriptive data dump with no theoretical claim (a desk return)
- Submitting while the paper is under review at another journal
Output format
【Section】General Research Article / Research Report / Review Article / other
【Length】within cap on the inclusive rule; earned past 12,000? [Y/N]
【Anonymized】text + self-cites + metadata clean? [Y/N]
【Abstract】present, within limit, states question/data/finding? [Y/N]
【House style】Language/Unified Style Sheet (NOT APA/Chicago)? [Y/N]
【Glossing/IPA/alt text】examples, transcription, figures conform? [Y/N]
【Data statement】accurate, not over-stated? [Y/N]
【Next】lang-review-process → lang-rebuttal on R&RSupplementary resources
templates/checklist.md— printable preflight checklisttemplates/manuscript_template.md— Language-conformant manuscript skeleton../../resources/official-source-map.md— CUP/LSA submission, style, and open-access 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
SKILL.md and 2 other files in Language-Linguistic-Society-Skills/skills/lang-submission of brycewang-stanford/Awesome-Journal-Skills.
- SKILL.md
- templates/checklist.md
- templates/manuscript_template.md
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Lang Submission next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lang Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Lang Attributethedaviddias/Front-End-Checklist | 74k | — | ~995 | Automated safety check: Pass | MIT | |
| Running CI PreflightPostHog/posthog | 40k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Finalize Agent Promptgithub/awesome-copilot | 40k | 1 repos | ~224 | Automated safety check: Pass | MIT | |
| Azure Deployment Preflightgithub/awesome-copilot | 40k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Implementation Final Reviewopenai/openai-agents-python | 30k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Running CI Preflight
PostHog/posthog
Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.
- Official
Finalize Agent Prompt
github/awesome-copilot
Finalize prompt file using the role of an AI agent to polish the prompt for the end user.
- Official
Azure Deployment Preflight
github/awesome-copilot
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks.
- Official
Implementation Final Review
openai/openai-agents-python
Review completed implementation changes before final verification.
Lambda Lang
sickn33/agentic-awesome-skills
Native agent-to-agent language for compact multi-agent messaging.
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 Lang Submission
What does Lang Submission do?
A skill your agent uses when running the final pre-submission preflight for Language (LSA) via the Cambridge University Press ScholarOne portal — double-anonymous anonymization, the section and…. Lang Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for Language (LSA) via the Cambridge University Press ScholarOne portal — double-anonymous anonymization, the section and word-limit rules (General Research Article ≤18,000 words; Review Article ≤5,000), the abstract, Leipzig glossing, IPA, the Language Style Sheet, figure alt text, and open-access status.
When should I use Lang Submission?
Lang Submission fits situations like: the section and word-limit rules (General Research Article ≤18; review Article ≤5; leipzig glossing; the Language Style Sheet.
How do I install Lang Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a claude-code`. Or copy the skill folder (Language-Linguistic-Society-Skills/skills/lang-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/lang-submission in your project. Claude Code loads it when a task matches its description.
How do I install Lang Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a codex`. Or copy the skill folder (Language-Linguistic-Society-Skills/skills/lang-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/lang-submission in your project. Codex loads it when a task matches its description.
Can I use Lang Submission in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lang-submission, .gemini/skills/lang-submission, .github/skills/lang-submission and .opencode/skills/lang-submission in your project.
What does Lang Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Lang Submission is instructions for the agent only.
Does Lang Submission access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lang Submission safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lang Submission use?
Lang Submission is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lang Submission use?
About 1.8k tokens (SKILL.md is roughly 7k 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 Submission?
Skills that share tags, products or a category with Lang Submission: Lang Attribute (thedaviddias/Front-End-Checklist, 74k stars), Running CI Preflight (PostHog/posthog, 40k stars), Finalize Agent Prompt (github/awesome-copilot, 40k stars) and Azure Deployment Preflight (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lang Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.