Name: cross-river
Rating: 59.2 (1 reviews)
Author: membranedev

cross-river

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

Quality

68%

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/cross-river/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 content is highly actionable with copy-paste CLI commands and a well-sequenced, state-checked connection flow, but it carries an unnecessary company-background paragraph and has broken step numbering that slightly hurts workflow and navigation clarity. Trimming the background and fixing the step labels would push it higher.

Suggestions

Delete or compress the opening company-background paragraph; Claude does not need Cross River's corporate description to use the CLI.

Fix the step numbering: either label the 'Searching for actions' section as 'Step 2' or reword 'skip to Step 2' to reference the actual section name, and reconcile the orphaned '1b' heading.

Add a brief output-verification note for action runs and proxy requests (e.g. check the `output`/`error` fields and HTTP status before treating a result as success).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable guidance, but the opening company-background paragraph ('Cross River is a technology infrastructure company that offers banking-as-a-service...') and a few rhetorical phrases ('so you can focus on the integration logic rather than auth plumbing') explain context Claude does not need, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	The body provides copy-paste-ready commands for every common case — install, login, connection ensure/get with --wait, action list/run with --input, and request with a full flags table — fully executable and covering the main flows, matching the top anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-act-repoll feedback loop, but it references an undefined 'Step 2' and uses an orphaned '1b' label, and the action/proxy sections lack output-verification guidance, matching the 'clear sequence with minor validation gaps' anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the single-file body is well organized into clearly signaled sections with an external docs link, but the broken step numbering ('Step 2', '1b') is a minor organization gap, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor.	4 / 5
	Total	16 / 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 answers both what and when and is anchored to a distinct brand, but its action verbs are generic and its trigger coverage relies almost entirely on the brand name. Tightening the actions to concrete capabilities and adding a few natural trigger phrases would raise it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Cross River capabilities such as 'create contacts, manage deals, send SMS/emails, and run workflow actions'.

Expand the 'Use when...' trigger with natural phrases a user would say, e.g. 'Use when working with Cross River contacts, deals, tasks, or invoices, or when automating Cross River workflows'.

Add a synonym or two beyond the bare brand name (e.g. 'Cross River API', 'Cross River banking-as-a-service') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the Cross River domain and lists several actions ('Manage data, records, and automate workflows'), but those verbs on abstract nouns are generic rather than concrete like 'fill forms' or 'convert pages', matching the anchor that names the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Cross River data') are explicitly present, but the 'when' is somewhat circular and could be more specific, matching the anchor where both exist yet the trigger could be sharper.	4 / 5
Trigger Term Quality	The natural keyword is essentially the brand 'Cross River' repeated as 'Cross River data', with no synonyms or variations; coverage is relevant but thin, matching the anchor where some keywords are present but common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The brand anchor 'Cross River' makes it mostly distinct with low conflict risk, though the generic action phrasing ('manage data, records') leaves minor overlap with CRM-style skills, matching the 'mostly distinct; minor overlap' anchor.	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/cross-river/SKILL.md
Commit: f484c82

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