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

wildapricot

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

Quality

Content

76%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 highly actionable with comprehensive executable commands and a well-structured connection workflow, but workflow clarity is capped by an undefined 'Step 2' reference and missing validation steps for destructive operations. Minor conciseness gains are available in the intro and entity list.

Suggestions

Define 'Step 2' explicitly (e.g. label 'Searching for actions' as Step 2) or remove the dangling step references so the connection-to-action flow is unambiguous.

Add a validation/verification checkpoint before destructive action runs and proxy DELETE/PUT calls (e.g. 'Confirm the target record id before delete; re-fetch to verify the change').

Trim the marketing intro paragraph and collapse the plural/singular entity list into a single line of entity names to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with copy-paste bash throughout, but the marketing-style intro ('These features help organizations automate administrative tasks and engage with their members more effectively.') and the redundant plural/singular entity list are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run, proxy) plus a concrete flag-options table, matching the comprehensive executable anchor.	5 / 5
Workflow Clarity	The connection setup has a clear state-machine sequence with checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but 'Step 2' is referenced yet never defined, and there are no validation/verification steps for potentially destructive action runs or proxy DELETE/PUT operations, which caps this at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	The single-file skill is well-organized with clear section headers (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) and easy navigation; no external references are needed for a CLI-wrapper skill, though the 'Popular actions' section largely duplicates 'Searching for actions'.	4 / 5
	Total	16 / 20 Passed

Description

66%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 has an explicit 'Use when' trigger and names a distinct niche product, but its action list is generic and its trigger keywords are limited to the product name. Tightening the verbs and adding concrete entity terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete WildApricot actions, e.g. 'Manage contacts, members, events, and invoices; automate membership workflows.'

Expand the trigger clause with natural entity terms users say: 'Use when the user wants to manage WildApricot members, events, invoices, or membership data.'

Drop the buzzword 'automate workflows' or ground it in a specific capability (e.g. 'automate membership renewal workflows').

Dimension	Reasoning	Score
Specificity	It names the WildApricot domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete (e.g. no 'create events', 'send invoices', 'update members'), and 'automate workflows' is buzzword-ish.	3 / 5
Completeness	It answers both 'what' ('WildApricot integration. Manage data, records, and automate workflows.') and 'when' with an explicit 'Use when the user wants to interact with WildApricot data.' clause; the 'when' is present but could be more specific, fitting the anchor one below 5.	4 / 5
Trigger Term Quality	The natural keyword 'WildApricot' is present and users would say it, but coverage is essentially that single product name plus 'data'; common trigger synonyms users actually mention (membership, members, events, invoices) are missing.	3 / 5
Distinctiveness Conflict Risk	WildApricot is a named, niche product and the trigger ('interact with WildApricot data') is product-specific, giving it a clear niche with minimal overlap risk against other skills.	5 / 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/wildapricot/SKILL.md
Commit: f484c82

Reviewed: 3 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.