Name: tribe-payments
Rating: 49.6 (1 reviews)
Author: membranedev

tribe-payments

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

Quality

53%

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

Quality

Content

50%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 CLI usage guidance is concrete and largely copy-paste ready, but the body is dominated by an enormous, non-actionable list of ~160 entity names that inflates tokens without value. Workflows for potentially destructive proxy/action calls lack validation checkpoints.

Suggestions

Remove or move the ~160-item entity bullet list into a separate reference file (or drop it entirely) — it adds tokens without actionable guidance.

Add a validation/verification step before running actions or proxy requests with destructive methods (e.g. confirm DELETE/PUT targets and check the response state before proceeding).

Replace the vague 'Use action names and parameters as needed' with a concrete example showing an action run with a real input payload.

Dimension	Reasoning	Score
Conciseness	The ~160-item bullet list of entity names (Customer, Transaction, ... Business Continuity Plan) is severe padding Claude cannot act on, and the intro restates what the product is; the CLI sections are lean, so overall it is noticeably verbose with padded sections rather than severely so.	2 / 5
Actionability	Copy-paste-ready commands are provided throughout (npm install, membrane login, connection ensure, action list/run, request) plus a concrete proxy-options table; minor gaps like placeholder CONNECTION_IDs and the vague 'Use action names and parameters as needed' keep it just below fully executable.	4 / 5
Workflow Clarity	The connection setup is sequenced with state-based branching and polling checkpoints, but proxy/action workflows that can issue destructive HTTP methods (DELETE) lack validation or verification steps, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The file is well sectioned with headers but is ~310 lines with no bundle references, and the large entity reference list that clearly belongs in a separate file is inlined; this matches the score-3 anchor of some structure with content that should be separate kept inline.	3 / 5
	Total	12 / 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 cleanly states both purpose and a 'Use when' trigger in third person, but its capability list is generic ('manage data, records, automate workflows') rather than concrete. Trigger coverage is adequate but lacks synonyms or varied phrasing.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete capabilities such as 'list transactions, issue refunds, manage payouts, and trigger webhooks'.

Broaden the trigger clause to include natural synonyms users might say, e.g. 'Use when the user wants to query Tribe Payments transactions, handle refunds or payouts, or automate payment workflows'.

Dimension	Reasoning	Score
Specificity	Names the domain (Tribe Payments) but the actions 'Manage data, records, and automate workflows' are minimal and generic rather than concrete capabilities, matching the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	Both 'what' (Tribe Payments integration managing data/records/workflows) and 'when' ('Use when the user wants to interact with Tribe Payments data') are present, but the 'when' could be more explicit/specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Tribe Payments data' provides a relevant natural trigger around the product name, but coverage is thin — missing common variations or synonyms users might say, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The named 'Tribe Payments' trigger carves a distinct niche with low conflict risk, but the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with adjacent payment/data skills, fitting the score-4 anchor.	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/tribe-payments/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.