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

Blog Docs Log in Get started

campay

CamPay integration. Manage data, records, and automate workflows. Use when the user wants to interact with CamPay 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/campay/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 highly actionable, well-structured guide with executable commands and a clear connection-state workflow. Its main drawbacks are some over-explanation, a misleading Apple Pay docs link, and lightly-specified error-recovery paths.

Suggestions

Remove or fix the "Official docs" link pointing at Apple Pay, which is unrelated to CamPay.

Trim the opening paragraph explaining what CamPay is; Claude does not need the business-domain primer to run CLI commands.

Flesh out the CONFIGURATION_ERROR / SETUP_FAILED branch with a concrete recovery step (e.g. inspect the `error` field and re-run `membrane connection ensure`).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows (a paragraph defining what CamPay is) and an irrelevant/wrong "Official docs: https://developer.apple.com/apple-pay/" link that adds noise.	3 / 5
Actionability	It provides concrete, executable `membrane` commands with flags and JSON examples for connection, action search, running actions, and proxying, with only minor gaps such as unexplained CONNECTION_ID placeholders and the broken Apple Pay docs URL.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED) and a poll-until-ready feedback loop, though validation guidance for the CONFIGURATION_ERROR / SETUP_FAILED failure paths is only lightly sketched.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references and no bundle files to misroute, but it is a single monolithic file with no extraction of the large clientAction reference table into a separate document.	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 correctly states both what the skill does and when to use it, anchored to a distinct CamPay niche. Its weakness is generic action verbs ("manage data/records, automate workflows") and thin trigger-term coverage that lack concrete payment-domain keywords.

Suggestions

Replace generic verbs with concrete CamPay actions, e.g. "Search payments, list invoices, and manage CamPay accounts and recipients."

Broaden the trigger with natural user phrasings such as "Use when the user wants to query CamPay payments, invoices, or campground booking transactions."

Drop the vague "Manage data, records, and automate workflows" which could describe almost any integration skill.

Dimension	Reasoning	Score
Specificity	The description names the CamPay domain and three actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete payment-specific operations, so it stops at domain-plus-1-2-actions rather than comprehensive coverage.	3 / 5
Completeness	It provides both a "what" (manage data, records, automate workflows) and an explicit "when" clause ("Use when the user wants to interact with CamPay data"), though the trigger could be more specific and concrete.	4 / 5
Trigger Term Quality	It includes "Use when the user wants to interact with CamPay data" which is a natural trigger, but coverage is limited to repeated "CamPay data" phrasing with no synonyms or concrete terms (payments, invoices, bookings) a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	The CamPay anchor carves out a clear niche with minimal conflict risk, though the generic "manage data, records, and workflows" framing leaves minor overlap with adjacent data-management skills.	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/campay/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.