Article Writing

Structure and style guidance for law review articles

16 stars

Best use case

Article Writing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Structure and style guidance for law review articles

Teams using Article Writing should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/article-writing/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/communication/article-writing/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/article-writing/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Article Writing Compares

Feature / AgentArticle WritingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Structure and style guidance for law review articles

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Law Review Article Writing Skill

**Domain:** Legal academic article structure and style
**Version:** 1.0.0
**Last Updated:** 2025-12-15

## Overview

This skill provides guidance for structuring and writing law review articles, including traditional doctrinal pieces, empirical studies, and interdisciplinary scholarship.

## Standard Article Structure

### I. Introduction (5-10% of article)

**Purpose:** Hook the reader, state the thesis, roadmap the article.

**Elements:**
1. **Opening hook** - Compelling case, statistic, or puzzle
2. **Problem statement** - What issue does this article address?
3. **Thesis statement** - What does this article argue?
4. **Contribution claim** - Why does this matter? What's new?
5. **Roadmap** - Brief preview of article structure

**Example opening patterns:**
- Case study opening: "In *Smith v. Jones*, the court faced..."
- Puzzle opening: "Legal scholars have long assumed X, but..."
- Stakes opening: "Every year, thousands of defendants..."
- Counter-intuitive opening: "Conventional wisdom holds that..."

### II. Background/Context (15-20%)

**Purpose:** Give readers necessary context without rehashing basics.

