Analyze Countly MCP test analytics to validate event tracking and crash reports.
npx skills add https://github.com/pi-2r/copilot-cli-docker --skill countly-tst
Please help me install this Agent Skill. Skill: countly-tst Source: https://github.com/pi-2r/copilot-cli-docker/tree/main/.copilot/skills/countly-tst Command: npx skills add https://github.com/pi-2r/copilot-cli-docker --skill countly-tst
This Skill enables QA and product teams to access and interact with a Countly test environment to validate instrumentation, event tracking, and crash reporting before production releases.
Include the #countly-tst tag in your prompt to activate this skill.
High-intent search queries and answers about installing and using this skill.
You can validate Countly analytics instrumentation by analyzing test environment data to verify event tracking, user sessions, retention, and crash reports across test apps before production releases.
Yes, you can probe Countly MCP server availability to ensure reachability before executing QA workflows for validating test app analytics and crash reporting.
Testing event tracking and funnels involves analyzing user journeys and segments in a controlled staging environment to identify instrumentation issues prior to production deployment.
Yes, it supports QA workflows by allowing you to inspect user retention, demographic segmentation, device data, and crash reports to quickly identify app performance issues in test apps.
You can analyze user segments in test apps by probing the Countly MCP test environment to inspect device and demographic segmentation alongside app version data.
pi-2rQuery production analytics data from Countly via the MCP server.
altrupetsIntegrate Sentry and Firebase Crashlytics error tracking into Flutter applications.
personamanagmentlayerAutomate web and API testing with Selenium, requests, and Faker.
michsindlingerAnalyzes user behavior and product metrics for decision-making, including cohort/funnel analysis and A/B testing.
