CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, code-complete monitoring skill with concrete endpoints and thresholds, but it is verbose and monolithic. Tightening the redundant metrics table and splitting the implementations into referenced script files would lift the weaker dimensions.

Suggestions

Remove or slim the 'Dashboard Metrics Summary' table since its thresholds already appear in the code comments, or conversely drop the inline thresholds and keep only the table to avoid duplication.

Move the full TypeScript implementations into scripts/ files (e.g. scripts/health-check.ts) and reference them from SKILL.md so the overview stays lean — this improves both conciseness and progressive disclosure.

Add an explicit validation/checkpoint step in the pipeline (e.g. 'Verify all checks returned before sending alerts; if a sub-check throws, log and continue rather than aborting the whole run') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code without explaining concepts Claude already knows, but the 'Dashboard Metrics Summary' table re-states threshold logic already embedded in the code comments, and the ~300-line length could be tightened — level-3 requires every token to earn its place.

2 / 3

Actionability

Provides fully executable TypeScript with specific Instantly API endpoints, concrete numeric thresholds, a working Slack alerting implementation, and copy-paste cron/GitHub Actions schedules.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced and Step 5 includes a try/catch feedback loop, but the multi-step pipeline has no explicit validation checkpoints between stages — the checks are simply aggregated and alerted, fitting the level-2 anchor of sequence present but checkpoints implicit.

2 / 3

Progressive Disclosure

Sections are well-organized, but the skill is monolithic — all five full code implementations live inline in SKILL.md with no bundle references; at ~300 lines it exceeds the simple-skill exception, so content that could be split into scripts/ is kept inline.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and clearly scoped to Instantly.ai observability. It answers both what and when with explicit, natural trigger phrases and uses standard third-person/infinitive skill voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Set up monitoring, alerting, and dashboards' plus 'campaign health monitoring, account health alerts' and 'building analytics dashboards' — matching the level-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Set up monitoring, alerting, and dashboards for Instantly.ai integrations') and when ('Use when implementing campaign health monitoring...'), with an explicit 'Trigger with phrases like' clause.

3 / 3

Trigger Term Quality

Provides natural phrases a user would say — 'instantly monitoring', 'instantly dashboard', 'instantly alerts', 'instantly observability', 'monitor instantly campaigns' — giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to Instantly.ai integrations with Instantly-prefixed triggers, giving it a clear niche unlikely to conflict with generic monitoring skills.

3 / 3

Total

12

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.