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

cufinder

CUFinder integration. Manage data, records, and automate workflows. Use when the user wants to interact with CUFinder 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/cufinder/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 concrete, actionable CLI integration guide with executable commands and a well-sequenced connection workflow including validation via state polling. It loses points mainly for a marketing-style overview paragraph and minor structural loose ends (unlabeled Step 2).

Suggestions

Trim the B2B marketing overview paragraph ('It helps sales and marketing teams... grow their networks') down to a one-line functional description; Claude does not need the audience pitch.

Fix the 'Skip to Step 2' references by explicitly labeling the 'Searching for actions' / 'Running actions' section as Step 2, or restructure into a numbered step sequence.

Consider moving the full proxy-request flags table and action-listing details into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the opening overview paragraph ('It helps sales and marketing teams... grow their networks') and phrases like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude does not need.	3 / 5
Actionability	Provides many copy-paste executable commands (install, login, connection ensure, action run, request) plus a flags table; minor placeholders like QUERY and CONNECTION_ID keep it just short of fully copy-paste ready for common cases.	4 / 5
Workflow Clarity	Clear install→authenticate→connect→poll-for-ready→search→run sequence with state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loops; slightly loose 'Skip to Step 2' references without a clearly labeled Step 2.	4 / 5
Progressive Disclosure	Single file with well-organized section headers and an external docs link; no bundle files exist so references are trivially one-level, but at ~140 lines it exceeds the simple-skill threshold that would allow a 5.	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 clearly names the niche domain and provides an explicit 'Use when' trigger, with third-person voice throughout. The main weakness is that the capability list ('Manage data, records, and automate workflows') is generic rather than listing concrete CUFinder-specific actions.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete CUFinder-specific actions such as 'find and verify contact information, build lead lists, and manage records'.

Add a few natural trigger synonyms or surface terms (e.g., 'lead generation', 'contact verification', 'sales intelligence') so users describing the task in their own words still match.

Dimension	Reasoning	Score
Specificity	Names the domain (CUFinder) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract' or 'fill'; not comprehensive.	3 / 5
Completeness	Both the 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with CUFinder data') are present, but the 'what' is somewhat generic, keeping it below a 5.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'CUFinder' and 'CUFinder data' that a user would actually say, but offers no synonyms or variations beyond the proper noun.	3 / 5
Distinctiveness Conflict Risk	The 'CUFinder' trigger is a unique niche brand name with distinct triggers and minimal overlap risk with other skills.	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/cufinder/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.