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

Asq Literature Positioning

ASecurity

Use when situating an Administrative Science Quarterly (ASQ) manuscript within organization-theory conversations and sharpening the gap/tension it addresses. Positions the argument; it does not develop the core theory or write the methods.

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Asq Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: asq-literature-positioning
description: Use when situating an Administrative Science Quarterly (ASQ) manuscript within organization-theory conversations and sharpening the gap/tension it addresses. Positions the argument; it does not develop the core theory or write the methods.
---

# Literature Positioning (asq-literature-positioning)

## When to trigger

- Your literature section reads as an annotated list rather than an argument
- You cite many works but are in *dialogue* with none of them
- You cannot name the specific scholarly conversation you are joining
- Reviewers say you "missed the relevant literature" or "misframed the contribution"

## Join a conversation, don't survey a field

ASQ readers are organization theorists. They expect you to enter a **specific, identifiable conversation** and advance it. The literature section is an *argument that creates the space* for your contribution — not a comprehensive survey.

Steps:

1. **Name the conversation.** Identify the 2–4 streams your paper speaks to (e.g., categories and audiences; status and Matthew effects; institutional logics; organizational identity; routines and capabilities; network brokerage; sensemaking; ecology and selection).
2. **Characterize what that conversation currently assumes.** State the prevailing view fairly and precisely — strong steelman, not strawman.
3. **Locate the tension.** Show where the conversation is incomplete, internally contradictory, or contradicted by your puzzle.
4. **Stake the opening.** Make explicit the theoretical space your paper will occupy.

## Engage the traditions

ASQ has a long lineage in organization theory and the sociology of organizations, running back to its 1956 founding by James D. Thompson. Failing to engage the relevant tradition is a common rejection trigger. Many of these traditions were *defined or sharpened in ASQ's own pages* — so the relevant prior is often an ASQ paper, not an AMJ/SMJ one. Map your puzzle to the canonical lineages where appropriate (verify exact citations yourself):

- Carnegie-school decision-making and bounded rationality (e.g., the garbage-can model, Cohen, March & Olsen 1972, ASQ)
- Institutional theory and institutional logics (a core ASQ conversation; note DiMaggio & Powell's 1983 "Iron Cage Revisited" appeared in *American Sociological Review*, not ASQ — cite it as lineage, not as an ASQ paper)
- Organizational ecology and selection
- Resource dependence and power
- Network and status/structural-position theories
- Categories, valuation, and audiences
- Identity, image, and sensemaking (e.g., Weick 1993, Mann Gulch, ASQ)
- Routines, capabilities, and practice

You need not cite all of these — but you must show command of the *relevant* lineage and recent ASQ-adjacent work in it.

## Recency and venue

- Engage **recent** work (the conversation as it stands now), not only foundational citations
- Anchor in recent **ASQ** articles first, then closely related Organization Science / AMJ / SMJ pieces — ASQ reviewers expect to see you in dialogue with the journal's own ongoing conversations, not only adjacent venues
- If a recent paper appears to scoop you, address it head-on and sharpen your distinct contribution

## Avoid the "everything" review

Cut anything that does not (a) establish the conversation, (b) build the tension, or (c) differentiate your contribution. A tight, argumentative review signals command; a sprawling one signals uncertainty.

## Checklist

- [ ] The specific conversation(s) you join are named, not implied
- [ ] The prevailing view is steelmanned, then shown to be incomplete/contradicted
- [ ] The theoretical opening for your paper is explicit
- [ ] The relevant organization-theory tradition is engaged, not bypassed
- [ ] Recent work (incl. recent ASQ) is engaged, not just classics
- [ ] Any near-scoop paper is addressed and differentiated
- [ ] Every cited stream earns its place (no filler citations)

## Anti-patterns

- "List-and-cite" reviews with no argument or tension
- Strawmanning prior work to manufacture a gap
- Citing only 1990s–2000s classics while ignoring the current debate
- Ignoring the obvious adjacent ASQ paper a reviewer will know
- Claiming "no one has studied X" instead of building a theoretical tension

## Output format

```
【Conversation(s)】the 2–4 streams you join
【Prevailing view】steelmanned summary
【Tension/opening】where it breaks and where your paper enters
【Tradition engaged】which org-theory lineage(s)
【Near-scoops handled】yes/no + how differentiated
【Next step】asq-methods
```

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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.

691 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 →