Name: forescout
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

forescout

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

Quality

61%

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

Quality

Content

61%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 solid, actionable Membrane-CLI reference with a clear connection workflow, but it is held back by an unnecessary concept-explanation intro and a lack of validation/verification checkpoints on the destructive-capable action and proxy paths. No bundle files exist, so progressive disclosure is judged on the single-file structure.

Suggestions

Trim the introductory 'Forescout is a cybersecurity platform...' paragraph and the 'auth plumbing' editorializing; Claude already knows the product domain.

Add verification checkpoints after action runs and proxy requests (e.g., check the output/error field, confirm state, retry on failure) to satisfy the destructive/batch workflow requirement.

Provide one concrete Forescout-specific worked example (e.g., list devices or query a vulnerability with a real action id and input) instead of only generic Membrane command templates.

Dimension	Reasoning	Score
Conciseness	Most of the body is an efficient command reference, but the opening paragraph explaining what Forescout is ('a cybersecurity platform that provides network visibility...') and editorial lines like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude already knows. Not 4 because the concept-explanation padding is notable; not 2 because the bulk is lean and command-driven.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request with a flags table). Not 5 because placeholders like <agentType> and CONNECTION_ID are never resolved into a Forescout-specific worked example, and no common-case action is demonstrated end-to-end.	4 / 5
Workflow Clarity	The connection-readiness polling loop with state transitions is a clear sequenced workflow, but the action-execution and proxy paths (which can be destructive/batch via POST/PUT/DELETE and action runs) have no validation or verification checkpoints. The rubric caps workflow clarity at 3 for destructive/batch skills without validation, so it cannot reach 4.	3 / 5
Progressive Disclosure	The body is a single self-contained file with clear section headers and no external references (no bundle files exist), which is appropriate for its size. Not 5 because the 'Forescout Overview' section is a skeletal placeholder and 'Popular actions' redundantly repeats the 'Searching for actions' command, leaving minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

61%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 and a distinct product name, but its capability statement is generic ('manage data, records, automate workflows') rather than naming concrete Forescout actions. It scores well on trigger and distinctiveness, weaker on specificity.

Suggestions

Replace generic verbs with concrete Forescout operations, e.g., 'Discover and manage network devices, query vulnerabilities, and run remediation workflows.'

Add natural trigger synonyms users would say, such as 'devices', 'network visibility', 'IoT/OT', or 'vulnerability management'.

Tie the 'Use when...' clause to specific scenarios, e.g., 'Use when the user wants to list Forescout devices, check vulnerabilities, or trigger remediations.'

Dimension	Reasoning	Score
Specificity	The description names the Forescout domain but the actions ("Manage data, records, and automate workflows") are minimal and generic rather than concrete Forescout operations, matching the anchor 'Names the domain but actions are minimal or generic.' It does not reach 3 because no genuinely concrete actions (e.g., devices, vulnerabilities, policies) are listed.	2 / 5
Completeness	Both 'what' ("Forescout integration. Manage data, records, and automate workflows.") and an explicit 'when' ("Use when the user wants to interact with Forescout data.") are present. Not 5 because the 'what' is generic and lacks multiple concrete trigger phrases; not 3 because the 'when' is explicit rather than missing or weakly implied.	4 / 5
Trigger Term Quality	It includes the natural product keyword 'Forescout' and the trigger phrase 'interact with Forescout data', but it misses common variations and synonyms (devices, network visibility, IoT/OT, vulnerabilities). Not 4 because keyword coverage is thin beyond the product name; not 2 because 'Forescout' is a real natural term users would say.	3 / 5
Distinctiveness Conflict Risk	'Forescout' is a unique named cybersecurity product, giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills. It sits at 5 rather than 4 because no closely related skill would naturally trigger on 'Forescout data'.	5 / 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/forescout/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.