A skill your agent uses when targeting Linguistic Inquiry (MIT Press) or deciding whether a generative-linguistics manuscript fits this venue.

MITAuto-check passed

Install Linguistic Inquiry

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill linguistic-inquiry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills linguistic-inquiry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/English-Humanities-Journal-Skills/skills/linguistic-inquiry .claude/skills/linguistic-inquiry && rm -rf skills-src

Use ~/.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/

Facts

Skill name
linguistic-inquiry
GitHub stars
1.2k
Token cost
~1.7k tokens
SKILL.md length
740 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when targeting Linguistic Inquiry (MIT Press) or deciding whether a generative-linguistics manuscript fits this venue.

  • Targeting Linguistic Inquiry (MIT Press)
  • SKILL.md covers Journal positioning, When to trigger, Scope & topic fit and Method & evidence bar, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Deciding whether a generative-linguistics manuscript fits this venue

What it does

Linguistic Inquiry is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting Linguistic Inquiry (MIT Press) or deciding whether a generative-linguistics manuscript fits this venue. Encodes the journal's fit in generative syntax and its interfaces, the formal-analysis bar, squib format, house style, glossing and double-blind norms, official-submission re-check, and desk-reject heuristics.

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

  • Targeting Linguistic Inquiry (MIT Press)
  • Deciding whether a generative-linguistics manuscript fits this venue

Example prompts

  • “/linguistic-inquiry”

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

Linguistic Inquiry loads about 1.7k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 740 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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). 740 words, ~1,715 tokens.

