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

Blog Docs Log in Get started

opswat

OPSWAT integration. Manage data, records, and automate workflows. Use when the user wants to interact with OPSWAT 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/opswat/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 body delivers strong executable CLI guidance and a well-structured connection state machine, but it pads the context window with vendor background Claude already knows and omits verification steps around action execution and proxy requests.

Suggestions

Cut the opening 'OPSWAT is a cybersecurity company...' paragraph; Claude does not need the company backstory to use the integration.

Add an explicit validation/checkpoint after running actions or proxy requests (e.g. inspect the `output` field and confirm expected status before proceeding) to lift workflow clarity.

Tighten or remove prose that restates the proxy options table, and drop the duplicated `action list --intent=QUERY` command that appears twice in 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but the opening paragraph explains what OPSWAT is (a company that protects critical infrastructure) — background Claude does not need — and some prose restates flag descriptions already shown in the table.	3 / 5
Actionability	Concrete, copy-pasteable `membrane` commands with `--json` flags and a clear options table cover the common cases, with only minor gaps (e.g. no full example showing a parameterized `action run` end-to-end).	4 / 5
Workflow Clarity	There is a clear connect → wait → search → run sequence with state branches (READY/BUILDING/CLIENT_ACTION_REQUIRED), but operations that run actions or proxy mutating requests lack explicit validation or verification checkpoints, capping clarity at 3 per the batch/destructive-operations rule.	3 / 5
Progressive Disclosure	Content is well-sectioned into Install, Authentication, Connecting, Searching, Popular actions, and Best practices with no nested references and no external bundle files to misplace — good organization with only minor gaps, though no detail is offloaded to separate files.	4 / 5
	Total	14 / 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 includes both a capability statement and a 'Use when' trigger, anchored to a specific brand, which satisfies the core completeness requirement. Its weakness is generic action verbs and thin trigger-term coverage lacking synonyms or product-specific phrases.

Suggestions

Replace generic verbs with OPSWAT-specific actions, e.g. 'Scan files for malware, look up hash/IP/URL reputation, and automate threat-response workflows.'

Add natural trigger phrases and synonyms users would say, such as 'OPSWAT', 'file reputation', 'hash lookup', or 'threat intelligence'.

Make the 'when' clause more concrete, e.g. 'Use when the user wants to scan a file or check hash/IP/URL reputation with OPSWAT.'

Dimension	Reasoning	Score
Specificity	Names the OPSWAT domain and lists a few concrete actions ("Manage data, records, and automate workflows") but the verbs are generic and not comprehensive — closer to "Names domain and 1-2 concrete actions" than the multi-specific anchor at 5.	3 / 5
Completeness	It states what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with OPSWAT data"), giving both halves, though the trigger clause is broad rather than concrete.	4 / 5
Trigger Term Quality	"OPSWAT" is the primary keyword and "OPSWAT data" repeats it, but there are no synonyms, product names, or natural variations a user would say (e.g. file scan, hash/IP/URL reputation), landing at "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	The OPSWAT brand name gives it a clear niche and low conflict risk with other skills, though the generic "data, records, workflows" verbs leave minor overlap risk with broad 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/opswat/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.