All authors
Claude Skills by ahmedrzzaa
github.com/ahmedrzzaa11 skills0 installs0 views
- Coroot Database AnalysisInvestigates Postgres, MySQL, MongoDB, Redis, and Memcached problems with Coroot - slow queries, connection exhaustion, replication lag, lock contention, unavailability, and cache misses or evictions - by comparing client-side eBPF query metrics with server-side cluster-agent metrics, top-query statistics, and network RTT, including managed RDS, Aurora, ElastiCache, Cloud SQL, Memorystore, and OCI databases. Use when a database or cache is slow, failing, lagging, or saturated, or when it is u...Votes: 0GitHub stars: 2
- Coroot Deployment AnalysisDeployment and release regression analysis with Coroot - identifying what changed, what resources were allocated, and how latency, errors, CPU, memory, restarts, and dependencies behaved before versus after a rollout. Use when the user asks to analyse a deployment or release, suspects a rollout caused a regression, or is deciding whether a rollback is justified.Votes: 0GitHub stars: 2
- Coroot Incident RcaProduction incident investigation and root-cause analysis with Coroot - scoping the incident, reading incident details and existing RCA, checking application health and dependencies, correlating logs, traces, deployments, and node resources, then producing an evidence-backed incident report. Use when the user reports an outage, SLO violation, error or latency spike, firing alert, or asks why a service is down, slow, or failing.Votes: 0GitHub stars: 2
- Coroot Investigation MethodThe top-level method for observing and debugging production with Coroot - read the alert fully, then narrow the search space one step at a time (wolf fencing) from metrics to logs to traces until the root cause is visible, confirm it with an independent signal, separate mitigation from fix, and write it up. Explains what counters, gauges, histograms, percentiles, logs, trace IDs, and spans can and cannot show, and hands off to the specialised Coroot skills. Use first when paged or on call, wh...Votes: 0GitHub stars: 2
- Coroot Log AnalysisInvestigates application and infrastructure logs through Coroot - pattern-first triage of error and warning log patterns, before-versus-during comparison, full-text search with Coroot's whole-token semantics, pivoting from log entries to traces, and accounting for sampling, truncation, and retention. Use when the user asks to check logs, find what errors a service is producing, explain an error spike or a new log pattern, find log lines for a request or trace, or when an incident investigatio...Votes: 0GitHub stars: 2
- Coroot ObservabilityCore rules, tool map, and safety guardrails for investigating live production systems through Coroot MCP - project selection, application and node identity, evidence standards, query limits, and status codes. Use for any Coroot question about service health, firing alerts, logs, traces, metrics, nodes, or dependencies, and as the entry point that routes to the specialised Coroot skills for incident RCA, deployment analysis, resource analysis, and QA failure diagnosis.Votes: 0GitHub stars: 2
- Coroot Qa Failure DiagnosisDiagnoses failed Cypress and Cucumber tests and CI runs using Coroot operational evidence - correlating the failing scenario's time window with application health, logs, traces, dependencies, resources, deployments, and nodes, then classifying the failure as an application defect, infrastructure problem, dependency failure, performance regression, test-data issue, or inconclusive. Use when an automated test or CI pipeline fails and the user wants to know whether the system under test was at f...Votes: 0GitHub stars: 2
- Coroot Resource AnalysisCPU, memory, thread and process, Kubernetes capacity, network, disk, and cost analysis with Coroot telemetry - allocation versus consumption, CPU throttling, OOM kills and memory pressure, single-thread bottlenecks, requests and limits versus node allocatable capacity, dependency bottlenecks, and evidence-based right-sizing. Use when the user asks about CPU or memory allotment, limits, throttling, saturation, OOMs, thread contention, node capacity, slow disk or network, infrastructure cost, o...Votes: 0GitHub stars: 2
- Coroot SetupInstalls, configures, and connects Coroot - Kubernetes (Operator/Helm), OpenShift, Docker, Docker Swarm, ECS, Ubuntu/RHEL, and Windows agents; external Prometheus and ClickHouse, retention, high availability, S3 tiering; AWS/GCP/OCI managed-database integrations; Slack, Teams, PagerDuty, Opsgenie, and webhook notifications; OpenTelemetry instrumentation, custom metrics, dashboards; and connecting Claude Code, Cursor, Codex, or headless agents to the Coroot MCP server. Use when the user wants ...Votes: 0GitHub stars: 2
- Coroot Telemetry AnalyticsCorrect quantitative analysis of Coroot metrics with PromQL - request rate, error ratio, and latency percentiles from Coroot's eBPF request metrics, RED and USE methods, baseline and time-window comparison, simple anomaly detection, SLO error-budget and burn-rate maths, and statistical traps such as averaged percentiles and Simpson's paradox. Use when writing or interpreting query_metrics PromQL, quantifying how much worse a service got, comparing periods, checking an SLO or burn rate, or val...Votes: 0GitHub stars: 2
- Coroot Trace AnalysisInvestigates request latency and errors with Coroot distributed traces - triage with traces_summary, error-origin analysis with traces_errors, slow-band flamegraphs with traces_outliers, and span-by-span reading with get_trace - while accounting for root-span-only filters, eBPF client-only spans versus OpenTelemetry end-to-end traces, sampling, version differences, and response truncation. Use when the user asks which endpoint is slow or failing, why p95 or p99 latency rose, where an error or...Votes: 0GitHub stars: 2