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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/performance/synthetic-monitoring-setup/skills/setting-up-synthetic-monitoring/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

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

The body is well-sectioned but generic and non-executable: it restates high-level steps across multiple sections without concrete code, validation checkpoints, or properly linked bundle references. Actionability is the primary weakness.

Suggestions

Add concrete, executable guidance — reference and invoke the bundled setup_monitor.py with example commands, or show real API/CLI calls for Pingdom/Datadog/New Relic instead of abstract 'Configure monitoring' steps.

Collapse redundant sections (How It Works, When to Use, Examples, Instructions) and remove generic filler prose to tighten token efficiency.

Integrate validation checkpoints into the workflow (e.g., verify probe reachability and alert delivery after configuration) and fix the dangling endpoints.yaml reference to point at an actual bundle file.

Dimension	Reasoning	Score
Conciseness	Mostly structured but padded with generic prose Claude already knows ('This skill streamlines the process...', 'ensure optimal application performance') and redundant restatements across How It Works, When to Use, Examples, and Instructions.	2 / 3
Actionability	No executable code or commands anywhere in the body; steps like 'Design monitoring scenarios' and 'Configure monitoring frequency and locations' describe rather than instruct, and the bundled setup_monitor.py is never invoked or referenced.	1 / 3
Workflow Clarity	Steps are sequenced (Instructions 1–6) but lack explicit validation checkpoints or feedback loops, and Error Handling is a generic bullet list rather than integrated verification — capping at 2 per the rubric.	2 / 3
Progressive Disclosure	Bundle directories exist but are never signaled from the body, and a prerequisite references ${CLAUDE_SKILL_DIR}/monitoring/endpoints.yaml which is not present in the bundle, so references are neither clearly signaled nor accurately linked.	2 / 3
	Total	7 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong across all dimensions: it states concrete capabilities, includes explicit 'Use when' guidance with natural trigger phrases, and is clearly distinct from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'uptime checks, transaction monitoring, and API health' — matching the anchor for naming several specific capabilities rather than a vague domain.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via the 'Use when implementing availability monitoring...' clause plus named trigger phrases.	3 / 3
Trigger Term Quality	Provides natural user-sayable triggers ('setup synthetic monitoring', 'monitor uptime', 'configure health checks') with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear synthetic-monitoring niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/synthetic-monitoring-setup/skills/setting-up-synthetic-monitoring/SKILL.md
Commit: 4c47e33

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.