Name: securitytrails
Rating: 52 (1 reviews)
Author: membranedev

securitytrails

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/securitytrails/SKILL.md

Quality

Content

57%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 action-dense with executable Membrane CLI commands and a solid connection-state feedback loop, but suffers from redundant sections, dangling step references, and no progressive disclosure to separate reference files. Output validation is absent.

Suggestions

De-duplicate action discovery (the 'Popular actions' section repeats the 'Searching for actions' command) and trim the introductory description of what SecurityTrails is.

Fix the broken 'Step 2' / '1b' numbering so the install→auth→connect→run workflow reads as a coherent numbered sequence.

Add an output-validation step (check the `output`/`error` fields and connection `state`) after running actions or proxy requests to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes a padded intro about what SecurityTrails is and redundant action-discovery instructions repeated between 'Searching for actions' and 'Popular actions'.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands with flags and a proxy-options table; minor gaps remain such as unfilled placeholders and no fully worked end-to-end example.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with a connection-state polling feedback loop, but the 'Step 2'/'1b' numbering is dangling and there is no validation of action or proxy output.	3 / 5
Progressive Disclosure	Sections are well-organized, but all 145 lines live in a single inlined file with no references to deeper material, and no bundle files exist to offload the detailed clientAction or proxy-flag content.	3 / 5
	Total	13 / 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 is distinct and includes an explicit 'Use when' trigger, but its capability list is generic rather than naming concrete SecurityTrails operations. Trigger coverage relies on a single keyword with no synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions such as 'query WHOIS, DNS records, subdomains, and IP data'.

Add natural synonyms users might say, e.g. 'domain intelligence', 'DNS history', or 'attack surface recon', to broaden trigger coverage.

Tighten the 'when' clause with concrete trigger phrases ('Use when the user asks for DNS history, subdomains, or WHOIS lookup') for a clearer completeness fit.

Dimension	Reasoning	Score
Specificity	Names the SecurityTrails domain but the actions are generic ('Manage data, records, and automate workflows') rather than concrete operations like querying WHOIS or DNS records.	2 / 5
Completeness	Both a 'what' (SecurityTrails integration managing data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with SecurityTrails data') are present, though the 'what' is somewhat generic.	4 / 5
Trigger Term Quality	'SecurityTrails' and 'interact with SecurityTrails data' provide one relevant keyword but miss common synonyms or variations users might say, matching the single-keyword anchor.	3 / 5
Distinctiveness Conflict Risk	SecurityTrails is a named platform giving a clear niche, with only minor overlap risk against other threat-intelligence or security-data 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/securitytrails/SKILL.md
Commit: f484c82

Reviewed: 4 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.