Name: fireeye
Rating: 55.2 (1 reviews)
Author: membranedev

fireeye

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

Quality

63%

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

Quality

Content

68%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 concrete, copy-paste CLI commands and a well-structured connection workflow, but it spends tokens explaining FireEye background Claude already knows and leaves a broken 'Step 2' cross-reference plus no verification of action results. Trimming the conceptual preamble and fixing the step labeling would lift the weaker dimensions.

Suggestions

Remove or compress the opening paragraph explaining what FireEye is and the 'so you can focus on the integration logic' prose; Claude already knows the domain.

Fix the 'skip to Step 2' reference by either labeling the target section 'Step 2' or rewording to 'skip to Searching for actions' so the workflow is navigable.

Add a brief verification step after running actions (e.g., check the `output` field / error state and retry or report on failure) to close the validation gap for batch or destructive operations.

Dimension	Reasoning	Score
Conciseness	The body opens by explaining what FireEye is ("a cybersecurity company that provides products and services...") and includes padded prose like "so you can focus on the integration logic rather than auth plumbing," which is unnecessary given Claude's existing knowledge.	3 / 5
Actionability	The skill provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input, proxy request) plus a flag table, covering the common workflow cases fully.	5 / 5
Workflow Clarity	A sequence with state-check checkpoints exists (READY/BUILDING/CLIENT_ACTION_REQUIRED polling loop), but it references a 'Step 2' that is never labeled and action execution lacks result verification, matching the anchor for steps with validation gaps.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) with no external references required, though at ~140 lines it exceeds the simple-skill threshold so it stays at good-structure rather than the top anchor.	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 includes an explicit 'Use when' trigger clause and names a distinct product, but its capability language is generic ('manage data, records, automate workflows') rather than concrete. Tightening the action list with specific FireEye operations would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('manage data, records, automate workflows') with concrete FireEye operations such as 'query alerts, list events and hosts, search malware, and run tasks'.

Add natural trigger synonyms users might say, e.g. 'Use when the user asks about FireEye alerts, events, hosts, malware, or threat tasks'.

Reference the specific data objects (Alerts, Events, Hosts, Malware, Tasks) already enumerated in the body so the description signals exactly what is actionable.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the FireEye domain but the actions are generic verbs with no concrete specifics, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions at level 3.	2 / 5
Completeness	Both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with FireEye data") are present, but the trigger is generic rather than concrete, matching the anchor for both present with room to be more specific.	4 / 5
Trigger Term Quality	The only keywords are "FireEye" and "FireEye data" — relevant but a single root term with no synonyms or file extensions, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"FireEye" is a specific product name giving a distinct trigger with minimal conflict risk, though the generic action language leaves minor overlap, matching the mostly-distinct anchor.	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/fireeye/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.