Name: pingdom
Rating: 64 (1 reviews)
Author: membranedev

pingdom

Pingdom integration. Manage Checks, AlertPolicies, Reports, Integrations, Users. Use when the user wants to interact with Pingdom data.

Quality

76%

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 ./skills/pingdom/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

A highly actionable, well-structured CLI integration guide with executable commands and a clear state-driven connection workflow. Its main weaknesses are introductory/marketing padding, a duplicated section, and slightly broken "Step 2" cross-references.

Suggestions

Cut the opening "Pingdom is a website monitoring service..." paragraph and the Membrane marketing phrasing; assume Claude knows what Pingdom is.

Remove or merge the "Popular actions" section, which repeats the `membrane action list --intent` command already shown under "Searching for actions".

Fix the "skip to Step 2" / "Step 2" references by either labeling the connection steps as Step 1/Step 2 or rewording them to point to a named section.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient CLI documentation, but the opening paragraph explains what Pingdom is (which Claude already knows), includes Membrane marketing language ("focus on the integration logic rather than auth plumbing"), and the "Popular actions" section duplicates the search command already shown under "Searching for actions".	3 / 5
Actionability	Fully executable, copy-paste-ready bash commands cover install, login, connection, action search/run, and proxying, with the proxy flags documented in a clear options table.	5 / 5
Workflow Clarity	A clear sequence (install → auth → connect → poll for READY → handle CLIENT_ACTION_REQUIRED → search → run) with explicit state-based feedback loops and error recovery, but the "skip to Step 2" references point to no clearly labeled Step 2, and action results lack explicit validation.	4 / 5
Progressive Disclosure	Well-organized into logical headers with all content at one level and no nested references; no bundle files exist so everything is appropriately inline, though the redundant "Popular actions" section and the loose "Step 2" cross-references are minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

78%Weight 40%Scale 1-5

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

A solid, specific description that names the Pingdom domain and its key resource types and includes an explicit Use-when clause. It could be sharpened with more varied action verbs and richer natural trigger synonyms.

Suggestions

Vary the action verb beyond "Manage" (e.g., "Create, list, and update Checks, AlertPolicies, Reports, Integrations, and Users") to lift specificity.

Add natural trigger synonyms users actually say, such as "uptime monitoring", "website monitoring", or "Pingdom alerts", to broaden trigger-term coverage.

Tighten the when-clause with concrete triggers, e.g. "Use when the user wants to manage Pingdom checks, alert policies, reports, integrations, or users."

Dimension	Reasoning	Score
Specificity	Lists several concrete resource types to manage — "Checks, AlertPolicies, Reports, Integrations, Users" — giving good coverage, but the single repeated verb "Manage" is less varied than the anchor-5 example's mix of distinct actions.	4 / 5
Completeness	It clearly states both what ("Manage Checks, AlertPolicies, Reports, Integrations, Users") and when ("Use when the user wants to interact with Pingdom data"), but the when-clause is somewhat generic rather than packed with concrete trigger phrases.	4 / 5
Trigger Term Quality	Good keyword coverage via "Pingdom" plus the named resource types, but it omits natural synonyms a user might say such as "uptime monitoring", "website monitoring", or "alerts".	4 / 5
Distinctiveness Conflict Risk	Naming the specific brand "Pingdom" with a Pingdom-scoped trigger creates a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/pingdom/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.