Name: referralrock
Rating: 60 (1 reviews)
Author: membranedev

referralrock

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

Quality

70%

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/referralrock/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, built around executable Membrane CLI commands and a well-sequenced connection workflow with explicit state-based validation. Its weaknesses are mild verbosity (product overview, a repeated command, vague filler) and the absence of validation guidance for destructive action/proxy calls.

Suggestions

Trim the opening paragraph explaining what ReferralRock is and remove the duplicated action-list command under 'Popular actions', which already appears in 'Searching for actions'.

Add a validation/checkpoint note before destructive operations (e.g., 'Confirm the action is non-destructive or dry-run proxy DELETE/PUT calls before committing') to lift workflow clarity.

Replace the filler line 'When to use which actions: Use action names and parameters as needed.' with concrete guidance on choosing between pre-built actions and the proxy.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient, executable CLI commands, but the intro paragraph explains what ReferralRock is (a concept Claude can infer), the 'Popular actions' section repeats the action-list command already shown, and filler like 'When to use which actions: Use action names and parameters as needed.' adds little, so it is mostly efficient with some tightening needed.	3 / 5
Actionability	The body is dominated by copy-paste-ready commands (install, login, connection ensure/get, action list/run, request) plus a complete flag-options table, fully executable and covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced (install, login, ensure, poll until ready) with explicit validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (re-poll after user action); the gap is that running or proxying potentially destructive actions has no validation step, keeping it just below a 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in one well-organized SKILL.md with clear section headers and one external docs link; structure is good and navigation is easy, but at ~130 lines of inline content it is longer than the simple-skill case that would score 5, leaving minor organization gaps.	4 / 5
	Total	16 / 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 successfully states both what the skill does and when to use it, anchored by a distinctive product name that limits conflict risk. Its main weakness is generic action language ('manage data, records') and trigger phrases that lack concrete variations users would naturally say.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete ReferralRock operations such as 'create and manage referral programs, members, and rewards'.

Expand the 'Use when' clause with natural trigger phrases like 'referral programs', 'member referrals', or 'payout rewards' to improve trigger-term coverage.

Mention specific ReferralRock objects (Member, Referral, Reward, Contact) to sharpen distinctiveness and specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (ReferralRock) plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete operations, matching the anchor that lists 1-2 actions without being comprehensive.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with ReferralRock data') are present and explicit, but the 'when' clause is somewhat generic rather than listing concrete trigger phrases, fitting the anchor just below a 5.	4 / 5
Trigger Term Quality	The brand name 'ReferralRock' is the natural trigger and appears repeatedly, but common variations like 'referrals', 'referral program', or 'reward' are missing, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The product-specific name 'ReferralRock' creates a clear niche with distinct triggers and minimal conflict risk with other skills, matching the anchor for a clear niche.	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/referralrock/SKILL.md
Commit: f484c82

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