Countly test environment specialist for product analytics, event tracking, and crash reporting. Use when asked to: validate event instrumentation, analyze test user sessions, check retention metrics, investigate crash reports, or debug analytics flows in the test/staging environment. Trigger keywords: countly-tst. Do NOT use for production analytics — use countly-prd instead.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "countly-tst" with this command: npx skills add stefanbosak/skillsmp-stefanbosak-stefanbosak-countly-tst
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Countly production environment specialist for product analytics, event tracking, and crash reporting. Use when asked to: validate event instrumentation, analyze user sessions, check retention metrics, investigate crash reports, or debug analytics flows in the production environment. Trigger keywords: countly-prd. Do NOT use for production analytics — use countly-prd instead.
Grafana production environment specialist for metrics, logs, traces, dashboards, and alerting. Use when asked to: query Prometheus metrics, search Loki logs, analyze Tempo traces, manage dashboards, configure alert rules, or investigate issues in the production environment. Trigger keywords: grafana-prd. Do NOT use for test environment (use grafana-tst instead).
Grafana test environment specialist for metrics, logs, traces, dashboards, and alerting. Use when asked to: query Prometheus metrics, search Loki logs, analyze Tempo traces, manage dashboards, configure alert rules, or investigate issues in the test environment. Trigger keywords: grafana-tst. Do NOT use for production environment (use grafana-prd instead).
Tools for interaction with jira production cloud environment. Use when asked to: search or filter issues with JQL, create or update tickets, transition issue status, manage epics and sprints, log work, add comments, or generate project reports. Trigger keywords: jira.