SuperAPI AI Directory

stakeholder-summary

General & other

View repository

Updated 10-15 20:29

About this skill

Stakeholder Summary

Matter Context

Matter context. Check the business area-level CLAUDE.md for ## 事项工作区. If Enabled is ✗, skip this section.


Recipient Check

Check the recipient before generating output. When the recipient is outside the privileged circle, flag it and provide a confidential version or redacted version.

Purpose

The business owner signing this contract does not want a legal memo. They want to know: can we sign? What are the traps? What do I need to do? This skill turns a completed review into that answer.

Which Side?

The underlying review memo was run against either seller-side or buyer-side review guidelines. Carry that framework forward accordingly. A buyer summary tells the business owner "what we get and what we agree to give up"; a seller summary tells them "what we are selling and what obligations we need to bear."

Audience Calibration

Different audiences need different summaries:

Audience Cares About Doesn't Care About
Procurement Price, renewal mechanism, approval routing Liability cap structure
Department head (budget holder) Whether the team can use it, what happens if it breaks, cost Scope of indemnity
Finance Total cost of ownership, renewal price risk Governing law
Security/IT Data processing, subprocessors, security certifications, where data is stored Everything else
Sponsoring executive Will this embarrass us, is legal blocking Details

If unclear, ask who this is for.

Summary

Length Limit—Enforced

The summary is:

  • One paragraph giving the conclusion and an explanation of what this is (in business language)
  • One paragraph explaining where attention is needed
  • A 2-3 item list listing what the stakeholder actually needs to do
  • A one-line closing with approval timing

Total no more than 200 words. If it exceeds that, it means you included details the stakeholder does not need.

Format

[工作成果文件头 — 按插件配置 ## 输出]

**[对方当事人] [协议类型]** — [可以签字 | 需要变更 | 受阻]

[一段:本协议在商业用语中是什么。不是"提供基于云的分析平台主服务协议"——而是"这是市场团队想要的仪表盘工具的合同。"]

[一段:利益方需要知道的事。如果有需要注意的地方——"注意:每年自动续约,必须在到期60天前取消。已加入追踪器,但你应该知道。"或者:"干净的协议,无意外,可以签字。"]

**你需要做的:**
- [ ] [操作事项]

**审批:** [谁在审批及预期时间]

Translation Reference

Legal Finding Business Translation
"Liability capped at 12 months of fees" "If they screw up, we can recover at most one year of what we paid them."
"No termination for convenience" "Once signed, we're locked in for the whole term—if we can't use it, we can't just cancel."
"Auto-renews with 60 days' notice" "It renews automatically every year. To cancel, we have to notify them two months before the renewal date."
"No IP indemnity" "If someone sues us claiming this tool infringes their patent, the vendor won't indemnify us."
"Subprocessor list not disclosed" "We don't know which other companies will have access to our data through them."
"Data deletion within 30 days after termination" "They delete data within one month of cancellation. Export anything you need beforehand."
"SLA credits capped at 10% of monthly fee" "We get a few credits when the service goes down. Nowhere near enough to cover the business losses from downtime."

What's not included

  • Clause numbers
  • Quoted defined terms
  • The word "indemnify" (as in "they cover us")
  • The word "notwithstanding"
  • Risk matrix with colored dots
  • The disclaimer that this is not legal advice

Handoff

From vendor agreement review/SaaS review: Those skills produce full memos. This skill reads the memo and compresses it.

To stakeholders: Send via the channel specified in the review guidelines.

Tone notes

Stakeholders remember two things about legal: whether it blocked me, and whether it explained things clearly. This skill is about how legal explains things clearly. Write like you're explaining it to a smart colleague over coffee.

If the honest summary is "no problems, sign it," then say that. Don't turn a clean review into three paragraphs just to look thorough.