instantly-observability
Set up monitoring, alerting, and dashboards for Instantly.ai integrations. Use when implementing campaign health monitoring, account health alerts, or building analytics dashboards from Instantly data. Trigger with phrases like "instantly monitoring", "instantly dashboard", "instantly alerts", "instantly observability", "monitor instantly campaigns".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong completeness and distinctiveness, clearly scoped to Instantly.ai monitoring and observability. The explicit trigger phrases and 'Use when' clause make it easy for Claude to select appropriately. The main weakness is that the capabilities could be more granular—listing specific concrete actions rather than broad categories like 'monitoring' and 'dashboards'.
Suggestions
Add more specific concrete actions, e.g., 'track email deliverability rates, configure threshold-based alerts for bounce rates, build campaign performance dashboards with send/open/reply metrics' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai integrations) and some actions (monitoring, alerting, dashboards), but doesn't list specific concrete actions like 'track bounce rates', 'configure Slack alerts for failed sends', or 'create campaign performance charts'. The actions remain at a category level rather than detailing specific capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up monitoring, alerting, and dashboards for Instantly.ai integrations) and 'when' (implementing campaign health monitoring, account health alerts, or building analytics dashboards) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger terms: 'instantly monitoring', 'instantly dashboard', 'instantly alerts', 'instantly observability', 'monitor instantly campaigns', plus contextual terms like 'campaign health monitoring', 'account health alerts', and 'analytics dashboards'. These cover variations users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform (Instantly.ai) combined with the specific function (monitoring/alerting/dashboards). The trigger terms all include 'instantly' which creates a clear niche unlikely to conflict with generic monitoring or dashboard skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with executable TypeScript code covering campaign health, warmup monitoring, webhook tracking, alerting, and scheduling. Its main weaknesses are moderate verbosity from repetitive code patterns across health check functions and the lack of explicit validation/verification steps to confirm the monitoring pipeline is working correctly before relying on it. The dashboard metrics summary table and error handling table are excellent additions.
Suggestions
Add a validation step (e.g., 'Step 0: Verify Setup') that runs a single health check and confirms Slack alerts are delivered before deploying the full scheduled monitor.
Consider extracting the repeated threshold-check pattern into a shared helper function to reduce code duplication and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive code blocks. While the code is useful, there's some redundancy across the health check functions and the overall structure could be tightened. The overview section is brief and appropriate, but the sheer volume of similar-pattern code (each health check follows the same structure) could be condensed with a shared pattern. | 2 / 3 |
Actionability | Fully executable TypeScript code with specific thresholds, API endpoints, concrete alert formatting, and deployment options (cron, GitHub Actions, Cloud Run). The code is copy-paste ready with clear interfaces and real API calls. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (health checks → alerting → scheduling), but there are no explicit validation checkpoints. There's no guidance on verifying the monitoring setup works correctly before relying on it, no test/dry-run step, and the error handling for the monitor itself is only briefly addressed in Step 5's catch block. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections: overview, prerequisites, numbered steps, summary table, error handling table, external resources, and a pointer to the incident runbook. References are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.