Name: partnerize
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

partnerize

Partnerize integration. Manage Organizations. Use when the user wants to interact with Partnerize data.

Quality

63%

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

Quality

Content

68%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 highly actionable with executable commands and a solid connection-state feedback loop, but it is held back by mild redundancy, background fluff, and broken step numbering that fragments the workflow. It is a strong, practical skill reference with modest polish gaps.

Suggestions

Fix the workflow numbering: define Step 1/Step 2 explicitly or remove the "skip to Step 2" and "1b" references so the sequence is unambiguous.

Trim the opening Partnerize marketing paragraph and fold the redundant "Popular actions" section into "Searching for actions" to reduce token overhead.

Add a short validation note for `action run` results (e.g. check the `output` field for errors before reporting success) to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening Partnerize overview paragraph and the redundant "Popular actions" section (which repeats the earlier `action list --intent=QUERY` command) add unnecessary tokens.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands across install, auth, connection, action search/run, JSON input, and proxy usage with a concrete options table, covering the common cases.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence exists and the connection-state polling loop is a genuine feedback loop, but "skip to Step 2" references an undefined Step 2 and "1b" appears with no 1a, leaving checkpoints implicit and numbering broken.	3 / 5
Progressive Disclosure	With no bundle files, the single-file CLI guide is well-organized under clear section headers with no nested references, though minor organization gaps (broken step numbering, a redundant section) keep it just below the top anchor.	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 correctly pairs a what/when structure and leverages a distinct proper noun, but its capability list is minimal and the trigger phrasing could be richer. It is solid but leaves specificity on the table.

Suggestions

Replace the generic "Manage Organizations" with concrete capabilities, e.g. "Manage campaigns, creatives, transactions, and commission rules in Partnerize."

Expand the trigger clause with natural user phrases and synonyms, e.g. "Use when the user wants to query Partnerize campaigns, transactions, or partnership data."

Keep the third-person imperative voice but add 1-2 more concrete actions to lift specificity toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Partnerize integration") and a single generic action ("Manage Organizations"), but provides no concrete specific capabilities — matching the anchor where actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Partnerize integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Partnerize data.") are present, though the "what" is thin and the trigger could be more specific.	4 / 5
Trigger Term Quality	Relevant keywords ("Partnerize", "Organizations", "Partnerize data") are present, but coverage lacks common variations or synonyms beyond the proper noun, fitting the partial-keyword anchor.	3 / 5
Distinctiveness Conflict Risk	The proper noun "Partnerize" gives the skill a distinct niche with low conflict risk, though the generic "Manage Organizations" phrase introduces minor overlap with other admin-style 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/partnerize/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.