acuity-scheduling
Acuity Scheduling integration. Manage Calendars, Clients, Users, Forms, Packages, Coupons. Use when the user wants to interact with Acuity Scheduling data.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/acuity-scheduling/SKILL.mdQuality
Discovery
75%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 effectively identifies its niche (Acuity Scheduling) and includes an explicit 'Use when' clause, making it complete and distinctive. However, it relies on the vague verb 'Manage' instead of listing specific actions, and it misses common natural trigger terms like 'appointments', 'bookings', and 'availability' that users would likely use when needing this skill.
Suggestions
Replace 'Manage' with specific concrete actions like 'Create and cancel appointments, look up client records, configure availability, apply coupons, manage booking forms'.
Add natural trigger terms users would say, such as 'appointments', 'bookings', 'availability', 'schedule', and 'book' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Acuity Scheduling) and lists entity types (Calendars, Clients, Users, Forms, Packages, Coupons), but uses the vague verb 'Manage' rather than listing specific concrete actions like 'create appointments', 'update client records', 'apply coupons'. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Calendars, Clients, Users, Forms, Packages, Coupons via Acuity Scheduling integration) and 'when' (Use when the user wants to interact with Acuity Scheduling data), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Acuity Scheduling' and entity names like 'Calendars', 'Clients', 'Coupons', which are relevant keywords. However, it misses common natural user terms like 'appointments', 'bookings', 'scheduling', 'availability', which are what users would most likely say. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'Acuity Scheduling' creates a clear niche that is unlikely to conflict with other skills. The brand name serves as a strong distinctive trigger. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent workflow clarity for the connection setup process and concrete CLI commands throughout. Its main weaknesses are some unnecessary introductory context (explaining what Acuity Scheduling is) and a monolithic structure that could benefit from splitting reference material into separate files. The popular actions table and proxy request documentation are valuable but contribute to a lengthy single file.
Suggestions
Remove the opening paragraph explaining what Acuity Scheduling is — Claude already knows this, and the description metadata covers it.
Consider extracting the popular actions table and proxy request details into separate reference files (e.g., ACTIONS.md, PROXY.md) to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Acuity Scheduling is (salons, therapists, consultants) is unnecessary context Claude already knows. The Membrane CLI setup and authentication flow is reasonably efficient but could be tightened. The overview section listing entity types without actionable detail adds little value. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. The popular actions table with specific action keys and the input parameter syntax are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), polling instructions with --wait flag, and clear guidance on what to do at each state. The headless environment flow includes a feedback loop for code completion. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's somewhat monolithic — the popular actions table, proxy request details, and connection state machine documentation could be split into separate reference files. No bundle files are provided, so everything is inline in a single file that's fairly long. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- Reviewed
Table of Contents
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.