Skip to content

Conclusion

What you built

  • A meeting follow-up assistant that turns a transcript into an evidence-backed, human-approved recap in a Webex space.
  • A meeting quality troubleshooting assistant that combines MCP meeting context with REST telemetry and opens Incident Mode only after approval.
  • Preloaded reusable skills that you inspected and customized, plus a capstone that coordinated them from a single business request.
  • A take-home skill bundle that the lab team will post in the session Webex space after the lab.

Key takeaways

  • Control Hub governs tool availability. A disabled tool cannot be invoked, regardless of what a prompt or skill asks.
  • Review each side effect. Check the target, recipients, and content immediately before approving a space, membership, message, or meeting.
  • Name the data source. The official Meetings MCP server supplies meeting context; the custom quality server fetches telemetry from the REST API. Neither proves root cause on its own.
  • Ground claims in evidence. Decisions, action items, quality observations, and uncertainty should point to data the agent actually retrieved.
  • Reuse the workflow. Skills capture repeatable steps and formats, while organization policy and human approval remain in control.

Next steps

The lab team will post the take-home skill bundle in the session Webex space after the lab. Download it there, review it, and adapt it to your own approved environment.

Tell us how we did

Important

Please complete the session survey here. If you cannot do it now, complete the session survey in the WebexOne event app later.