**Elements:**
- Legal doctrine overview (only what's needed)
- Historical development (if relevant)
- Current state of scholarship
- Gap identification (what's missing?)

**Calibration:** Assume reader is smart lawyer unfamiliar with this specific area.

### III. Core Argument (40-50%)

**Purpose:** Develop and support the thesis.

**Structure options:**

**Linear argument:**
```
A. First supporting claim
   1. Evidence/authority
   2. Analysis
B. Second supporting claim
   1. Evidence/authority
   2. Analysis
C. Third supporting claim
   ...
```

**Problem-solution:**
```
A. Problem detailed
B. Existing solutions critiqued
C. Proposed solution
D. Solution defended
```

**Case study driven:**
```
A. Case 1 analysis
B. Case 2 analysis
C. Pattern identification
D. Theoretical implications
```

### IV. Counterarguments (10-15%)

**Purpose:** Acknowledge and respond to objections.

**Best practices:**
- State opposing view fairly and strongly
- Distinguish weak vs. strong objections
- Provide substantive responses
- Concede points where appropriate

### V. Implications/Applications (10-15%)

**Purpose:** Show what follows from your argument.

**Elements:**
- Doctrinal implications
- Policy recommendations
- Future research directions
- Limitations acknowledgment

### VI. Conclusion (5%)

**Purpose:** Synthesize and close.

**Elements:**
- Restate thesis (fresh language)
- Summarize key contributions
- End with broader significance or call to action

## Writing Style Guidelines

### Voice and Tone

- **Authoritative but not arrogant** - State claims confidently, acknowledge limitations
- **Precise** - Legal writing demands exactness
- **Accessible** - Avoid unnecessary jargon
- **Engaging** - Vary sentence structure, use active voice

### Common Style Rules

1. **Prefer active voice**
   - Weak: "The statute was interpreted by the court..."
   - Strong: "The court interpreted the statute..."

2. **Avoid nominalizations**
   - Weak: "The implementation of the policy..."
   - Strong: "Implementing the policy..."

3. **Be specific**
   - Weak: "Courts have generally held..."
   - Strong: "The Second Circuit has consistently held..."

4. **Use strong verbs**
   - Weak: "The defendant made an argument that..."
   - Strong: "The defendant argued that..."

5. **Eliminate throat-clearing**
   - Cut: "It is important to note that..."
   - Cut: "It should be emphasized that..."
   - Cut: "It goes without saying that..."

### Paragraph Structure

**IRAC for analytical paragraphs:**
- **I**ssue - What question does this paragraph address?
- **R**ule - What legal principle applies?
- **A**nalysis - How does the rule apply to facts?
- **C**onclusion - What follows?

**Topic sentences:**
- Every paragraph needs a clear topic sentence
- Topic sentence should advance the argument
- Reader should understand paragraph's point from first sentence

### Transition Strategies

**Between sections:**
- End section with forward reference
- Begin section with backward reference
- Use explicit transition sentences

**Between paragraphs:**
- Logical connectors (however, moreover, therefore)
- Reference to previous paragraph's conclusion
- Parallel structure

## Footnote Density

**Academic standard:** Approximately 1 footnote per 2-3 sentences of text.

**When to footnote:**
- Direct quotations (always)
- Specific claims of fact
- Legal rules and holdings
- Others' arguments you're engaging
- Supporting examples

**When NOT to footnote:**
- Your own original analysis
- General knowledge
- Logical deductions from cited premises

## Length Calibration

| Article Type | Word Count | Footnotes |
|--------------|------------|-----------|
| Student Note | 15,000-25,000 | 150-300 |
| Standard Article | 20,000-35,000 | 200-400 |
| Major Piece | 30,000-50,000 | 300-500 |
| Essay/Commentary | 5,000-10,000 | 50-100 |

## Available Workflows

- `workflows/structure-argument.md` - Develop article outline
- `workflows/integrate-sources.md` - Weave sources into argument
- `workflows/peer-review-prep.md` - Prepare for submission

## Quality Checklist

Before completion, verify:

- [ ] Thesis clearly stated in introduction
- [ ] Each section advances the central argument
- [ ] Counterarguments addressed fairly
- [ ] Citations support claims made
- [ ] Transitions smooth between sections
- [ ] Conclusion synthesizes without mere repetition
- [ ] No unsupported assertions
- [ ] Voice consistent throughout

---

*Legal scholarship persuades through rigorous argument and careful evidence.*

Related Skills

blog-writing

16
from diegosouzapw/awesome-omni-skill

Write compelling blog posts with proven structure — hook openings, scannable body sections, clear CTAs. Use this skill when drafting blog posts, articles, or content marketing pieces.

article

16
from diegosouzapw/awesome-omni-skill

Generate technical articles and documentation using AI. Use for writing blog posts, documentation, and technical content.

article-title-optimizer

16
from diegosouzapw/awesome-omni-skill

This skill analyzes article content in-depth and generates optimized, marketable titles in the format 'Title: Subtitle' (10-12 words maximum). The skill should be used when users request title optimization, title generation, or title improvement for articles, blog posts, or written content. It generates 5 title candidates using proven formulas, evaluates them against success criteria (clickability, SEO, clarity, emotional impact, memorability, shareability), and replaces the article's title with the winning candidate.

article-recommender

16
from diegosouzapw/awesome-omni-skill

Generate three-version article recommendations (standard, concise, and personal commentary) in both Chinese and English for BestBlogs.dev weekly newsletter. Use when users request article recommendations,推荐语,推荐理由,or ask to write recommendations for newsletter content. Triggered by phrases like "帮我编写推荐理由", "生成推荐语", "write a recommendation", or when presenting curated content.

article-image-generator

16
from diegosouzapw/awesome-omni-skill

Generates consistent, professional cover images for business/fiscal articles using Ideogram with standardized prompts and naming conventions. Use when creating new articles, updating missing covers, or maintaining visual consistency across the content library.

article-extractor

16
from diegosouzapw/awesome-omni-skill

Extract clean article content from URLs (blog posts, articles, tutorials) and save as readable text. Use when user wants to download, extract, or save an article/blog post from a URL without ads, navigation, or clutter.

article-cover

16
from diegosouzapw/awesome-omni-skill

Generate professional article cover images as SVG files. Use when user wants to create cover/banner images for blog posts, technical articles, or documentation. Creates visually appealing covers with titles, diagrams, and tech-themed graphics.

article-analysis

16
from diegosouzapw/awesome-omni-skill

Analyze blog posts and web articles by fetching content from URLs. Use when the user mentions blog post, article, Substack, Medium, web page, newsletter, or provides a URL to analyze.

writing-skills

16
from diegosouzapw/awesome-omni-skill

Use when creating, updating, or improving agent skills.

writing-project-technical-writing

16
from diegosouzapw/awesome-omni-skill

Writes technical prose (READMEs, ADRs, code comments) in the project's established human voice. Use when creating or editing .md files, writing Swift doc comments, authoring ADRs, or reviewing technical writing for voice consistency.

u09613-writing-and-rhetoric-optimization-for-household-logistics

16
from diegosouzapw/awesome-omni-skill

Operate the "Writing And Rhetoric Optimization for household logistics" capability in production for household logistics workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.

postmortem-writing

16
from diegosouzapw/awesome-omni-skill

Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...