psci-literature-positioning
Use when positioning a Psychological Science manuscript against the literature within the journal's tight word budget. With roughly 40 references and a 2,000-word Introduction+Discussion, positioning must be sharp — establish the gap and the contribution fast. Stakes the contribution; it does not write the literature review.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill psci-literature-positioning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Literature Positioning (psci-literature-positioning) Psychological Science gives you almost no room for a traditional literature review: roughly **40 references** and an Introduction that shares a **2,000-word** budget with the Discussion. Positioning must be **surgical** — name the open question, the contribution, and the broad relevance in a few tight paragraphs. ## When to trigger - Drafting
What does the psci-literature-positioning skill do?
Use when positioning a Psychological Science manuscript against the literature within the journal's tight word budget. With roughly 40 references and a 2,000-word Introduction+Discussion, positioning must be sharp — establish the gap and the contribution fast. Stakes the contribution; it does not write the literature review.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill psci-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.