Agent skill · Code Review & Quality

lang-literature-positioning

Use when positioning a Language (LSA) manuscript within the literature so it reads as in dialogue with current linguistics across frameworks. Language reviewers are drawn from across subfields; the positioning must engage the strongest rival accounts fairly, not build a subfield-only wall. Maps the conversation; it does not write the literature review.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-literature-positioning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Language-Linguistic-Society-Skills/skills/lang-literature-positioning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Literature Positioning (lang-literature-positioning) At *Language* the literature section proves the paper is **in dialogue with current linguistics** — across frameworks, not only inside your own. Because the journal is generalist and its editors recruit **double-anonymous** reviewers from across subfields, your positioning is the signal they read to place the paper and to match referees. A section that engages only your framework's in-group tells the editor this belongs at a subfield venue. This skill maps the conversation and locates your contribution in it. ## When to trigger - Drafting or restructuring the literature/positioning section - A reader said the paper "ignores the obvious competing analysis" or "reinvents a known result" - Writing a **Discussion Note** or **Perspectives Commentary** that must engage a specific published claim precisely and fairly - Deciding which debates to foreground for a general linguistics readership ## How to position for Language 1. **Name the question, not the construction.** State the live theoretical debate the paper joins (e.g., "is this alternation phonological or morphological?") in terms a linguist outside your area recognizes — not j

What's inside
Steps it walks through
  1. When to trigger
  2. How to position for Language
  3. Cross-framework positioning (Language-distinctive)
  4. Discussion Note / Commentary positioning
  5. Positioning move table (gap-as-tension, Language-style)
  6. Anti-patterns
  7. Positioning pass for Language
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the lang-literature-positioning skill do?

Use when positioning a Language (LSA) manuscript within the literature so it reads as in dialogue with current linguistics across frameworks. Language reviewers are drawn from across subfields; the positioning must engage the strongest rival accounts fairly, not build a subfield-only wall. Maps the conversation; it does not write the literature review.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lang-literature-positioning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going