Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Orgsci Literature Positioning

ASecurity

Use when positioning an Organization Science manuscript in the literature — identifying the organization-theory conversation it joins, problematizing rather than gap-spotting, and integrating across the disciplines (organization theory, strategy, sociology, economics, psychology) the journal draws on.

1,052 stars
0 votes
0 copies
1 views
Added 6/6/2026
ai-agentsaws

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Orgsci Literature Positioning?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Orgsci Literature Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-orgsci-literature-positioning/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-orgsci-literature-positioning)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: orgsci-literature-positioning
description: Use when positioning an Organization Science manuscript in the literature — identifying the organization-theory conversation it joins, problematizing rather than gap-spotting, and integrating across the disciplines (organization theory, strategy, sociology, economics, psychology) the journal draws on.
---

# Literature Positioning (orgsci-literature-positioning)

## When to trigger

- Your introduction reads as "no one has studied X" (gap-spotting)
- You cannot name the specific conversation your paper joins
- Reviewers cite literatures you did not engage, or say "this is not positioned"
- Your micro paper ignores the macro literature on the same construct (or vice versa)

## Join a conversation, do not spot a gap

Organization Science is **interdisciplinary** — it draws on organization theory, strategy, sociology, economics, and psychology — so positioning is not citing everything; it is locating one conversation and advancing it. Replace gap-spotting with **problematization**: surface and challenge an assumption the existing literature takes for granted, then show how your study revises it. Because the editorial standard is **overall contribution** ("theoretical novelty is neither necessary nor sufficient"), positioning should make clear which contribution source you are claiming — new theory, new data, methodological insight, a new setting that tests generalizability, a sharper mechanism, or relevance to a social problem or grand challenge.

## Position across levels and disciplines

- **Name the home conversation.** One literature where your paper is unmistakably a member — and the canonical works that define it.
- **Bridge levels honestly.** If your phenomenon has both a micro and a macro literature (e.g., individual learning vs. organizational learning; identity vs. organizational identity), engage both and state which you extend. Organization Science readers span micro to macro; a one-sided review reads as parochial.
- **Translate borrowed theory.** When you import sociology, economics, or psychology, make the organizational stakes explicit — why does an organizations audience care?
- **Set up the contribution.** The positioning should leave the reader expecting exactly the contribution your discussion will deliver, no more and no less.

## Anti-patterns

- A "literature review" that summarizes everything and argues nothing.
- Gap-spotting ("understudied," "neglected") with no challenged assumption.
- Ignoring the sibling literature at the other level of analysis.
- Citing a discipline's theory without translating it to an organizational problem.

## Output format

```
【Home conversation】the one literature this paper joins
【Challenged assumption】what the field takes for granted that you revise
【Cross-level / cross-discipline bridges】micro↔macro, borrowed theory translated
【Contribution source set up】new theory / data / method / setting / mechanism / social relevance
【Next step】orgsci-methods or orgsci-contribution-framing
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →