Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/linear-observability
Implement monitoring, logging, and alerting for Linear integrations.
Passed 19 of 25 test cases with the skill, and 10 of 25 without it.
and 12 more in the full report
9 fixed10 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What top-level status string values should a Linear integration health check endpoint return, and what individual diagnostic check name should be used for testing API connectivity?
| Checked | Without skill | With skill |
|---|---|---|
| restricts overall health status values to healthy, degraded, or unhealthy | Missed | Passed |
| names the API connectivity check linear_api | Missed | Passed |
The instructions your model reads when the skill loads.
Production monitoring for Linear integrations using Prometheus metrics, structured logging with pino, health checks, and alerting rules. Track API latency, error rates, rate limit headroom, and webhook throughput.
// src/metrics/linear-metrics.ts
import { Counter, Histogram, Gauge, register } from "prom-client";
export const metrics = {
// API request tracking
apiRequests: new Counter({
name: "linear_api_requests_total",
help: "Total Linear API requests",
labelNames: ["operation", "status"],
}),
// Request duration
apiLatency: new Histogram({
name: "linear_api_request_duration_seconds",
help: "Linear API request duration",
labelNames: ["operation"],
buckets: [0.1, 0.25, 0.5, 1, 2, 5, 10],
}),
// Rate limit headroom
rateLimitRemaining: new Gauge({
name: "linear_rate_limit_remaining",
test cases passed, vs 10 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.