monitoring-error-rates
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-error-ratesMonitor and analyze application error rates to improve reliability. Use when tracking errors in applications including HTTP errors, exceptions, and database issues. Trigger with phrases like "monitor error rates", "track application errors", or "analyze error patterns".
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
20%This skill content is highly verbose and abstract, explaining monitoring concepts Claude already understands rather than providing actionable implementation guidance. It lacks any executable code, specific commands, or concrete examples that would enable Claude to actually set up error monitoring. The structure exists but serves more as a conceptual overview than a practical skill.
Suggestions
Replace abstract descriptions with executable code examples (e.g., actual Prometheus alerting rules, Grafana dashboard JSON, or log parsing scripts)
Remove sections explaining what error monitoring is and when to use it - focus only on how to implement it
Add concrete examples with specific metrics queries, threshold values, and alert configurations that can be copy-pasted
Include validation steps in the workflow (e.g., 'Test alert by running: curl -X POST localhost:9090/-/reload && verify alert fires')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. Sections like 'Overview', 'How It Works', and 'When to Use This Skill' explain basic monitoring concepts that don't add actionable value. The content could be reduced by 70%+ while preserving all useful information. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The 'Instructions' section lists abstract steps like 'Identify error sources' without showing how. Examples describe what the skill 'will do' rather than providing actual implementation code or specific commands. | 1 / 3 |
Workflow Clarity | Steps are listed in the Instructions section with a logical sequence, but there are no validation checkpoints or feedback loops. The Error Handling section exists but is a troubleshooting list rather than integrated validation steps within the workflow. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one monolithic file. The Resources section mentions external documentation but doesn't link to specific files. Content like detailed Prometheus/Grafana configurations could be split into separate reference files. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (error monitoring with concrete error types), includes natural trigger phrases users would actually say, and explicitly addresses both what the skill does and when to use it. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Monitor and analyze application error rates' with specific error types including 'HTTP errors, exceptions, and database issues'. | 3 / 3 |
Completeness | Clearly answers both what ('Monitor and analyze application error rates to improve reliability') and when ('Use when tracking errors... Trigger with phrases like...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'monitor error rates', 'track application errors', 'analyze error patterns', plus specific error types like 'HTTP errors', 'exceptions', 'database issues'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on error rate monitoring and analysis with distinct triggers; unlikely to conflict with general monitoring or logging skills due to specific error-focused terminology. | 3 / 3 |
Total | 12 / 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.