Name: cj-affiliate
Rating: 55.2 (1 reviews)
Author: membranedev

cj-affiliate

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

Quality

62%

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/cj-affiliate/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 body is a well-structured, actionable Membrane CLI guide with a genuinely useful connection-state feedback loop. Its main weaknesses are minor redundancy between the action-discovery sections and some introductory padding that could be trimmed.

Suggestions

Remove the duplicated action-discovery command — keep it in one place ('Popular actions') and reference it from 'Searching for actions' instead of restating it.

Tighten or cut the opening 'CJ Affiliate is a large affiliate marketing network...' paragraph, which restates domain background Claude largely already knows.

Label the post-connection section as 'Step 2: Search and run actions' so the 'skip to Step 2' references resolve, and add a brief verification note (e.g. check the `output` field / HTTP status) after running actions or proxy requests.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands with brief explanations, but the opening 'CJ Affiliate is a large affiliate marketing network...' paragraph and the duplicated action-discovery command in both 'Searching for actions' and 'Popular actions' add unnecessary explanation, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the redundancy and introductory padding are noticeable.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) with a clear flags table and copy-paste-ready syntax, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; it is not 5 because placeholders like CONNECTION_ID and actionId require the user to fill them in and a worked end-to-end example is absent.	4 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with an explicit state machine (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-and-recheck feedback loop, matching 'Clear sequence with most checkpoints present; minor validation gaps'; it is not 5 because the 'Step 2' reference is never labeled as such and running/proxy steps lack a validation checkpoint.	4 / 5
Progressive Disclosure	As a single-file CLI guide with no bundle files, it is well-organized into clear sections (Overview, Working with CJ Affiliate, Popular actions, Best practices) and has no nested references, fitting 'Good structure; most content appropriately placed'; it is not 5 because, at ~143 lines, the proxy-flag table and connection state-machine detail could arguably live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 successfully pairs a clear 'Use when' trigger with a named, distinctive platform, but its capability list is generic rather than concrete. Tightening the action verbs and adding natural synonyms would raise both specificity and trigger coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete CJ Affiliate capabilities such as 'pull advertiser and reporting data, manage links and products, automate commission workflows'.

Add natural synonyms and surface terms users actually say, e.g. 'commissions', 'advertisers', 'publishers', 'affiliate links', so the trigger fires on varied phrasings.

Keep the explicit 'Use when...' clause but make the trigger more specific, e.g. 'Use when the user wants to query CJ Affiliate reporting, manage advertiser links, or automate commission workflows.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('CJ Affiliate integration') but its actions — 'Manage data, records, and automate workflows' — are generic and not concrete, matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no truly concrete capability (e.g. 'pull advertiser reports', 'create links') is named.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with CJ Affiliate data') are present and explicit, matching 'Has both what and when; when could be more explicit or specific'; it is not 5 because the 'what' is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural brand term 'CJ Affiliate' and 'interact with CJ Affiliate data', but lacks synonyms or common variations users might say, fitting 'Some relevant keywords but missing common variations or synonyms'; it is not a 4 because keyword coverage beyond the brand name is thin.	3 / 5
Distinctiveness Conflict Risk	Naming the specific CJ Affiliate platform gives it a clear niche with low conflict risk, fitting 'Mostly distinct; minor overlap risk'; it is not 5 because the generic 'manage data, records, automate workflows' phrasing could overlap with other integration skills.	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/cj-affiliate/SKILL.md
Commit: f484c82

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