Tessl • The management layer for AI agent skills

SkillPublic

alert-logic

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

Quality

69%

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

67%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 delivers a mostly executable, well-sequenced integration workflow with concrete CLI commands and explicit connection-state checkpoints. Its weaknesses are padding (an unexplained term list, a product intro, redundant command forms) and a broken 'Step 2' cross-reference that slightly disrupts the documented flow.

Suggestions

Cut the 'Alert Logic Overview' bullet list of bare terms (or fold each term into the action that operates on it) and drop the product-intro paragraph — the detail that matters is already conveyed by the actions and proxy section.

Fix the dangling 'Step 2' reference: either number the actual steps in 'Connecting to Alert Logic' or replace the reference with the section name the reader should jump to.

Deduplicate the action-discovery command (pick one of 'membrane action list' or 'npx @membranehq/cli@latest action list') and add a brief error-recovery note for failed action runs.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the 'Alert Logic Overview' section is a list of ten bare terms with no usage guidance, the intro paragraph explains what the product is, and the action-list command appears redundantly in two forms ('membrane action list' and 'npx @membranehq/cli@latest action list').	3 / 5
Actionability	Concrete, executable commands appear throughout (install, login, connection ensure, action list/run with flags, a proxy flag table), with only minor gaps such as the reference to a 'Step 2' section that does not exist.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run→proxy sequence is clear with explicit checkpoints (state polling, clientAction handling, error-field checks), though the dangling 'Step 2'/'1b' numbering is a minor sequencing gap and there is no error-recovery guidance for failed action runs.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-sectioned and self-contained, but the proxy flag table and clientAction schema details are reference material that could be split out, and the bare overview list adds no navigational value.	4 / 5
	Total	15 / 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 names the target product and includes an explicit 'Use when' clause, but it stops at the domain name. Its capability statements are generic ('manage data, records') with no concrete Alert Logic actions or natural trigger synonyms, making it read like a template description with the product name substituted in.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Alert Logic capabilities, e.g. 'Query incidents and findings, run vulnerability scans, manage deployments and remediations, fetch log management data'.

Expand the trigger clause with natural user phrasings and synonyms, e.g. 'Use when the user mentions Alert Logic, security incidents, threat findings, vulnerability scans, or compliance reports'.

Make the 'when' clause non-circular by tying it to user goals (investigating a threat, checking scan results, pulling compliance evidence) rather than restating 'interact with Alert Logic data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Alert Logic integration') but its actions are generic — 'Manage data, records, and automate workflows' names no concrete Alert Logic capability such as incidents, scans, or vulnerabilities.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Alert Logic data') are present, though the 'what' is vague and the 'when' is circular rather than listing concrete triggers.	4 / 5
Trigger Term Quality	'Alert Logic' is the natural keyword a user would say, but coverage stops there; common variations like threats, vulnerabilities, incidents, or security findings are missing, and 'data'/'records' are generic.	3 / 5
Distinctiveness Conflict Risk	'Alert Logic' is a distinct named product giving a clear niche, but the generic 'manage data, records, and automate workflows' phrasing carries minor overlap risk with other data-integration 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/alert-logic/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

alert-logic

Table of Contents

Is this your skill?