Download SKILL.mdSave it as .claude/skills/linguistic-inquiry/SKILL.md (or your agent's skills folder).
name
linguistic-inquiry
description
Use when targeting Linguistic Inquiry (MIT Press) or deciding whether a generative-linguistics manuscript fits this venue. Encodes the journal's fit in generative syntax and its interfaces, the formal-analysis bar, squib format, house style, glossing and double-blind norms, official-submission re-check, and desk-reject heuristics.

Linguistic Inquiry (linguistic-inquiry)

Journal positioning

Linguistic Inquiry, published by MIT Press, is the leading venue for theoretically driven work in generative grammar — principally syntax and its interfaces with morphology, semantics, and phonology. Its defining expectation is a formal analysis that advances generative theory: a precise proposal, motivated by sharp data, that makes the grammar more explanatory or revises a theoretical assumption with consequences beyond the immediate case. The journal also publishes short squibs posing a focused empirical or theoretical problem. A broad descriptive survey, a framework-agnostic overview, or a paper indifferent to generative architecture is a poor fit. This skill is a fit / venue-selection / re-framing aid. It does not replace the journal's current submission guidelines. Before submitting, re-check the live Linguistic Inquiry author instructions, and defer all reporting specifics to the official page.

When to trigger

  • The author names Linguistic Inquiry for a generative-grammar article or a squib.
  • An analysis must be sharpened into an explicit, falsifiable formal proposal with consequences for generative theory.
  • The author is choosing between Linguistic Inquiry and a generalist or cross-linguistically oriented theoretical venue.
  • The author needs Linguistic Inquiry's formal-rigor bar and desk-reject heuristics.

Scope & topic fit

  • Generative syntax: argument structure, movement, locality, binding, case and agreement, ellipsis, and the architecture of the grammar.
  • Syntax–semantics, syntax–morphology, and syntax–phonology interfaces analyzed in generative terms.
  • Formal morphology and phonology where the proposal bears on grammatical architecture.
  • Squibs: a compact, self-contained problem or counterexample that sharpens or challenges an existing analysis.
  • Theory-comparison work where a new proposal is shown to be more explanatory than established alternatives.

Method & evidence bar

  • The contribution is an explicit, formally precise proposal whose theoretical consequences are stated; the central claim and its stakes for the grammar are clear early.
  • Empirical data (judgments, paradigms, well-chosen examples) are marshaled to motivate and test the proposal; linguistics is partly empirical, so the data must genuinely discriminate between analyses — defer reporting specifics to official guidance.
  • The formal analysis is consistent, derivations are shown, and predictions are falsifiable and checked against the data.
  • Alternative analyses are considered and shown to be less adequate or less general.
  • Cross-linguistic evidence is brought in where it bears on the generality of the proposal.
  • Numbered examples carry morpheme-by-morpheme interlinear (Leipzig-style) glosses and translations; judgment diacritics are used consistently.

Structure & house style

  • Full-length article building a formal argument step by step; squibs are short and tightly focused — re-check current length limits and article types on the live guide.
  • Citation follows the journal's current style with a reference list; theoretical notation and tree/derivation conventions are consistent and defined.
  • Double-blind review: anonymize the manuscript (self-citations and acknowledgements) per current policy.
  • Numbered examples with aligned interlinear glosses, translations, and sources, in the journal's example format; IPA where phonetic detail matters.
  • Trees, feature matrices, and derivations are typeset to the journal's specifications and remain legible in print.
Show full SKILL.md (270 more words)Show less

Official-submission checklist

  • Before giving submission-ready advice, read ../../resources/source-basis.md and ../../resources/official-source-map.md; start from the MIT Press anchors, then cite the current Linguistic Inquiry page you checked.
  • Search the live site for "Linguistic Inquiry submission guidelines" and follow the current MIT Press version.
  • Re-check article types (Article vs. Squib), length limits, and the abstract requirement.
  • Confirm the citation/notation style and anonymization for double-blind review.
  • Re-check the example/glossing format and tree/derivation typesetting requirements.
  • Re-check any data, elicitation ethics, and AI-use/competing-interest disclosures.
  • If the live official instructions conflict with this skill, the official instructions win.

Pre-submission self-check

  • There is an explicit, formally precise proposal with stated consequences for generative theory.
  • The data genuinely discriminate the proposal from the leading alternatives.
  • Derivations are shown and the predictions are falsifiable and tested.
  • Numbered examples carry Leipzig-style interlinear glosses, translations, and sources.
  • The manuscript is anonymized and notation/citation follow the current style.
  • A squib (if applicable) is self-contained and poses one focused problem.

Common desk-reject triggers

  • A descriptive or survey paper with no formal proposal or theoretical consequence.
  • An analysis indifferent to generative architecture or untestable as stated.
  • Data that do not actually distinguish the proposal from existing analyses, or ignoring strong competing analyses and established results in the area.
  • Examples lacking proper glosses, translations, or consistent judgment diacritics.
  • A squib padded into a full paper, or a full claim compressed into a squib.

Re-routing decision

  • Discipline-wide result across subfields → language (LSA generalist).
  • Framework-neutral general theoretical linguistics → journal-of-linguistics.
  • Theoretical syntax/morphology grounded in rich cross-linguistic data → natural-language-and-linguistic-theory.
  • Formal semantics or philosophy-of-language argument of philosophical interest → the-philosophical-review.
  • Sociolinguistic or experimental result, better at the disciplinary flagship → language.

Output format

text
[Fit] High / Medium / Low (one-line reason)
[Target] Linguistic Inquiry
[Area] <syntax / interface / squib>
[Claim] <the formal proposal in one line>
[Data/framework] <do the data + formal analysis clear LI's generative-theory bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <article type/squib / length / notation style / anonymization / glossing>
[Re-route suggestion] <if not a fit, a better-matched venue>

© 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 English-Humanities-Journal-Skills/skills/linguistic-inquiry of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Linguistic Inquiry 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.

Linguistic Inquiry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linguistic Inquiry this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.7kAutomated safety check: PassMIT
Touch Targetsthedaviddias/Front-End-Checklist74k—~938Automated safety check: PassMIT
Implementing Mimecast Targeted Attack Protectionmukul975/Anthropic-Cybersecurity-Skills34k—~1.8kAutomated safety check: PassApache-2.0
Target Journalbrycewang-stanford/Auto-Empirical-Research-Skills4.6k—~1.1kAutomated safety check: PassCustom licence
Press And PRappeeky/aso-skills2.2k—~1.8kAutomated safety check: PassMIT
Workflow Score To TargetMengTo/Skills6.7k—~1.3kAutomated safety check: PassMIT

Similar skills

  • Touch Targets

    thedaviddias/Front-End-Checklist

    A skill your agent uses when applies to all interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items.

    74k GitHub stars~938 tokensUpdated 4 days ago
    MobileAuto-check passed
  • Implementing Mimecast Targeted Attack Protection

    mukul975/Anthropic-Cybersecurity-Skills

    Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect…

    34k GitHub stars~1.8k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Target Journal

    brycewang-stanford/Auto-Empirical-Research-Skills

    Journal targeting analysis for the sewage-house-prices paper.

    4.6k GitHub stars~1.1k tokensUpdated 5 days ago
    Research & ScienceAuto-check passed
  • Press And PR

    appeeky/aso-skills

    When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an…

    2.2k GitHub stars~1.8k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Score work out of 10 against a clear rubric, then improve it round by round until every item reaches the target score the user named (for example "get it to 8 out of 10", "bring everything under 6…

    6.7k GitHub stars~1.3k tokensUpdated 4 days ago
    EducationAuto-check passed
  • Press Media Relations

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1…

    2.9k GitHub stars~3.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag 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…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.6k tokensUpdated 13 days ago
    Auto-check passed

Questions about Linguistic Inquiry

What does Linguistic Inquiry do?

A skill your agent uses when targeting Linguistic Inquiry (MIT Press) or deciding whether a generative-linguistics manuscript fits this venue. Linguistic Inquiry is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting Linguistic Inquiry (MIT Press) or deciding whether a generative-linguistics manuscript fits this venue.

When should I use Linguistic Inquiry?

Linguistic Inquiry fits situations like: targeting Linguistic Inquiry (MIT Press); deciding whether a generative-linguistics manuscript fits this venue.

How do I install Linguistic Inquiry in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill linguistic-inquiry -a claude-code`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/linguistic-inquiry in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/linguistic-inquiry in your project. Claude Code loads it when a task matches its description.

How do I install Linguistic Inquiry in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill linguistic-inquiry -a codex`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/linguistic-inquiry in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/linguistic-inquiry in your project. Codex loads it when a task matches its description.

Can I use Linguistic Inquiry 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 linguistic-inquiry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linguistic-inquiry, .gemini/skills/linguistic-inquiry, .github/skills/linguistic-inquiry and .opencode/skills/linguistic-inquiry in your project.

What does Linguistic Inquiry need to run?

SKILL.md names no scripts, command-line tools or credentials: Linguistic Inquiry is instructions for the agent only.

Does Linguistic Inquiry 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 Linguistic Inquiry 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 Linguistic Inquiry use?

Linguistic Inquiry 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 Linguistic Inquiry use?

About 1.7k tokens (SKILL.md is roughly 6.9k 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 Linguistic Inquiry?

Skills that share tags, products or a category with Linguistic Inquiry: Touch Targets (thedaviddias/Front-End-Checklist, 74k stars), Implementing Mimecast Targeted Attack Protection (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Target Journal (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars) and Press And PR (appeeky/aso-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linguistic Inquiry?

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.