Name: alertops
Rating: 60 (1 reviews)
Author: membranedev

alertops

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

Quality

70%

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

Quality

Content

82%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 skill body is a well-structured, highly actionable guide to driving AlertOps through the Membrane CLI, with executable commands and a clear connection-state workflow. Its main gaps are minor verbosity and the lack of result-validation guidance for action runs.

Suggestions

Add a brief validation note for `membrane action run` outputs (e.g. check the `output` field and handle non-zero/error responses before proceeding), especially for mutating AlertOps actions.

Trim marketing phrasing such as "so you can focus on the integration logic rather than auth plumbing" and the redundant "Popular actions" section that repeats the `action list --intent` command from "Searching for actions".

Consider moving the connection state-machine detail or the proxy flags table into a separate reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, built around executable command examples, with only minor marketing-style padding ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run, request proxy) plus a complete flags table, with only appropriate ID placeholders.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit checkpoints (poll BUILDING until READY, handle CLIENT_ACTION_REQUIRED re-auth, inspect error on CONFIGURATION_ERROR), but the action-running step lacks equivalent validation of returned results.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no external bundle files, though the single file is somewhat long and parts (e.g. the connection state-machine detail or proxy flags) could be split out.	4 / 5
	Total	17 / 20 Passed

Description

57%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 correctly answers both what the skill does and when to use it with an explicit trigger clause, anchored to a distinct product. Its main weakness is generic, non-concrete action language that under-specifies the actual AlertOps capabilities.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete AlertOps actions such as creating alerts, managing on-call schedules, and configuring escalation policies.

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "when the user wants to create or acknowledge alerts, manage on-call schedules, or set up escalation rules in AlertOps".

Dimension	Reasoning	Score
Specificity	The description names the domain ("AlertOps integration") but its actions are generic ("Manage data, records, and automate workflows") rather than concrete operations like creating alerts or managing on-call schedules.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "Use when the user wants to interact with AlertOps data" trigger are present, but the "when" is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	"AlertOps" is a natural keyword users would say and the "Use when... interact with AlertOps data" clause provides a trigger, but coverage lacks common variations or synonyms beyond the product name and "data/records/workflows".	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a specific named product (AlertOps) gives it a clear niche with minimal conflict risk, though the generic verbs leave minor overlap with broad data-management skills.	4 / 5
	Total	13 / 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/alertops/SKILL.md
Commit: f484c82

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