monitoring-apis
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-apisBuild real-time API monitoring dashboards with metrics, alerts, and health checks. Use when tracking API health and performance metrics. Trigger with phrases like "monitor the API", "add API metrics", or "setup API monitoring".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill fails to deliver on its stated purpose of building API monitoring dashboards. The content is generic API development boilerplate with no monitoring-specific guidance—no metrics collection code, no alerting configuration, no health check implementations, and no dashboard setup. The skill appears to be a template that wasn't customized for the monitoring use case.
Suggestions
Add concrete, executable code examples for metrics collection (e.g., Prometheus client setup, custom metrics registration)
Include specific alerting configuration examples with thresholds and notification channels
Provide health check endpoint implementation code with actual status checks
Replace generic API development prerequisites and steps with monitoring-specific workflow: instrument endpoints → configure collectors → setup dashboards → define alerts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't teach API monitoring specifically. Prerequisites list basic development concepts Claude already knows, and the instructions are generic API development steps rather than monitoring-specific guidance. | 1 / 3 |
Actionability | No concrete code examples, commands, or executable guidance for monitoring dashboards. Instructions like 'Generate boilerplate code using Bash(api:monitor-*)' are vague and don't show actual implementation. No metrics collection, alerting, or health check code provided. | 1 / 3 |
Workflow Clarity | Steps are numbered but appear to be copy-pasted generic API development steps, not monitoring-specific workflows. Two separate numbered lists restart at 1, suggesting poor organization. No validation checkpoints for monitoring setup or alert configuration. | 1 / 3 |
Progressive Disclosure | References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is so thin that it's unclear what value those references provide. The skill body itself lacks substance to serve as a useful overview. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
90%This is a solid skill description with excellent trigger term coverage and completeness. The explicit 'Use when' and 'Trigger with phrases' clauses make it easy for Claude to know when to select this skill. The main weakness is that the capability description could be more specific about the concrete actions performed.
Suggestions
Expand the capability list with more specific actions like 'track response times, error rates, and throughput' or 'configure alerting thresholds and notification channels' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (API monitoring dashboards) and lists some actions (metrics, alerts, health checks), but lacks comprehensive detail on specific concrete actions like 'configure alert thresholds', 'visualize latency percentiles', or 'track error rates'. | 2 / 3 |
Completeness | Clearly answers both what (build real-time API monitoring dashboards with metrics, alerts, and health checks) and when (tracking API health/performance, with explicit trigger phrases provided). | 3 / 3 |
Trigger Term Quality | Includes good natural trigger phrases users would say: 'monitor the API', 'add API metrics', 'setup API monitoring', plus terms like 'API health', 'performance metrics', and 'dashboards' that cover common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API monitoring dashboards with distinct triggers like 'monitor the API' and 'API metrics' - unlikely to conflict with general dashboard skills or other monitoring types. | 3 / 3 |
Total | 11 / 12 Passed |
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.