Name: rewardful
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

rewardful

Rewardful integration. Manage Affiliates, Products. Use when the user wants to interact with Rewardful data.

Quality

72%

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/rewardful/SKILL.md

Quality

Content

82%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 well-structured with executable commands and a real polling/feedback loop for connection state. Its main weaknesses are minor verbosity, a broken 'Step 2' cross-reference, and no use of external reference files for bulkier detail.

Suggestions

Remove or relocate the opening marketing paragraph ('Rewardful is a SaaS platform...') since it explains background Claude does not need.

Fix the dangling 'Step 2' references by adding a matching 'Step 2' heading or rewriting the jumps to point to 'Searching for actions'.

De-duplicate the discovery command shown in both 'Searching for actions' and 'Popular actions', and consider moving the proxy flags table and clientAction state machine into a separate reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight and command-focused with a compact flags table, but the opening marketing paragraph and the duplicated discovery command in 'Popular actions' are trimmable padding.	4 / 5
Actionability	It provides copy-paste-ready executable commands throughout (install, login, connection ensure, action run with JSON input) plus a clear proxy flags table covering the common cases.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run→proxy sequence exists with a genuine connection-state feedback loop, but the dangling 'Step 2' references and lack of a final success-validation checkpoint are minor gaps.	4 / 5
Progressive Disclosure	Section headers are clean and well-organized with nothing buried, and no bundle files exist to reference; however the inline proxy flags table and clientAction state machine could be split into separate files, and there are no one-level-deep references at all.	4 / 5
	Total	17 / 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 successfully covers both what the skill does and when to use it, anchored to a distinct named application. It is held back by thin action specificity and generic trigger phrasing that lacks common synonyms.

Suggestions

Expand the action list beyond a single 'Manage' verb to concrete operations like 'create, update, and list Affiliates, Commissions, and Referrals'.

Add natural trigger synonyms such as 'referral programs', 'affiliate links', 'commissions', and 'payouts' so users' varied phrasing matches.

Tighten the 'when' clause with concrete triggers, e.g. 'Use when the user wants to manage affiliates, referrals, commissions, or payouts in Rewardful.'

Dimension	Reasoning	Score
Specificity	Names the Rewardful domain and concrete entities ('Manage Affiliates, Products') but only offers one verb covering two nouns, so it lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both what ('Rewardful integration. Manage Affiliates, Products.') and when ('Use when the user wants to interact with Rewardful data.'), though the trigger clause is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	'Rewardful', 'Affiliates', and 'Products' are relevant keywords users would say, but common synonyms like 'referral', 'affiliate programs', and 'commissions' are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS 'Rewardful' gives a clear niche with minimal conflict risk, but the generic 'interact with Rewardful data' trigger and thin entity list leave minor overlap risk with sibling integration skills.	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/rewardful/SKILL.md
Commit: f484c82

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