Name: faradaysec
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

faradaysec

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

Quality

66%

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

Quality

Content

75%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 a strong, highly actionable integration guide with executable commands and a well-sequenced connection workflow including state-based checkpoints and a feedback loop. Its main weakness is mild verbosity in the introductory framing and a few justifying sentences that assume Claude lacks context it already has.

Suggestions

Trim the opening 'Faraday is a collaborative penetration testing...' paragraph and 'This is the fastest way to get a connection' line to remove context Claude already knows.

Add an explicit verification step after 'membrane action run' (e.g. check the output/error field before reporting success) to close the workflow-validation gap.

Consider moving the proxy flag table and clientAction field reference into a one-level reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient and command-focused, but the opening paragraph explaining what Faraday is and lines like 'This is the fastest way to get a connection' restate context Claude largely already knows, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Copy-paste-ready commands cover the full flow (install, login, connection ensure, action list/run, request) plus a complete proxy-flag table, matching the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	A clear install→auth→connect→wait→search→run sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop matches the 'clear sequence with most checkpoints present; minor validation gaps' anchor; it is not a 5 because action-run results lack an explicit verification step.	4 / 5
Progressive Disclosure	With no bundle files present, the single self-contained SKILL.md is well organized into clear sections with no nested references, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor; it is not a 5 because at ~140 lines the proxy flag table and clientAction detail block could live in a one-level reference file.	4 / 5
	Total	16 / 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 pairs a what with an explicit 'Use when' clause and leverages a distinctive product name, but its action verbs are generic and it omits the natural pentest/vulnerability vocabulary users would actually say. It is functional but underspecific.

Suggestions

Replace generic verbs with concrete Faraday operations, e.g. 'Manage vulnerabilities, hosts, and findings; automate pentest workflows.'

Add natural trigger terms users say, such as 'vulnerabilities', 'pentest', 'security assessments', or 'findings'.

Tighten the what-clause so it conveys the actual capability (vulnerability management) rather than 'interact with Faraday data'.

Dimension	Reasoning	Score
Specificity	The description names the Faraday domain but its actions ('Manage data, records, and automate workflows') are generic with no concrete operations, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Faraday data'), so the 'Use when' cap at 3 does not apply; it is not a 5 because the what is vague and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	'Faraday' and 'Faraday data' are natural product-name keywords, but natural synonyms a pentester would actually say (vulnerabilities, pentest, hosts, findings) are absent, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Faraday' is a uniquely-named product giving a clear niche with the 'interact with Faraday data' trigger, but the generic 'manage data, records' verbs leave minor overlap risk with other 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/faradaysec/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.