Name: faraday
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

faraday

Faraday integration. Manage Organizations. Use when the user wants to interact with Faraday data.

Quality

65%

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

Quality

Content

67%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 strong, actionable reference with concrete commands, a populated action table, and a sensible connection-state workflow with validation loops. Its main weaknesses are mild verbosity in the overview sections and a broken 'Step 2' cross-reference.

Suggestions

Trim the "Faraday Overview" bullet list and introductory platform paragraph to remove concepts Claude already knows or that do not drive action.

Fix the 'skip to Step 2' reference by either adding an explicit 'Step 2' header or rewording to 'skip to Searching for actions'.

Consider moving the large 'Popular actions' table into a references/ file (e.g. ACTIONS.md) once bundle files are supported, keeping only a few key examples inline.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient command-and-table reference, but the "Faraday Overview" bullet list and the introductory platform description explain concepts/actions Claude does not need, fitting 'mostly efficient but includes some unnecessary explanation that could be tightened'; it is not 4 because several padded sections remain.	3 / 5
Actionability	The body gives concrete, mostly copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus a populated actions table, matching 'mostly executable guidance with minor gaps'; it is not 5 because placeholders like CONNECTION_ID and some assumed context prevent full copy-paste coverage.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-state → search → run sequence with validation checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after user action), but cross-references like 'skip to Step 2' with no matching Step 2 header create a minor navigation gap, fitting anchor 4 over 5.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections with no bundle files to reference, but at ~165 lines the large inline 'Popular actions' table is content that could live in a separate reference file, fitting 'good structure; minor organization gaps' rather than the fully-split anchor 5.	4 / 5
	Total	15 / 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 is functional, naming a specific platform and providing a 'Use when' clause so both what and when are covered. It is held back by a single named action and generic trigger phrasing that lacks concrete synonyms a user would naturally say.

Suggestions

List more concrete capabilities (e.g. 'Manage Organizations, findings, hosts, and vulnerabilities') to raise specificity beyond one action.

Expand the trigger clause with natural phrases users say, e.g. 'Use when the user wants to query Faraday vulnerabilities, findings, hosts, or pentest data'.

Keep third-person voice but make the 'when' more specific so it doubles as a distinctiveness signal.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Faraday integration") and one concrete action ("Manage Organizations"), matching the anchor for naming a domain plus 1-2 actions without comprehensive coverage; it is not score 2 because a specific action is named, and not 4 because only one action is listed.	3 / 5
Completeness	Both a 'what' ("Faraday integration. Manage Organizations.") and a 'when' ("Use when the user wants to interact with Faraday data.") are present, but the 'when' is generic rather than tied to concrete trigger phrases, matching the anchor where both exist yet 'when' could be more explicit.	4 / 5
Trigger Term Quality	Relevant keywords ("Faraday", "Faraday data") and a natural phrase ("interact with Faraday data") appear, but common variations or synonyms (e.g. vulnerabilities, pentest findings, security assessments) are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Faraday" names a specific platform giving it a clear niche with minimal conflict risk, but the thin trigger wording leaves minor overlap risk with other Faraday-related skills, fitting 'mostly distinct; minor overlap risk' better than the fully distinctive anchor 5.	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/faraday/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.