Agent skill
opinion-summary
Summarizes U.S. transactional legal opinions into executive-ready briefs preserving issues, analysis, conclusions, qualifications, and key authorities. Triggers when asked to summarize a legal opinion, opinion memorandum, legal analysis memo, or produce an executive opinion recap.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/opinion-summary
SKILL.md
Legal Opinion Summary
Condense a full legal opinion into a professional summary that preserves substance and qualifications. Target 20–30% of original length unless instructed otherwise.
Quick Start
Before summarizing, confirm:
- Full opinion text (including relied-upon exhibits/appendices)
- Governing jurisdiction(s) and transaction context
- Privilege/confidentiality marking requirements
- Target audience and desired length
Required Sections
| Section | Content |
|---|---|
| Issues Presented | Plain-language statement of each legal question; number if multiple |
| Factual Background | Material facts only; omit narrative detail |
| Legal Analysis | Per issue: controlling standard, key reasoning, decisive facts |
| Conclusion / Recommendation | Outcome, recommendation, reliance conditions |
| Qualifications / Assumptions | Material limits, open questions, reliance assumptions |
| Risk / Alternatives | If addressed: risks, likelihoods, alternatives |
| Authorities | Controlling statutes, regs, or cases; short cites only |
Issue Analysis Table
For each issue, populate:
| Issue | Standard | Key Facts | Reasoning | Conclusion |
|---|
Compression Rules
- Include every legal question and final conclusion.
- Preserve all material qualifiers, uncertainties, and counterarguments.
- Retain controlling statutory language or contract excerpts when central to analysis.
- Remove string citations and non-controlling authorities.
- Use short citations sufficient for lookup.
Pitfalls
- Never introduce theories or arguments absent from the original opinion.
- Never overstate certainty — mirror all caveats, limits, and contingencies exactly.
- Preserve privilege/work-product sensitivity; apply required markings.
- Mark uncertain citations with
[VERIFY]. - Maintain professional memorandum tone throughout.
Key changes: consolidated the description into a tighter trigger-focused sentence, removed the verbose template (the Required Sections table + Issue Analysis Table serve the same purpose more concisely), merged the guidelines into a "Pitfalls" section, eliminated the redundant "Compression Checklist" heading in favor of "Compression Rules", and cut ~30% of tokens while preserving all legal substance. Please grant write permission so I can save the file, or copy the content above directly.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?