setting-up-synthetic-monitoring
Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health. Use when implementing availability monitoring or tracking critical user journeys. Trigger with phrases like "setup synthetic monitoring", "monitor uptime", or "configure health checks".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill setting-up-synthetic-monitoring60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly addresses both what and when, and carves out a distinct niche in synthetic/proactive monitoring that differentiates it from other monitoring-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Setup synthetic monitoring', 'uptime checks', 'transaction monitoring', and 'API health'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (setup synthetic monitoring for uptime checks, transaction monitoring, API health) AND when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'synthetic monitoring', 'monitor uptime', 'configure health checks', 'availability monitoring', 'critical user journeys'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on synthetic/proactive monitoring with distinct triggers like 'synthetic monitoring', 'uptime', and 'health checks'. Unlikely to conflict with general monitoring or logging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is primarily descriptive rather than instructive, explaining what synthetic monitoring is and when to use it rather than providing concrete, executable guidance. It lacks any actual code, configuration examples, or specific commands that Claude could use to implement monitoring. The content would benefit significantly from executable examples showing actual monitoring tool configurations.
Suggestions
Replace abstract examples with concrete, executable configuration files (e.g., actual Datadog or Pingdom YAML/JSON configs) that can be copy-pasted
Remove the 'Overview', 'How It Works', and 'When to Use This Skill' sections - Claude already knows what synthetic monitoring is; focus on the specific implementation details
Add validation steps to the workflow, such as 'Test the monitoring check manually before enabling alerts' and 'Verify alert channels receive test notifications'
Provide actual code examples for transaction monitoring scripts rather than just mentioning they exist
| 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 what synthetic monitoring is rather than providing actionable instructions. The content is heavily padded with unnecessary context. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The 'Examples' section describes what 'the skill will do' abstractly rather than showing actual configuration files, API calls, or scripts. Instructions are vague directions like 'Configure monitoring frequency' without showing how. | 1 / 3 |
Workflow Clarity | Steps are listed in the Instructions section but lack validation checkpoints. No feedback loops for error recovery - the Error Handling section lists things to check but doesn't integrate validation into the workflow. Missing explicit verification steps before proceeding. | 2 / 3 |
Progressive Disclosure | Content is somewhat organized with clear sections, but it's a monolithic document with no references to external files for detailed configurations. The Resources section mentions guides but provides no actual links. Content that could be in separate files (transaction script examples, alert configurations) is not properly referenced. | 2 / 3 |
Total | 6 / 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 — 13 / 16 Passed
Validation for skill structure
| 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 | |
- 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.