← SwoogoCONTENT HISTORY
WHAT CHANGED
Update to Swoogo
Snapshot Nov 17, 2026 · 00:14 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Swoogo and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Connect or troubleshoot the Swoogo plugin and verify access to the user's events. Use for initial setup, missing Swoogo tools, or authentication errors; not for unrelated Codex configuration.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 442
}
],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: Connect or troubleshoot the Swoogo plugin and verify access to the user's events. Use for initial setup, missing Swoogo tools, or authentication errors; not for unrelated Codex configuration.\n---\n\n# Get started with Swoogo\n\n1. Read [the shared workflow rules](../../references/workflow-rules.md).\n2. Use the host's plugin connection flow for the bundled `swoogo` MCP server at `https://mcp.swoogo.com`. Have the user finish Swoogo sign-in and OAuth consent in the host or browser. Never request passwords, API secrets, or tokens in chat.\n3. Discover the connected tools. Use the exposed tool names and schemas; the host may add a namespace to the `swoogo_` names. If connection is still pending, report that state instead of claiming access or creating another plugin.\n4. Once connected, call `swoogo_get_events` with `per_page: 5` for a small read-only check. An empty successful result verifies the connection but does not prove the account contains no events beyond the user's permissions.\n5. Show the returned event names, IDs, dates, and status, labeling the list as a sample when more pages exist. Offer the appropriate workflow: an event briefing, registration assistance, agenda management, or attendance reporting.\n\nOn 401, reconnect using OAuth. On 403, explain the missing permission and use the existing Swoogo administrator/support route. On rate limits, respect retry guidance. Do not change authentication settings, bypass permissions, register anyone, send email, or write a record to test access.\n\nFinish with the connection result and one useful next action. Never report setup as verified before a successful authenticated read.\n"
}SHA-256 of public snapshot: 41e1319619e10fa3dcfe485ac6dc417e829714dbade7a481d54668dd829304cd