Agent skill · data analytics · jeremylongshore
figma-observability
Set up monitoring, metrics, and alerting for Figma API integrations.
Why this skill is useful
Adds executable scripts for monitoring Figma API health with custom metrics and structured logging that aren't in public docs.
What it needs
Requires pino, prometheus, winston installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Figma Observability Overview Monitor Figma REST API health with custom metrics, structured logging, and alerts. Track request latency, error rates, rate limit headroom, and cache hit rates. Prerequisites Prometheus or compatible metrics backend (or use OpenTelemetry) Structured logging (pino, winston) Alerting system (PagerDuty, Slack, OpsGenie) Instructions Step 1: Instrumented Figma Client Step 2: Prometheus Metrics Step 3: Alert Rules Step 4: Health Check with Details Output Instrumented client logging every Figma API call Prometheus metrics for requests, latency, rate limits, cache Alert rules for error rate, rate limits, latency, auth failures Health check endpoint with Figma connectivity details Error Handling Issue Cause Solution ------- ------- ---------- High cardinality Too many label values Normalize endpoint paths Alert storms Threshold too low Tune for duration and thresholds Missing rate limit headers Not all endpoints return them Handle null values gracefully Metrics not scraping Wrong port or path Verify Prometheus scrape config Examples Scrape the instrumented client's metrics (Step 2) and confirm request tracking works: Fire the health check with dependency detail (Step 4): Alert thresholds (429 rate, p95 latency) are in references/alert-rules.md. Resources Prometheus Best Practices OpenTelemetry JS SDK Figma Rate Limits Next Steps For incident response, see figma-incident-runbook.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/figma-observability