stakeholder-summary

Convert contract review findings into a stakeholder summary under 200 words.

9.1k|1.8k|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/anthropics/claude-for-legal --skill stakeholder-summary-anthropics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-summary
Source: https://github.com/anthropics/claude-for-legal/tree/main/commercial-legal/skills/stakeholder-summary
Command: npx skills add https://github.com/anthropics/claude-for-legal --skill stakeholder-summary-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a detailed contract review into a short, stakeholder-friendly summary that answers whether the user can sign and what practical actions or risks they should know, without sounding like legal briefing.

Core Features & Use Cases

  • Audience-calibrated stakeholder communication: Writes in plain English for procurement, department heads, finance, security/IT, or executives, matching the house style and desired length.
  • Verdict + “catch” + action checklist: Produces a compact output under 200 words with an approval-ready structure (verdict, surprise issue, 2–3 next steps, and timing).
  • Safety and routing guardrails: Applies destination/privilege checks and requires reconciliation of internal escalation routing status when relevant.

Quick Start

Use the skill to produce a stakeholder-ready summary for the business from the completed contract review, targeting an appropriate channel and approval timeline.

Frequently Asked Questions about stakeholder-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize a contract review for business stakeholders?

To summarize a contract review for business stakeholders, you translate completed legal findings into a plain English, under-200-word summary. This process converts detailed review drafts into an approval-ready verdict, catch, and action checklist format for decision-making.

What is the best way to communicate contract risks to procurement teams?

Communicating contract risks to procurement requires audience-calibrated summaries that avoid legal jargon. You can generate a compact business summary that preserves the review side framing, such as sales versus purchasing, while highlighting practical actions and timing.

Can I generate an approval-ready contract summary under 200 words?

Yes, you can generate an approval-ready contract summary under 200 words. It enforces a strict verdict, surprise issue, and 2-3 next steps format to ensure business stakeholders receive concise, decision-ready takeaways without sifting through legal briefing.

How do I handle privilege checks when routing contract summaries outside legal?

Handling privilege checks when routing contract summaries outside legal requires applying destination and privilege guardrails during the communication process. This ensures sensitive legal information is filtered appropriately before reaching procurement or executive channels.

Does stakeholder communication require reconciling escalation routing from review drafts?

Yes, stakeholder communication can require reconciling escalation routing from review drafts. The process optionally verifies and aligns the internal escalation routing status based on upstream contract review findings to ensure correct handling.