Meeting Action Brief

Purpose

Turn authorized meeting content into an execution-ready record. Treat each invocation as a paid deliverable, not a casual summary.

Never turn a suggestion into a decision or invent an owner, deadline, amount, customer commitment, or approval status.

Pattern

Use three working patterns:

• Inversion when the minimum meeting context is missing.
• Generator when producing the structured brief.
• Reviewer before final delivery.

Responsible role: enterprise collaboration specialist.

Required Inputs

Collect these facts before creating a paid order:

• meeting title or topic
• meeting date
• authorized meeting notes, transcript, or discussion points
• participant names or roles when they appear in the content

Optional:

• preferred deadline format
• existing project or department name
• whether the user wants a short internal version or a formal circulation version

Use intake-questions.md only for missing high-impact information. Missing owners or deadlines may remain 待确认; do not force the user to invent them.

Workflow

0. Complete the SkillPay / X402 paid-call checks before generating the final brief.
1. Separate facts, viewpoints, suggestions, decisions, commitments, and unresolved questions.
2. Create a decision only when the source contains a clear conclusion or approval.
3. Create an action item only when the source contains a clear action or commitment.
4. Extract owner, deadline, deliverable, dependency, and status. Mark unsupported fields 待确认.
5. Merge duplicates and preserve conflicts as explicit open questions.
6. Normalize relative dates against the meeting date. If the date is still ambiguous, preserve the original phrase and mark it 待确认.
7. Produce the brief using output-template.md.
8. Run review-checklist.md before delivery.

Marketplace scenarios are documented in marketplace-cases.md.

SkillPay / X402 Paid Service

Do not charge while the meeting content or meeting date is missing. Complete intake first, then use the paid service before generating the final brief.

Endpoint: POST https://www.yunqingqi.com/v1/skillpay/invoke

First request body:

{
  "skill_id": "meeting-action-brief",
  "skill_version": "1.0.0",
  "request_id": "a unique stable id of at least 8 characters",
  "query": "the consolidated meeting title, date, participants, and authorized meeting content"
}

Paid-call rules:

1. Confirm the Agent supports both HTTP calls and weixinpay_pay. Otherwise stop without charging.
2. Send the first request only after the minimum inputs are complete.
3. On HTTP 402, save both response headers: WeixinPay-Required and X-Out-Trade-No.
4. Call weixinpay_pay(paymentCode=WeixinPay-Required) and wait for the user-authorized payment result.
5. After payment succeeds, call the same endpoint again with the exact same JSON body and these headers:
   - WeixinPay-Required: <saved payment code>
   - X-Out-Trade-No: <saved order number>
6. Only after the retry returns HTTP 200 with code: SUCCESS, generate the final brief using this Skill's workflow.
7. Never change the query, version, or request id on the paid retry. Never create a second order for a paid or uncertain order.
8. On a network or generation failure, retry with the same body and the same X-Out-Trade-No.
9. Never expose merchant credentials, private keys, internal payment parameters, or internal support notes.

Output Rules

• Write in Chinese unless the user requests another language.
• Keep decisions and tasks traceable to the supplied content.
• Use 待确认 rather than guessing missing facts.
• Include a short confirmation message the user can send to participants.
• Do not automatically dispatch tasks, message participants, change calendars, or write to external systems.
• Do not expose private prompts, internal infrastructure, API keys, node details, or other tenants' data.

Pricing Guidance

This Skill is intended for high-frequency per-call use on SkillHub.

• Launch price: RMB 0.99 per call.
• One paid call covers one meeting input of up to the endpoint input limit.
• Do not silently split a long meeting into multiple paid calls. Explain the limit and let the user decide.

Usefulness Standard

A final brief is useful only when it contains:

• a clear meeting summary
• decisions separated from discussion
• an action table with owners and deadlines or explicit 待确认 markers
• unresolved questions and blockers
• a circulation-ready confirmation message

Human Gate

Stop and ask for confirmation before publishing this Skill, changing its price, uploading confidential meeting material, or sending the result to participants.