Name: partnerstack
Rating: 60.8 (1 reviews)
Author: membranedev

partnerstack

PartnerStack integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with PartnerStack data.

Quality

71%

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/partnerstack/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 body is an efficient, actionable CLI guide with concrete commands, a flags table, and a connection-state feedback loop. Main weaknesses are inconsistent step numbering and minor over-explanation in the intro and auth prose.

Suggestions

Fix the dangling "skip to Step 2" reference by labeling the downstream section (Searching for actions) as Step 2, and renumber 1b consistently.

Trim the opening paragraph and "so you can focus on the integration logic rather than auth plumbing" to assume Claude's competence.

Add one complete end-to-end example (connect -> discover action -> run with a real --input payload) to make actionability copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and flag tables, with only minor trimmable prose (the intro paragraph on what PartnerStack is and "so you can focus on the integration logic rather than auth plumbing"), fitting anchor 4.	4 / 5
Actionability	Concrete copy-paste commands cover the common cases (login, connection ensure, action list/run, request with full flag table); it falls at anchor 4 rather than 5 because examples use placeholders and lack a complete end-to-end run with real values.	4 / 5
Workflow Clarity	The connection flow has a real feedback loop (ensure -> check state -> poll --wait -> handle clientAction -> poll again), but the "skip to Step 2" reference points to no clearly labeled Step 2 and section numbering (1b) is inconsistent, leaving minor gaps at anchor 4.	4 / 5
Progressive Disclosure	Content is well-organized with clear ##/###/#### headers in a single file with no bundle references; the detailed clientAction spec and proxy flags table could arguably live in reference files, but inline placement is reasonable for a CLI guide, matching anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

67%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 answers both what and when with a concrete entity list and an explicit Use-when clause, but relies on a single generic verb and omits several natural PartnerStack trigger terms. It is clearly distinct as a named-platform integration with only minor overlap risk.

Suggestions

Vary the action verbs beyond the single "Manage" (e.g., "Create and update Leads, track Deals, issue Rewards") to raise specificity.

Add natural PartnerStack terms users actually say — partners, affiliates, referrals, payouts, deals — to the trigger clause.

Tighten the when-clause to name the platform more specifically, e.g. "Use when the user wants to manage PartnerStack partnerships, leads, or payouts."

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Leads, Projects, Users, Goals, Filters" lists six concrete resource types, giving broad coverage of the domain; the single generic verb "Manage" is the only gap versus anchor 5's multiple distinct action verbs.	4 / 5
Completeness	Both halves are present: "Manage Organizations, Leads, Projects, Users, Goals, Filters" (what) and "Use when the user wants to interact with PartnerStack data" (when); the when-clause is explicit but the trigger phrase is somewhat generic, so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	The trigger "interact with PartnerStack data" plus entity names (Leads, Projects, Goals) provides some natural keywords, but core PartnerStack concepts users would say (partners, affiliates, referrals, payouts) are missing, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	"PartnerStack integration" is a clear named-platform niche with minimal conflict risk, but generic entity names (Users, Goals, Projects, Filters) create minor overlap with other CRM/project skills, placing it at anchor 4.	4 / 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/partnerstack/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.