Name: alert-logic
Rating: 59.2 (1 reviews)
Author: membranedev

alert-logic

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

Quality

68%

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

Quality

Content

75%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 well-structured, actionable integration guide with executable commands and a clear workflow including state-handling checkpoints; its only weaknesses are minor verbosity and a few unresolved placeholders.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete CLI commands, but includes mild over-explanation such as "so you can focus on the integration logic rather than auth plumbing," fitting the efficient-with-minor-trimmable-padding anchor.	4 / 5
Actionability	It provides concrete, executable membrane commands with flags for install, auth, connection, action search/run, and proxy requests, with only minor gaps such as the unresolved CONNECTION_ID placeholder.	4 / 5
Workflow Clarity	A clear install → auth → connect → search → run/proxy sequence is given with a state-machine and polling feedback loop for BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, matching the clear-sequence-with-most-checkpoints anchor just short of full checklists.	4 / 5
Progressive Disclosure	The single-file skill has no bundle references but is organized into well-labeled sections with content appropriately inlined rather than buried, fitting the good-structure anchor for a self-contained skill.	4 / 5
	Total	16 / 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 correctly pairs a what/when structure and names a distinct product, but its capability verbs are generic and it lacks the natural trigger terms (incidents, scans, vulnerabilities, compliance) a user would actually say.

Suggestions

Replace generic verbs with concrete Alert Logic actions, e.g. "Search incidents and findings, run vulnerability scans, and review remediation recommendations."

Expand the "Use when" clause with natural trigger terms such as threats, incidents, scans, vulnerability assessments, and compliance.

Tighten "Manage data, records, and automate workflows" since "data" and "records" do not map to distinct Alert Logic concepts.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of actions, but "manage data" and "records" are generic rather than concrete capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both the "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Alert Logic data"), but the trigger clause is broad and could be more specific, fitting the both-present-but-could-be-tighter anchor.	4 / 5
Trigger Term Quality	The description repeats "Alert Logic" and "interact with Alert Logic data" but omits the natural terms a user would say (threats, incidents, scans, vulnerabilities, compliance), matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Alert Logic integration" names a specific product giving it a clear niche and low conflict risk, though the generic "Manage data, records" phrasing leaves minor overlap risk with adjacent security/data skills.	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/alert-logic/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.