Name: campayn
Rating: 60 (1 reviews)
Author: membranedev

campayn

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

Quality

70%

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

Quality

Content

82%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 content is a well-structured, highly actionable CLI integration guide with executable commands and a strong connection-state feedback loop. Its main weaknesses are minor: a little marketing-fluff padding, an orphaned 'Step 2' reference, and bulk reference material kept inline rather than split into bundle files.

Suggestions

Trim the opening marketing paragraph and the 'so you can focus on the integration logic rather than auth plumbing' aside to reduce padding.

Fix the broken 'Step 2' cross-references by either labeling the 'Searching for actions' section as Step 2 or removing the dangling references.

Consider moving the popular-actions table and the clientAction field breakdown into a references/ file, keeping SKILL.md as a lean overview that links one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, but the marketing-style intro ('designed to help small businesses...engage with their audience') and 'so you can focus on the integration logic rather than auth plumbing' are minor over-explanation that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste ready commands throughout (connection ensure, action list/run with --input JSON, request proxy) plus a concrete popular-actions table covering common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with explicit state validation and feedback loops (READY/CLIENT_ACTION_REQUIRED/poll-again), but references to a nonexistent 'Step 2' and absent post-run validation are minor gaps, matching 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	With no bundle files, the single SKILL.md is well-sectioned with clear headers and easy navigation, but at ~150 lines (above the simple-skill threshold) bulk inline material like the popular-actions table and clientAction field breakdown is not split into references, matching 'good structure; minor organization gaps'.	4 / 5
	Total	17 / 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 answers both 'what' and 'when' and is anchored to a distinct named product, but its capability language is generic and its trigger terms lack the natural feature vocabulary users would actually say. Tightening the action list and adding concrete Campayn trigger phrases would lift it from mid-range to strong.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Campayn capabilities such as 'create and send email campaigns, manage contacts and lists, and retrieve signup forms'.

Expand trigger terms to natural user phrases like 'email campaigns, contact lists, newsletters, or signup forms in Campayn' so the skill surfaces for real-world requests.

Keep the explicit 'Use when...' clause but bind it to specific Campayn tasks rather than the abstract 'interact with Campayn data'.

Dimension	Reasoning	Score
Specificity	It names the Campayn domain but the listed actions ("Manage data, records, and automate workflows") are generic abstractions rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both 'what' ("Campayn integration. Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Campayn data") are present, but the 'when' could be more concrete, matching the 'has both what and when; when could be more specific' anchor.	4 / 5
Trigger Term Quality	The trigger clause surfaces essentially only "Campayn"/"Campayn data" as keywords and omits natural feature terms a user would say (email campaigns, contacts, lists, newsletters), matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named product "Campayn" gives a clear niche with minimal conflict risk, but the boilerplate 'Manage data, records, and automate workflows' mirrors sibling integration skills, creating minor overlap, matching the 'mostly distinct; minor overlap risk' 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/campayn/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.