Name: paykickstart
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

paykickstart

Paykickstart integration. Manage Campaigns. Use when the user wants to interact with Paykickstart data.

Quality

65%

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

Quality

Content

67%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 a strong, actionable integration guide with concrete CLI commands, a clear connection workflow, and state-based validation checkpoints. Its main weaknesses are mild verbosity (over-explaining the platform and Membrane) and inline content that could be split into reference files.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete commands, but includes some unnecessary explanation Claude could infer (the opening "PayKickstart is a shopping cart..." overview and padded sentences like "This is the fastest way to get a connection"), so it is not lean enough for a 4.	3 / 5
Actionability	Concrete, executable `membrane` CLI commands appear throughout with a flags table and parameter examples; it falls just short of 5 because examples rely on placeholders (CONNECTION_ID) with no fully copy-pasteable end-to-end run.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, but a couple of validation gaps (no explicit 're-poll until READY' feedback loop wording) keep it below a 5.	4 / 5
Progressive Disclosure	The single-file skill is well-organized with clear section headers, but sizable inline content (the full proxy-flags table and nested clientAction fields) could be split into reference files; no bundle files exist, so structure is good with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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 an explicit 'Use when' trigger and names a specific platform niche, but it is generic and surface-level — naming only one entity (Campaigns) and offering thin trigger phrases. Tightening the action list and trigger keywords would lift it toward the top anchors.

Suggestions

Expand the capability list beyond "Manage Campaigns" to the other entities the skill covers (orders, customers, subscriptions, coupons) for specificity.

Replace the generic "interact with Paykickstart data" trigger with concrete phrases users would say (e.g. "Use when creating Paykickstart campaigns, fetching orders, or managing subscriptions").

Add file-extension or API-named keywords (e.g. paykickstart.com, getfunnel) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Manage Campaigns"), but the action is thin and only one of many entity types is mentioned, so it is not comprehensive; not a 4 because it lacks several specific actions.	3 / 5
Completeness	Both a 'what' ("Paykickstart integration. Manage Campaigns.") and an explicit 'when' clause are present, but the 'when' is generic ("interact with Paykickstart data") rather than listing concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Paykickstart data" includes the platform name but only generic keywords; it misses common variations, synonyms, or specific entity terms (campaigns, orders, subscriptions) users would actually say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform Paykickstart gives it a clear niche with minimal conflict risk, but the generic wording ("interact with Paykickstart data") leaves minor overlap risk versus other integration skills, so it is mostly distinct rather than fully clear.	4 / 5
	Total	14 / 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/paykickstart/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.