Name: hyperping
Rating: 59.2 (1 reviews)
Author: membranedev

hyperping

Hyperping integration. Manage data, records, and automate workflows. Use when the user wants to interact with Hyperping data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/hyperping/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.

The body delivers executable, well-sequenced CLI guidance with a clear connection state machine and feedback loops. It is efficient and actionable, with only minor padding and no Hyperping-specific action examples.

Suggestions

Trim the marketing-style intro ('used by developers, DevOps engineers, and IT professionals...') to one line about what Hyperping monitors.

Add one or two concrete Hyperping action examples (e.g., creating a check or listing notification groups) in 'Popular actions' instead of only discovery commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean CLI commands and state-machine guidance; only minor instances of over-explanation (the 'who uses Hyperping' sentence and 'so you can focus on the integration logic' phrasing) could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready commands cover install, auth, connect, search, run, and proxy with a flags table, but 'Popular actions' stays generic with no Hyperping-specific action examples, leaving a minor gap.	4 / 5
Workflow Clarity	The install → auth → connect → poll-for-ready → search → run sequence is clear with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, though action-run result validation is not addressed.	4 / 5
Progressive Disclosure	Content is well-sectioned with no nested references and only an external docs link; with no bundle files and reasonable organization it fits the 'good structure, minor gaps' anchor rather than the exemplary split-file case.	4 / 5
	Total	16 / 20 Passed

Description

62%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.

The description cleanly answers both what and when in third person with a clear product niche, but its action list and trigger terms are generic and could be more specific. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Hyperping capabilities (e.g., 'Create and manage uptime checks, check groups, and notification groups' instead of 'Manage data, records').

Expand the trigger phrase with natural synonyms users would say, e.g. 'Use when the user wants to monitor uptime, manage checks, or configure Hyperping alerts.'

Add file-type or entity keywords (checks, monitors, notification groups) to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Hyperping) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' (Hyperping integration; manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Hyperping data) are present, though the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Hyperping data' gives one relevant natural phrase but lacks synonyms or common variations, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Hyperping' gives it a clear niche with minimal conflict risk, but the trigger phrasing is narrow enough to leave minor overlap risk with generic data skills.	4 / 5
	Total	14 / 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/hyperping/SKILL.md
Commit: f484c82

Reviewed: 5 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.