Name: cybersource
Rating: 52.8 (1 reviews)
Author: membranedev

cybersource

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/cybersource/SKILL.md

Quality

Content

63%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 actionable and the connection workflow is well-sequenced with state handling and a polling loop, but it is held back by some restated background knowledge and a monolithic structure with no reference files to offload the CLI and proxy detail.

Suggestions

Trim or remove the opening 'CyberSource is a payment management platform...' paragraph and the agent-types aside; assume Claude knows the product and focus on the integration mechanics.

Move the proxy request flag table and full connection-state reference into a separate REFERENCES.md (or similar) and link to it one level deep, so the overview stays lean.

Add an explicit validate-fix-retry checklist for the SETUP_FAILED / CONFIGURATION_ERROR states to elevate the workflow from a strong 4 toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the introductory paragraph and overview restate what CyberSource is (a concept Claude already knows) and the agent-types line adds tangential detail that does not earn its tokens.	3 / 5
Actionability	It provides concrete, copy-pasteable CLI commands for install, login, connection ensure, action list/run, and proxy requests with a clear flag table, covering the common cases with only minor gaps (e.g. no example of parsing the JSON output).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with a READY fast-path, a 1b polling branch, and explicit state-by-state guidance (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), including a re-poll feedback loop; it is short of a 5 only because re-auth/retry on SETUP_FAILED is described but not turned into an explicit validate-fix-retry checklist.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are empty) and the body is a single monolithic overview that inlines the full CLI reference and proxy flag table rather than splitting them into one-level-deep reference files.	3 / 5
	Total	14 / 20 Passed

Description

53%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 anchored to a specific product (CyberSource) which keeps conflict risk low, but the capabilities are generic and the trigger vocabulary misses the payment-oriented terms users would actually say. It answers what and when but only at a surface level.

Suggestions

Add concrete CyberSource-specific actions to the description, e.g. 'process payments, manage subscriptions, and handle fraud screening' instead of the generic 'Manage data, records, and automate workflows'.

Expand the 'Use when' clause with natural payment triggers users would say, e.g. 'Use when the user wants to process or refund a payment, manage subscriptions, or query CyberSource transactions'.

Replace abstract verbs ('Manage data, records') with the platform's actual entities (Payment, Customer, Subscription, Payment Instrument) to sharpen specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (CyberSource integration) and two concrete action classes ('Manage data, records' and 'automate workflows'), but these are generic verbs rather than specific CyberSource capabilities like payments, fraud, or subscriptions.	3 / 5
Completeness	It states a clear 'what' (CyberSource integration, managing data/records, automating workflows) and includes a 'Use when' clause, but the 'when' is narrow ('interact with CyberSource data') and omits the payment/subscription triggers that define the skill.	3 / 5
Trigger Term Quality	'CyberSource' and 'CyberSource data' are the only natural terms; common user phrases such as 'payments', 'process a payment', 'subscriptions', or 'fraud' that would actually trigger this skill are absent.	3 / 5
Distinctiveness Conflict Risk	'CyberSource' is a named product niche with distinct triggers, so overlap with other skills is low; the generic 'Manage data, records, and automate workflows' phrasing creates only minor broadness.	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/cybersource/SKILL.md
Commit: f484c82

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