act-365
Act! 365 integration. Manage Contacts, Groups, Opportunities, Tasks, Users. Use when the user wants to interact with Act! 365 data.
60
70%
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/act-365/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 product (Act! 365) and includes an explicit 'Use when' clause, making it complete and distinctive. However, it relies on the vague verb 'Manage' rather than listing specific actions, and could benefit from additional trigger terms covering common CRM vocabulary and action verbs.
Suggestions
Replace 'Manage' with specific concrete actions like 'Create, update, delete, search, and list Contacts, Groups, Opportunities, Tasks, and Users'.
Add common CRM-related trigger terms such as 'CRM', 'customer relationship management', 'deals', or 'sales pipeline' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Act! 365) and lists entity types (Contacts, Groups, Opportunities, Tasks, Users) but uses the vague verb 'Manage' without specifying concrete actions like create, update, delete, search, or sync. | 2 / 3 |
Completeness | Answers both 'what' (manage Contacts, Groups, Opportunities, Tasks, Users in Act! 365) and 'when' (Use when the user wants to interact with Act! 365 data) with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Act! 365' as a strong product-specific trigger and entity names like 'Contacts', 'Opportunities', 'Tasks' which users might say, but misses common variations like 'CRM', 'customer relationship management', 'deals', 'pipelines', or action-oriented terms like 'add contact' or 'create opportunity'. | 2 / 3 |
Distinctiveness Conflict Risk | Act! 365 is a specific product name that creates a clear niche; unlikely to conflict with other CRM skills unless there are multiple Act! 365 skills. The product-specific naming makes it highly distinguishable. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for integrating with Act! 365 via Membrane, making it practically useful. However, it suffers from unnecessary introductory context, a bloated actions table with empty descriptions, and could benefit from better end-to-end workflow sequencing with validation steps. The content would be stronger if trimmed and restructured with progressive disclosure.
Suggestions
Remove the introductory paragraph explaining what Act! 365 is and the bare entity list under 'Act! 365 Overview' — Claude doesn't need this context.
Either add descriptions to the popular actions table entries or remove the table and rely on `membrane action list --intent` for discovery, since 20 rows of 'No description' waste tokens.
Add explicit validation/verification steps after running actions (e.g., check output for errors, verify expected fields in response) to improve workflow clarity.
Consider splitting the proxy request reference and popular actions table into a separate REFERENCE.md file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Act! 365 is ('simplified CRM software designed for small businesses...') is unnecessary context Claude doesn't need. The 'Act! 365 Overview' section listing entity types without any actionable detail adds little value. The popular actions table with 'No description' repeated 20 times is wasteful. However, the CLI commands and workflow steps are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and parameter examples. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a reasonable sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but there are no explicit validation checkpoints or feedback loops for action execution. The overall flow from install → auth → connect → discover → run is implicit rather than clearly numbered end-to-end, and error recovery for action runs is not addressed. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. The popular actions table (20 rows with no descriptions) and the proxy request options table could be in separate reference files. The structure uses headers reasonably well but everything is inline when some content could benefit from being split out. | 2 / 3 |
Total | 9 / 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.