Name: opsgenie
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

opsgenie

Opsgenie integration. Manage Alerts. Use when the user wants to interact with Opsgenie data.

Quality

66%

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

Quality

Content

67%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 is a well-structured, mostly executable guide to driving Opsgenie via the Membrane CLI, with a genuine connection-readiness feedback loop. Its weaknesses are a padded intro, a redundant 'Popular actions' section, and a dangling 'Step 2' reference that breaks one workflow path.

Suggestions

Remove the opening paragraph defining Opsgenie and the filler line 'When to use which actions: Use action names and parameters as needed.' — Claude already knows this.

Resolve the dangling 'skip to Step 2' reference by labeling the searching/running-actions section as Step 2 or removing the forward reference.

Turn the 'Popular actions' section into an actual list of common Opsgenie actions instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening paragraph explains what Opsgenie is (knowledge Claude already has) and filler lines like 'When to use which actions: Use action names and parameters as needed.' add no value. It is above 2 (not heavily padded) but not the lean 4 that trims all over-explanation.	3 / 5
Actionability	Concrete, copy-pasteable membrane CLI commands cover install, auth, connection, action search/run, and proxy requests with a full flags table. Minor gaps keep it from 5: the 'Popular actions' section only repeats discovery rather than listing actual popular actions, and placeholders like CONNECTION_ID are unavoidable but unexplained.	4 / 5
Workflow Clarity	A clear install → auth → connect → search → run sequence exists with a real feedback loop (poll connection state, handle CLIENT_ACTION_REQUIRED, re-poll after user action, surface CONFIGURATION_ERROR). It misses 5 because of a dangling 'skip to Step 2' reference with no labeled Step 2, leaving one path unresolved.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references, and no bundle files exist to split. It does not reach 5 because at ~156 lines some content (the connection state-machine detail, the proxy flags table) could live in separate reference files, and the 'Popular actions' section overlaps with 'Searching for actions' rather than being cleanly separated.	4 / 5
	Total	15 / 20 Passed

Description

66%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 states what the skill does and when to use it, and the named product makes it distinct. Its main weakness is thin trigger-term coverage and limited specificity — only 'Manage Alerts' is named despite the body covering schedules, overrides, and users.

Suggestions

Expand the action list beyond 'Manage Alerts' to reflect the body's full scope (e.g. 'manage alerts, schedules, overrides, and users').

Add natural trigger terms users actually say, such as 'incidents', 'on-call schedules', or 'paging', rather than the generic 'interact with Opsgenie data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Opsgenie integration') and one concrete action ('Manage Alerts'), but coverage is not comprehensive — schedules, overrides, users, and notes from the body are absent. It sits above 2 (which would name only the domain with no real action) and below 4 (which lists several specific actions).	3 / 5
Completeness	It states both what ('Opsgenie integration. Manage Alerts.') and when ('Use when the user wants to interact with Opsgenie data.'), matching the anchor where both are present but the 'when' is generic. It falls short of 5, which requires concrete trigger phrases rather than the broad 'interact with Opsgenie data'.	4 / 5
Trigger Term Quality	'Opsgenie', 'Alerts', and 'Opsgenie data' are relevant but it misses the natural variations users actually say ('incidents', 'on-call', 'paging', 'notifications'). This matches the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	'Opsgenie' is a specific named product, giving it a clear niche with distinct triggers and minimal conflict risk with other skills. It is not merely broad like the 4-anchor example, which still implies overlap with related document/incident tools.	5 / 5
	Total	15 / 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/opsgenie/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.