Name: victorops
Rating: 62.4 (1 reviews)
Author: membranedev

victorops

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

Quality

74%

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/victorops/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 body is highly actionable with executable commands and a sensible workflow including connection-state feedback loops, with only minor conciseness and workflow-labeling gaps.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven, but includes minor over-explanation Claude does not need (the opening paragraph describing what VictorOps is, and the 'auth plumbing' aside).	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) plus a flags table covering the common cases.	5 / 5
Workflow Clarity	Clear sequence from install through connect to running actions, with state-check feedback loops for connection readiness; minor gap is the dangling 'skip to Step 2' reference with no labeled Step 2.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear sections and no nested references; good structure, though slightly above the simple-skill threshold and without external references to signal.	4 / 5
	Total	17 / 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 covers both what and when with a clear, distinct VictorOps niche, but the listed actions are generic and it misses natural trigger synonyms like 'incidents' and 'on-call'.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete VictorOps-specific actions such as 'manage incidents, teams, schedules, and escalation policies'.

Add natural trigger terms users would say, e.g. 'Use when the user wants to manage VictorOps incidents, on-call schedules, or escalations'.

Mention the core entities (User, Team, Schedule, Escalation Policy, Incident) to improve specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (VictorOps) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not comprehensive enough for a 4.	3 / 5
Completeness	Explicitly states both what ('VictorOps integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with VictorOps data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the brand keyword 'VictorOps' and 'interact with VictorOps data', but omits natural synonyms users would say (incidents, on-call, alerts) that the body itself uses.	3 / 5
Distinctiveness Conflict Risk	Targets a distinct branded niche (VictorOps) with a brand-specific trigger, giving minimal conflict risk with other skills.	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/victorops/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.