Name: tapfiliate
Rating: 69.6 (1 reviews)
Author: membranedev

tapfiliate

Tapfiliate integration. Manage Affiliates, Referrals, Conversions, Programs, Invoices. Use when the user wants to interact with Tapfiliate data.

Quality

85%

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

Quality

Content

92%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.

A well-structured, highly actionable skill body built around concrete CLI commands and a clear connection workflow with validation checkpoints. Its only weakness is minor verbosity in a few introductory and best-practice sentences.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and a compact flag table, but includes a few sentences of mild over-explanation (the opening SaaS description of Tapfiliate and some restated best-practice rationale) that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready `membrane` CLI commands cover the common cases — install, login (interactive and headless), connection ensure/wait, action list/run, and proxy requests — with flags documented in a table.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit validation checkpoints and feedback loops: ensure -> poll with `--wait` until not `BUILDING` -> branch on `READY` / `CLIENT_ACTION_REQUIRED` / `CONFIGURATION_ERROR` / `SETUP_FAILED` -> re-poll after the user acts -> then search and run actions.	5 / 5
Progressive Disclosure	The skill ships no bundle files and keeps everything in a single well-organized SKILL.md with clear section headers and one-level structure; there are no nested references to inline, satisfying the no-external-references case.	5 / 5
	Total	19 / 20 Passed

Description

78%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.

A solid, third-person description that names a specific platform and several concrete objects it manages, with an explicit 'Use when' trigger clause. It would reach the top level by varying its action verbs and making the 'when' trigger more concrete with specific user phrases.

Suggestions

Replace the single repeated verb 'Manage' with varied concrete actions (e.g. 'create, approve, and pay out affiliates; track referrals; export conversions and invoices').

Make the 'Use when' clause more concrete by listing specific user intents, e.g. 'Use when the user wants to create affiliates, track referrals, approve commissions, or pull Tapfiliate invoices and payouts.'

Add common synonyms / variations a user might say ('affiliate program', 'referral payouts', 'commission tracking') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Tapfiliate domain plus several concrete objects to manage ('Affiliates, Referrals, Conversions, Programs, Invoices'), though the actions are mostly a single repeated verb ('Manage') rather than varied concrete verbs, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both what ('Manage Affiliates, Referrals, Conversions, Programs, Invoices') and when ('Use when the user wants to interact with Tapfiliate data'), but the 'when' clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural terms a user would say ('Tapfiliate', 'Affiliates', 'Referrals', 'Conversions', 'Invoices'), giving good keyword coverage, but lacks synonyms and file-extension-style variations that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	Naming the specific platform 'Tapfiliate' with its distinct affiliate-marketing triggers gives it a clear niche with minimal risk of activating for the wrong skill.	5 / 5
	Total	17 / 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/tapfiliate/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.