Go2.gg

**Quick judgment** A capable, fairly comprehensive skill for URL shortening, link analytics, QR code generation, webhooks, and link-in-bio pages via the Go2.gg platform. Well-suited for marketing, growth, and content workflows where tracked links and QR codes are needed, including more advanced targeting and automation. **What it’s good for** - Creating and managing short links with rich options (custom slugs, tags, expiration, password, geo/device targeting, UTM parameters). - Pulling detailed analytics for links (total clicks, by country/device/browser/referrer, over time) for campaign reporting. - Generating QR codes (including unauthenticated, quick SVG/PNG generation) and managing tracked QR codes tied to specific links. - Setting up webhooks for click and link events to integrate with external systems (CRMs, dashboards, automations). - Programmatically managing link-in-bio (gallery) pages with multiple item types and themes. **Main risks & limitations** - **Phishing/abuse potential:** URL shorteners inherently obscure destination URLs, which can be misused for spam or phishing. This requires responsible use and adherence to safety policies. - **Tracking & privacy:** Built-in analytics and QR tracking can raise privacy concerns if used without proper user consent or disclosure. - **External dependency:** Requires the Go2.gg API and a valid `GO2GG_API_KEY` for most features; outages, rate limits (e.g., 60 req/min on free tier), or key misconfiguration will affect reliability. - **Domain & slug constraints:** Custom domains must be verified; slugs may be reserved or already in use, leading to validation errors that callers must handle. **Recommended scenarios** - Marketing, growth, and product teams needing automated creation and management of campaign links and QR codes. - Creators or businesses building and updating link-in-bio pages programmatically. - Developers integrating click analytics or short-link events into dashboards, CRMs, or automation pipelines via webhooks. - Any workflow where quick QR generation (even without auth) is needed directly from the assistant, with optional tracking when an API key is available.