Act! 365 integration. Manage Contacts, Groups, Opportunities, Tasks, Users. Use when the user wants to interact with Act! 365 data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill act-36575
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/act-365/SKILL.mdDiscovery
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 adequately identifies the specific platform (Act! 365) and provides explicit 'Use when' guidance, making it complete and distinctive. However, it lacks specificity in the actions beyond generic 'Manage' and could benefit from more natural trigger terms that users might actually say when needing CRM functionality.
Suggestions
Replace 'Manage' with specific actions like 'Create, update, search, and delete Contacts, Groups, Opportunities, Tasks, and Users'
Add natural trigger terms users might say: 'CRM', 'customer database', 'sales contacts', 'deal tracking', 'contact management'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Act! 365) and lists entity types (Contacts, Groups, Opportunities, Tasks, Users) but uses vague 'Manage' without specifying concrete actions like create, update, delete, search, or sync. | 2 / 3 |
Completeness | Clearly 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Act! 365' and entity names which are relevant, but misses common variations users might say like 'CRM', 'customer database', 'sales pipeline', or 'contact management'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Act! 365' is a specific product name that creates a clear niche; unlikely to conflict with other CRM skills due to the explicit product identifier. | 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.
This skill provides solid, actionable CLI commands for Act! 365 integration via Membrane, with good coverage of common operations. However, it wastes tokens on CRM explanation Claude doesn't need, includes a bulky action table with empty descriptions, and lacks validation/error handling guidance for the multi-step connection workflow.
Suggestions
Remove the opening paragraph explaining what Act! 365 is - Claude already knows this context
Add validation steps after connection setup (e.g., 'Verify connection: membrane connection list --json and confirm status is active')
Move the action table to a separate ACTIONS.md reference file or remove 'No description' entries entirely
Add error handling guidance for common failures (auth timeout, invalid connection, action not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Act! 365 is wastes tokens on information Claude already knows. The action table with 'No description' entries adds bulk without value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection setup, action discovery, and proxy requests are all copy-paste ready with concrete examples and flag documentation. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are clearly sequenced, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the large action table could be moved to a separate reference file. Links to official docs exist but no internal file references for advanced topics or detailed API documentation. | 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 | |
Table of Contents
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.