stakeholder-summary

Converts contract review memos into plain-English summaries for business stakeholders.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business stakeholders who requested a contract review do not want a legal memo — they want to know whether they can sign, what the catch is, and what they need to do. This Skill compresses a completed contract review into a sub-200-word summary a non-lawyer will actually read. ## Core Features & Use Cases - Audience-calibrated summaries: Tailors content for procurement, department heads, finance, security/IT, or executive sponsors, focusing only on what each audience cares about. - Enforced brevity and plain language: Caps output at 200 words, bans legal terms of art, and translates findings like liability caps and auto-renewals into business language. - Escalation reconciliation: Tallies escalation targets named in the upstream review against routed escalation drafts so no required approver is silently dropped. - Use Case: After running a vendor agreement review, ask for a summary for the procurement lead and receive a two-paragraph verdict with a short action checklist and approval timing. ## Quick Start Summarize this completed contract review for the business stakeholder in procurement.

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 a non-legal stakeholder?

Provide the completed review memo and name the audience, such as procurement or finance. The Skill produces a two-paragraph plain-English summary with a verdict, the key catch, a short action checklist, and approval timing, all under 200 words.

What should a business stakeholder contract summary include?

It should include a one-paragraph description of the deal in business terms, one paragraph on the catch or surprise, a checklist of at most three action items, and a one-line approval status. It excludes section numbers, defined terms, and legal jargon.

Does the summary change based on the audience?

Yes. Procurement sees price and renewal mechanics, finance sees total cost and renewal risk, security sees data handling and subprocessors, and executives see only whether the deal is safe to approve. The Skill asks who the audience is if it is not obvious.

Can I forward a privileged legal summary to a vendor or counterparty?

No. Forwarding privileged work product outside the legal circle can waive protection. The Skill flags risky destinations and offers a sanitized version for broad channels while keeping the privileged version for legal only.

What are the limitations of an automated contract summary?

It compresses rather than re-reviews, so it depends entirely on the quality of the upstream review memo. It also cannot assert that renewal tracking or escalations happened unless those steps were actually run and verified.