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

broadridge

Broadridge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Broadridge 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/broadridge/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 well-structured, highly actionable CLI integration guide with concrete commands and good connection-state feedback loops. The main weaknesses are minor verbosity (company intro, duplicated action-list examples) and a few dangling step references.

Suggestions

Trim or remove the opening 'Broadridge is a financial technology company...' paragraph, which explains context Claude does not need for the integration task.

Consolidate the 'Searching for actions' and 'Popular actions' sections so the `action list` syntax appears once with a single canonical example.

Fix the broken sequence references: label the post-connection section as 'Step 2' explicitly or add the missing '1a' so 'skip to Step 2' and '1b' resolve correctly.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused, but it opens with a Broadridge company description Claude does not need and repeats the `action list` invocation with different syntax in both 'Searching for actions' and 'Popular actions', which is unnecessary padding.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connection ensure, action run, request) with consistent `--json` output and a flags table, placing it at 'mostly executable guidance with minor gaps' rather than fully comprehensive due to unsubstituted placeholders like CONNECTION_ID and QUERY.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear and the connection-state polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) is an explicit feedback loop, but dangling references to 'Step 2' and a '1b' subsection without a matching '1a' leave minor sequencing gaps.	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear ## / ### section headers and no nested references, which is appropriate for a CLI integration skill; it stops short of level 5 only because there is no content split or signaled reference structure to navigate.	4 / 5
	Total	15 / 20 Passed

Description

66%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 specific to a niche vendor with an explicit 'Use when' trigger, so completeness and distinctiveness are strong. Weaknesses are the generic action verbs and the single narrow trigger phrase with no keyword variations.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Manage client accounts and documents, search and run Broadridge actions, and automate workflows' to lift specificity.

Broaden the trigger clause with several natural phrases, e.g. 'Use when the user wants to interact with Broadridge data, manage Broadridge client records, or automate Broadridge workflows.'

Consider adding related Broadridge-domain terms (e.g. investor communications, client onboarding) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Broadridge domain plus several action areas ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations, fitting the '1-2 concrete actions, not comprehensive' anchor better than the fully vague or fully specific neighbors.	3 / 5
Completeness	It states what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Broadridge data') explicitly, but the 'when' clause is a single narrow trigger rather than a set of concrete trigger phrases, so it falls just below the level-5 anchor.	4 / 5
Trigger Term Quality	'Broadridge' is the natural keyword a user would say, and the trigger 'Use when the user wants to interact with Broadridge data' is reasonable, but coverage is narrow with no synonyms, variations, or related product terms, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Broadridge' is a specific named financial vendor with a clear niche and distinct triggers, giving minimal conflict risk with any other skill.	5 / 5
	Total	15 / 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/broadridge/SKILL.md
Commit: f484c82

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