Google meet collaboration workflow

Plan and validate Google Meet add-ons, conference REST integrations, event subscriptions, artifacts, and preview media API work.From its SKILL.md

Install

npx -y skills add gaelic-ghost/socket --skill google-meet-collaboration-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

1.4 KB, 236 tokens by cl100k_base, as published. Nobody here has run it

Choose the smallest correct surface: web add-on for in-meeting shared collaboration, REST API for meeting spaces and post-conference artifacts, Workspace Events for subscriptions, or the Media API only for an explicitly accepted Developer Preview evaluation.
Define Workspace identity, OAuth scopes, organizer and participant data access, add-on deployment, and data retention before implementation.
For an add-on, design shared state and participant controls as collaboration features rather than as an unattended meeting bot.
For REST/event work, separate meeting-space management from artifact processing and avoid using conference data for user performance evaluation.
For Media API evaluation, record preview status, consent, media handling, cost, and rollback conditions. Do not present preview behavior as production stable.
Validate in a test Workspace and meeting: installation, participant join, shared state, event subscription, artifact availability, authorization failure, and removal.

Start with the Google Meet SDK and API overview. Hand web implementation to the web workflow and backend work to the chosen server skill.

Read from the repository

Just SKILL.md. No reference files, no scripts.