stakeholder-summary

Convert contract review outputs into a stakeholder-ready sign/changes/block summary.

Updated May 26, 2026
One-click install
npx skills add https://github.com/yachela/claude-for-legal-ar --skill stakeholder-summary-yachela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-summary
Source: https://github.com/yachela/claude-for-legal-ar/tree/main/commercial-legal/skills/stakeholder-summary
Command: npx skills add https://github.com/yachela/claude-for-legal-ar --skill stakeholder-summary-yachela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a contract review into a fast, business-readable summary so stakeholders can decide whether to sign without wading through legal detail.

Core Features & Use Cases

  • Plain-English verdict: Produces a two-paragraph read with a clear READY TO SIGN / NEEDS CHANGES / BLOCKED status.
  • Catch-first risk framing: Highlights the one surprising “gotcha” in stakeholder-friendly language rather than legal analysis.
  • Actionable next steps: Adds a short 2-3 item checklist describing what the stakeholder must do, plus an approval/timing line.
  • Audience and tone calibration: Adjusts the summary to the intended reader (procurement, finance, security/IT, executives) and preserves the sales-side vs purchasing-side playbook framing.

Quick Start

Use the stakeholder-summary skill to summarize the contract review for the business stakeholder.

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?

A stakeholder-ready contract summary is a concise, business-readable brief that translates legal review details into a clear sign, changes, or blocked verdict. It highlights key risks and next steps so stakeholders can decide without reading the full legal analysis.

How do I translate contract risks into plain English for executives?

You translate contract risks by framing the single most surprising issue in stakeholder-friendly language rather than dense legal analysis. This produces a short brief with a clear sign or block verdict and a 2-3 item checklist of actionable next steps.

Does the contract summary brief work for both sales-side and purchasing-side reviews?

Yes, the summary brief applies to both sales-side and purchasing-side contract review outputs. It preserves the original review's framing and adjusts tone for procurement, finance, security, or executive audiences.

What is the best way to format a sign-ready contract brief?

The best way to format a sign-ready contract brief is to enforce a concise, under-200-word structure with destination and privilege checks. Include a two-paragraph read, a clear status verdict, and a short 2-3 item checklist with an approval timing line.

What should a stakeholder contract summary include for procurement teams?

A stakeholder contract summary for procurement should include a READY TO SIGN, NEEDS CHANGES, or BLOCKED status, a short 2-3 item next steps checklist, and an approval timing line. It adjusts tone specifically for the procurement audience.

When should I not use an automated contract summary brief?

You should not use an automated contract summary brief when a review requires deep legal analysis beyond stakeholder communication, or when destination and privilege checks cannot be verified. The brief supports business sign decisions, not detailed legal record-keeping.