copilot-cli

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.

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.

Documentation search specialist for retrieving accurate, structured information from official docs, GitHub repositories, and private resources. Use when asked to: look up API references, find library usage examples, read official guides, search framework documentation, or retrieve content from a specific docs URL. Trigger keywords: doc-search. Do NOT use for real-time or frequently changing information — use web-search 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).

Graylog production environment specialist for log search, aggregation, and analysis. Use when asked to: search logs, find errors, query streams, analyze log patterns, investigate failures, check log volumes in the production environment. Trigger keywords: graylog-prd. Do NOT use for testing environment logs (use graylog-tst instead).

Graylog test environment specialist for log search, aggregation, and analysis. Use when asked to: search logs, find errors, query streams, analyze log patterns, investigate test run failures, debug staging issues, or check log volumes in the test or staging environment. Trigger keywords: graylog-tst. Do NOT use for production environment logs (use graylog-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.

Find working code samples, verify API signatures, and fix Microsoft SDK errors using official docs. Use whenever the user is writing, debugging, or reviewing code that touches any Microsoft SDK, .NET library, Azure client library, or Microsoft API—even if they don't ask for a "reference." Catches hallucinated methods, wrong signatures, and deprecated patterns. If the task involves producing or fixing Microsoft-related code, this is the right skill. Trigger keywords: ms-refs.

Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill. Trigger keywords: ms-docs.

Create agent skills for Microsoft technologies using official documentation. Use whenever the user wants to build, generate, or scaffold a skill for any Microsoft technology (Azure, .NET, M365, VS Code, Bicep, etc.)—even phrased casually like "make a skill for Cosmos DB." Investigates the topic via official docs, then generates a hybrid skill with essential knowledge stored locally and dynamic lookups for depth. Trigger keywords: ms-skill-creator.

PostgreSQL sandbox database specialist for querying, inspecting, and analyzing data. Use when asked to: list databases or tables, inspect schema and column definitions, run SELECT queries, analyze data patterns, or retrieve row counts and statistics. Trigger keywords: postgres. Do NOT use for non-PostgreSQL data stores — use the appropriate skill instead.

Structured step-by-step reasoning specialist for complex, multi-step problems. Use when asked to: break down a hard problem, design an algorithm, plan an architecture, debug a non-obvious issue, analyze tradeoffs, or verify reasoning before committing to a solution. Trigger keywords: sequential-thinking, st. Do NOT use for simple lookups, straightforward code generation, or single-step questions — answer directly instead.

Timezone and time conversion specialist for accurate, DST-aware time calculations worldwide. Use when asked to: convert a time between timezones, get the current time in a city or region, schedule meetings across multiple timezones, or check UTC offsets and daylight saving status. Trigger keywords: time-conversion, time-conv. Do NOT use for calendar arithmetic (adding days/weeks) — use a general reasoning approach instead.

Real-time web search specialist for retrieving up-to-date information from the internet. Use when asked to: find current events, look up recent releases or changelogs, research any topic requiring live data, or fetch and summarize the content of a specific URL. Trigger keywords: web-search. Do NOT use for static official documentation — use doc-search instead.