Name: sumo-logic
Rating: 61.6 (1 reviews)
Author: membranedev

sumo-logic

Sumo Logic integration. Manage Connectionses, Contents, Users, Roles. Use when the user wants to interact with Sumo Logic 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/sumo-logic/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 content is a strong, executable guide that walks through install, auth, connection setup, action discovery, and proxy use with concrete commands and explicit state checkpoints. It is slightly verbose in a few introductory spots and could add verify/retry loops around action execution.

Suggestions

Trim the product-description opener ("Sumo Logic is a cloud-based log management...") to one line, since Claude already knows what Sumo Logic is.

Add an explicit validation step after running actions or proxy requests (e.g., check the `output`/response status and retry or surface `error` when present).

Replace the bare "Sumo Logic Overview" bullet list with one line linking action discovery to `membrane action list`, since the bare names are not actionable on their own.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, leading with executable commands and flags, but a few sentences explain things Claude could infer (e.g., the Sumo Logic product pitch and "Membrane handles authentication and credentials refresh automatically"), placing it just above the score-3 midpoint.	4 / 5
Actionability	Every step is given as a concrete, copy-pasteable command (install, login, connection ensure, action list/run, proxy request) with the relevant flags and JSON-shape output fields named, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll loop, but action execution and proxy use lack explicit verify/retry steps, so most checkpoints are present with minor gaps.	4 / 5
Progressive Disclosure	The body is well-sectioned (overview, install, auth, connecting, searching, popular actions, proxy, best practices) with no bundle files, so content stays one level deep and is easy to navigate, though the overview's bare action list is a minor organization gap.	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 functional, naming the Sumo Logic domain with an explicit Use-when trigger, but it leans on the generic verb "Manage" for every entity and omits natural user terms like "logs" or "search." It is clear and distinct but not comprehensive.

Suggestions

Replace the blanket "Manage" with distinct concrete verbs per entity (e.g., "run search jobs, query messages and records, manage collectors and sources").

Add natural trigger terms users actually say: "Use when the user wants to search Sumo Logic logs, run search jobs, or query collectors and sources."

Fix the typo "Connectionses" to "Connections".

Dimension	Reasoning	Score
Specificity	The description names the domain ("Sumo Logic integration") and three concrete entity types ("Manage Connectionses, Contents, Users, Roles") but the actions are all reduced to the generic verb "Manage", so coverage is concrete in objects but not in distinct actions, matching the score-3 anchor that lists a domain with limited concrete actions.	3 / 5
Completeness	The "what" is stated ("Manage Connectionses, Contents, Users, Roles") and an explicit "when" clause is present ("Use when the user wants to interact with Sumo Logic data"), but the when-trigger is generic and could be more specific, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	"Sumo Logic" is the main natural keyword and "interact with Sumo Logic data" is a relevant phrase, but common user phrasings like "logs", "log search", "search job", or "collector" are absent, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	"Sumo Logic integration" is a clear niche unlikely to fire for unrelated skills, though the generic "interact with Sumo Logic data" trigger leaves minor overlap risk with a sibling log/analytics skill.	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/sumo-logic/SKILL.md
Commit: f484c82

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