instantly-observability
Set up comprehensive monitoring and alerting for your Instantly.ai campaigns to ensure high deliverability.
Install
mkdir -p .claude/skills/instantly-observability && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2403" && unzip -o skill.zip -d .claude/skills/instantly-observability && rm skill.zipInstalls to .claude/skills/instantly-observability
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Set up monitoring, alerting, and dashboards for Instantly.ai integrations.Key capabilities
- →Monitor Instantly.ai campaign health
- →Track account warmup performance
- →Monitor webhook delivery status
- →Set up automated alerts for critical events
- →Generate performance dashboards from Instantly data
- →Check for unhealthy or bounce-protected campaigns
How it works
This skill uses Instantly API v2 analytics and webhook events to perform health checks on campaigns, account warmups, and webhook delivery, then sends alerts based on defined thresholds.
Inputs & outputs
When to use instantly-observability
- →Monitoring campaign status
- →Setting up deliverability alerts
- →Building dashboards for email analytics
- →Tracking webhook event health
About this skill
Instantly Integration Observability
Overview
Define actionable service signals without logging lead content, email bodies, or credentials. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result.
Prerequisites
- The target repository, Instantly workspace, environment, and accountable owner
- Current security, privacy, compliance, capacity, and change-control requirements
- An approved API v2 key only when a bounded live verification is necessary
Tool Discipline
Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output.
Current Contract
- Use campaign sending-status rather than inferring health from aggregate counts alone.
- Webhook event aggregate endpoints expose success/failure evidence.
- Workspace-wide rate limits require shared client telemetry across keys.
Authentication
Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions.
Instructions
- Define service-level indicators for request success, latency, 429s, job age, sending state, and webhook failures.
- Instrument route templates, status classes, retry counts, request IDs, and workspace-safe labels.
- Poll documented health and aggregate endpoints at a bounded cadence.
- Redact API keys, addresses, lead payloads, reply content, and email bodies.
- Set alerts against measured baselines with owner-reviewed thresholds.
- Link each alert to diagnosis, containment approval, and rollback steps.
Approval Boundaries
Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Output
Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
Error Handling
| Condition | Response |
|---|---|
401 | Stop and verify that the bearer key exists, is current, and was not revoked. |
403 | Stop and compare the operation with its exact required scope; do not broaden to all:all by default. |
429 | Coordinate the workspace-wide budget, honor endpoint overrides, and bound retries. |
| Schema or tenant mismatch | Fail closed, preserve redacted evidence, and do not retry a mutation. |
Examples
Use a compact handoff that makes scope, mutation authority, and evidence reviewable.
Input:
service=campaign-sync; window=24h; payload-logging=false
Expected handoff:
sli=defined; dashboard=planned; sensitive-fields=excluded
Resources
When not to use it
- →When the monitor itself is rate-limited
- →When Instantly updates data with a delay
Prerequisites
Limitations
- →Monitor itself can be rate-limited if checks are too frequent
- →Slack alerts require a valid webhook URL
- →Instantly data may have up to a 1-hour lag
How it compares
This skill provides automated, scheduled monitoring and alerting for Instantly.ai integrations, offering real-time awareness beyond manual checks of campaign performance.
Compared to similar skills
instantly-observability side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| instantly-observability (this skill) | 2 | 2mo | Caution | Intermediate |
| langfuse | 7 | 8mo | No flags | Intermediate |
| perplexity-observability | 1 | 2mo | No flags | Intermediate |
| typescript-sdk | 2 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
langfuse
davila7
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation.
perplexity-observability
jeremylongshore
Set up comprehensive observability for Perplexity integrations with metrics, traces, and alerts. Use when implementing monitoring for Perplexity operations, setting up dashboards, or configuring alerting for Perplexity integration health. Trigger with phrases like "perplexity monitoring", "perplexity metrics", "perplexity observability", "monitor perplexity", "perplexity alerts", "perplexity tracing".
typescript-sdk
comet-ml
TypeScript SDK patterns for Opik. Use when working in sdks/opik-typescript.
error-tracking
diet103
Add Sentry v8 error tracking and performance monitoring to your project services. Use this skill when adding error handling, creating new controllers, instrumenting cron jobs, or tracking database performance. ALL ERRORS MUST BE CAPTURED TO SENTRY - no exceptions.
azure-monitor-opentelemetry-ts
microsoft
Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Application Insights.
genkit-production-expert
jeremylongshore
Build production Firebase Genkit applications including RAG systems, multi-step flows, and tool calling for Node.js/Python/Go. Deploy to Firebase Functions or Cloud Run with AI monitoring. Use when asked to "create genkit flow" or "implement RAG". Trigger with relevant phrases based on skill purpose.