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

Journal Of Law Economics And Organization

ASecurity

Use when targeting Journal of Law, Economics, and Organization (JLEO) or deciding whether a manuscript at the intersection of law, economics, and organization fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill journal-of-law-economics-and-organization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Journal Of Law Economics And Organization?

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

Security grade badge for Journal Of Law Economics And Organization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-journal-of-law-economics-and-organization/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-journal-of-law-economics-and-organization)

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

Download with Pro
Files
SKILL.md
---
name: journal-of-law-economics-and-organization
description: Use when targeting Journal of Law, Economics, and Organization (JLEO) or deciding whether a manuscript at the intersection of law, economics, and organization fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# Journal of Law, Economics, and Organization (journal-of-law-economics-and-organization)

## Journal positioning

JLEO is the leading journal at the intersection of law, economics, and organization, publishing positive political theory, the economics of contracts and institutions, and organizational economics. It rewards papers — theoretical or empirical — that explain how legal rules, political institutions, and organizational arrangements shape behavior and outcomes. The readership spans economists, political scientists, and organizational scholars working in the institutions-and-organizations tradition, so a paper must carry a genuine law-economics-organization contribution, not a single-discipline result.

This skill is a **fit / venue-selection / re-framing** tool. It does not replace the journal's current official submission guidelines. Before submitting, re-check the live author instructions on the journal/Oxford University Press site and the editorial submission system.

## When to trigger

- The author names JLEO as the target venue, or wants a home at the law–economics–organization intersection.
- A paper analyzes contracts, institutions, political institutions, or organizational form with economic tools.
- A positive-political-theory or organizational-economics paper needs re-framing so the institutions-and-organization contribution is foregrounded.
- The author needs JLEO's desk-reject risks and a credible institutions / organization alternative list.

## Scope & topic fit

- Positive political theory: institutions, legislatures, bureaucracy, delegation, and the economics of politics.
- The economics of contracts, property rights, and incomplete contracting.
- Organizational economics: firm boundaries, hierarchy, incentives, and governance.
- Institutional analysis of law and regulation and how organizational/political structures shape outcomes.

## Method & evidence bar

- Theory papers need clearly stated models, correct equilibrium analysis, and results that illuminate institutions or organization; assumptions must map to the institutional setting.
- Empirical papers need credible identification (experiments, quasi-experiments, DiD, IV, RDD, or well-justified design) with threats pre-empted, and defensible measurement of institutional/organizational variables.
- Both modeling and empirics are welcome, but the contribution must be about the law–economics–organization mechanism, not a generic effect.
- Inference and robustness must meet current standards; institutional detail must be accurate.

## Structure & house style

- The introduction states the institutional/organizational question, the model or data, the approach, and the headline result early, and explains the law-economics-organization contribution.
- Position against the relevant positive-political-theory / organizational-economics literature; relate the model or design to the institutional setting explicitly.
- Uses an unstructured abstract; an appendix carries proofs, derivations, institutional detail, and robustness.
- Propositions and exhibits should be self-contained; the central result (model implication or credible effect) should be clearly stated.

## Official-submission checklist

- Before giving submission-ready advice, read `../../resources/source-basis.md` and `../../resources/official-source-map.md`; start from the official source anchors for this journal family, then cite the current journal-specific page you checked.
- Search the live site for "Journal of Law, Economics, and Organization instructions for authors / submission guidelines" and follow the current Oxford University Press version.
- Re-check formatting, abstract requirements, anonymization, and proof/appendix conventions on the submission system.
- Re-check the current data and code availability / replication policy for empirical work.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence stating the law–economics–organization mechanism and why it matters for institutions or organization.
- [ ] The contribution is stated as a model implication / credible institutional effect, not as statistical significance.
- [ ] The introduction positions the paper against the current positive-political-theory / organizational-economics frontier.
- [ ] Proofs are complete and correct, or identification and measurement of institutional variables are defensible.
- [ ] Appendix, institutional detail, and (if empirical) data/code are ready for the official policy.

## Common desk-reject triggers

- A single-discipline paper (pure law, pure politics, or generic economics) with no institutions-and-organization contribution.
- A theory paper with incomplete proofs or assumptions that do not map to the institutional setting.
- An empirical paper with mismeasured institutional variables and no credible identification.
- A generic effect dressed up as an organizational result with no real mechanism.

## Re-routing decision

- Empirical effects of law/regulation/antitrust/crime in the Chicago tradition → `journal-of-law-and-economics`.
- IO-theory of contracts/regulation/industry → `rand-journal-of-economics`; pure microeconomic theory / mechanism → `journal-of-economic-theory` or `games-and-economic-behavior`.
- Management/organization-theory framing → `academy-of-management-journal`; general-interest at the top → `american-economic-review`; broad general field → `european-economic-review`.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] Journal of Law, Economics, and Organization
[Topic tags] <2–3 closest topics>
[Method/evidence] <does the institutions/organization contribution clear JLEO's bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <submission system / abstract / proofs-appendix / data-code / institutional detail>
[Re-route suggestion] <if not a fit, a better-matched venue>
```

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', ...

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