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

campaignhq

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

Quality

64%

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

Quality

Content

72%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 concrete commands and a solid connection state-machine, but it loses workflow-clarity points for missing verification on destructive action/proxy flows and loses progressive-disclosure points for inlining a large reference table with no external file structure.

Suggestions

Add a verification checkpoint after destructive/batch actions, e.g. "After delete-campaign or send-transactional-email, re-run get-campaign / get-transactional-campaign to confirm the result before reporting success."

Move the 20-row Popular actions table into a separate ACTIONS.md and summarize the categories inline so SKILL.md stays an overview pointing one level deep.

Trim the opening "CampaignHQ is a software platform..." paragraph and the auth-plumbing editorializing; Claude can infer the product context.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, state tables, and a proxy-options table that earn their tokens, with only minor padding such as the opening product-description paragraph and editorializing like "so you can focus on the integration logic rather than auth plumbing." Matches the efficient-with-minor-trim anchor; not a 5 because those few explanatory sentences are removable.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end: install, login, connection ensure/get with --wait, action list/run with --input, proxy with a full flags table, plus a 20-row popular-actions table of real action keys. Matches the fully-executable anchor; placeholders like <actionId> are clearly marked.	5 / 5
Workflow Clarity	Connection setup has a clear state-driven sequence with checkpoints (ensure -> poll --wait -> branch on READY/CLIENT_ACTION_REQUIRED -> re-poll), but the action-run and proxy flows include destructive/batch operations (delete-campaign, send-transactional-email) with no verification step, so the destructive-operation cap holds. Not a 4 because that validation gap is explicit in the guidelines.	3 / 5
Progressive Disclosure	Headers organize the single self-contained file well, but there are no external references at all and the 20-row popular-actions table is inline reference material that could live in a separate file. Matches the some-structure / content-that-should-be-separate-is-inline anchor; not a 4 because there is no reference signaling or file split, and not a 2 because section structure is genuinely present.	3 / 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 cleanly states both what the skill does and when to use it, and the product name keeps it distinct, but the capability wording ("manage data, records, automate workflows") is generic and the trigger offers only a single product keyword with no natural variations.

Suggestions

Replace abstract verbs with concrete capabilities, e.g. "Manage contacts, lists, donations, and campaigns; run and schedule email sends."

Broaden the trigger with natural synonyms a user would say, e.g. "Use when the user wants to manage CampaignHQ contacts, send campaign emails, or query donation/list data."

Keep the third-person voice but make the what-clause enumerate the actual entities the skill exposes (contacts, lists, donations, tasks) rather than "data and records."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the CampaignHQ domain but the actions are generic abstractions rather than concrete capabilities, matching the anchor where actions are minimal or generic. Not a 1 because it does name real actions (manage, automate); not a 3 because those actions lack the concreteness of "extracts content"-level verbs.	2 / 5
Completeness	Both halves are present: "Manage data, records, and automate workflows" (what) and "Use when the user wants to interact with CampaignHQ data" (when), but the what is vague and the when is generic. Matches the anchor where both exist but when could be more specific; not a 5 because neither half is concrete and comprehensive.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with CampaignHQ data" supplies the one natural keyword (CampaignHQ) a user would say, but offers no synonyms or variations. Matches the anchor for some relevant keywords missing common variations; not a 4 because coverage is a single term with no breadth.	3 / 5
Distinctiveness Conflict Risk	The product name "CampaignHQ" forms a clear niche trigger unlikely to fire for unrelated skills, though the surrounding "data, records, workflows" phrasing is generic. Fits mostly-distinct with minor overlap risk; not a 5 because the trigger leans on the brand name rather than distinct concrete capability phrases.	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/campaignhq/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.