Name: opslevel
Rating: 61.6 (1 reviews)
Author: membranedev

opslevel

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

Quality

72%

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/opslevel/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 a well-structured, highly actionable CLI guide with a strong validation-driven connection workflow. Its main weakness is minor redundancy and a couple of unlabeled step references.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout and justified OpsLevel context; the only real redundancy is the 'Popular actions' section repeating the action-list command already shown under 'Searching for actions'.	4 / 5
Actionability	Fully executable, copy-paste-ready commands (install, login, connection ensure, action run, request) plus a complete proxy flag table cover the common cases with specific examples.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence with explicit state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop; the dangling 'Step 2' reference and unlabeled steps are a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist; the body is well-organized into clear single-level sections with no nested references. Being over 50 lines with some inlined material (proxy table, clientAction details) that could be split keeps it just below the top anchor.	4 / 5
	Total	17 / 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 is third-person, names a distinct product, and includes an explicit 'Use when' trigger covering both what and when. It is held back by generic action verbs and limited trigger-term variation.

Suggestions

Replace generic verbs with concrete OpsLevel-specific actions (e.g., 'manage services, run checks, view maturity reports, manage teams') to raise specificity.

Broaden the trigger to capture natural user phrasings: 'Use when the user wants to manage OpsLevel services, checks, teams, or service maturity reports.'

Add common synonyms/file or entity terms users actually say when reaching for this skill.

Dimension	Reasoning	Score
Specificity	Names the OpsLevel domain and lists actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the domain-plus-1-2-actions anchor without being comprehensive.	3 / 5
Completeness	Provides both a 'what' ('OpsLevel integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with OpsLevel data'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	'OpsLevel' is a strong natural keyword and 'data, records, workflows' add some relevance, but common variations users might say (e.g., 'service maturity', 'checks', 'services') are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific OpsLevel product gives it a clear niche with low conflict risk, but the narrow 'interact with OpsLevel data' trigger may miss common phrasings, leaving minor overlap risk.	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/opslevel/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.