article-summary

Generates structured 500-800 word summaries of legal articles distilling thesis, methodology, arguments, authorities, conclusions, and significance. Triggers when summarizing legal scholarship, reviewing law review articles, preparing literature reviews, or triaging articles for full reading.

11 stars

Best use case

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

Generates structured 500-800 word summaries of legal articles distilling thesis, methodology, arguments, authorities, conclusions, and significance. Triggers when summarizing legal scholarship, reviewing law review articles, preparing literature reviews, or triaging articles for full reading.

Teams using article-summary 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-summary/SKILL.md --create-dirs "https://raw.githubusercontent.com/CaseMark/skills/main/skills/legal/article-summary/SKILL.md"

Manual Installation

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

How article-summary Compares

Feature / Agentarticle-summaryStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Generates structured 500-800 word summaries of legal articles distilling thesis, methodology, arguments, authorities, conclusions, and significance. Triggers when summarizing legal scholarship, reviewing law review articles, preparing literature reviews, or triaging articles for full reading.

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

# Legal Article Summary

Produces a structured summary (500–800 words) of a legal article that works as both a standalone reference and a read/skip triage tool.

## Prerequisites

- Full article text or sufficient excerpts covering thesis, methodology, arguments, and conclusions
- Citation info: author(s), title, journal, volume, year
- Target audience: academic, practitioner, or general (defaults to practitioner)

## Quick Start

1. Collect the article text and citation details
2. Classify the article type (doctrinal / empirical / policy / comparative / theoretical)
3. Produce the header block and six summary sections below
4. Verify summarized points against the original before delivering

## Output Format

### Header Block

| Field | Content |
|-------|---------|
| Citation | Bluebook or jurisdiction-appropriate format |
| Author(s) | Name(s) and affiliation if relevant |
| Publication | Journal/venue and date |
| Article Type | Doctrinal / Empirical / Policy / Comparative / Theoretical |

### Summary Sections (500–800 words total)

**1. Thesis & Research Question** — Central argument in 1-2 sentences. Identify the legal problem: doctrinal gap, policy critique, empirical question, or theoretical development.

**2. Methodology & Approach** — Method (case law analysis, statutory interpretation, comparative, empirical, theoretical). Note dataset, jurisdiction scope, or time period if applicable.

**3. Key Arguments & Findings** — Major points in logical sequence mirroring the author's reasoning. Use numbered list for distinct arguments. Preserve the author's emphasis; reflect counterarguments if substantially treated.

**4. Authorities & Precedents** — Key cases, statutes, regulations, or principles forming the analytical foundation. Note usage: supporting, distinguishing, or criticizing.

**5. Conclusions & Recommendations** — Separate analytical findings (evidence-supported) from normative proposals (reform/practice changes). Note stated limitations or areas for further research.

**6. Significance & Implications** — Relationship to existing scholarship (confirms, challenges, extends). Practical impact on practice, judicial decisions, legislation, or regulatory policy. Novel contributions.

## Pitfalls

- **Editorializing** — present arguments faithfully; no evaluative commentary unless requested
- **Flattening hedges** — preserve modal language ("may," "suggests," "could"); do not convert tentative conclusions into definitive statements
- **Over-quoting** — use direct quotes sparingly, only when phrasing is particularly significant
- **Oversimplifying** — preserve qualifications, conditions, and nuanced reasoning
- **Conflating arguments** — verify each summarized point maps to a distinct original argument
- **Terminology drift** — match the article's legal terms; briefly gloss highly specialized concepts essential to the core argument

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.