agendor
Agendor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agendor data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill agendor72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 correctly identifies the integration target (Agendor) and includes an explicit 'Use when' clause, which is good. However, it lacks specific concrete actions that would help Claude understand the full capabilities, and the generic terms 'data', 'records', and 'workflows' could benefit from more domain-specific language related to CRM/sales functionality.
Suggestions
Add specific concrete actions like 'create contacts', 'update deals', 'manage sales pipeline', 'track opportunities' to improve specificity.
Include natural trigger terms users might say such as 'CRM', 'sales', 'contacts', 'deals', 'pipeline' alongside 'Agendor'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agendor) and mentions general actions ('Manage data, records, and automate workflows'), but lacks specific concrete actions like 'create contacts', 'update deals', or 'sync pipeline stages'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Agendor data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Agendor' as a key trigger term which users would naturally say, but lacks common variations or related terms users might use (e.g., 'CRM', 'sales pipeline', 'contacts', 'deals'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Agendor' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other CRM or data management skills. | 2 / 3 |
Total | 9 / 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 guidance with executable CLI commands and a useful actions reference table. However, it lacks validation checkpoints for multi-step operations (connection setup, action execution) and includes some unnecessary introductory content about what Agendor is. The overview section structure is unclear and the content could be more concise.
Suggestions
Add validation steps after key operations (e.g., 'Verify connection succeeded by running `membrane connection list --json` and confirming the connection appears')
Remove or significantly condense the introductory paragraph explaining what Agendor is - Claude already knows this
Clarify or remove the cryptic 'Agendor Overview' section with Contact/Task/Company hierarchy - it's unexplained and adds no actionable value
Add error handling guidance for common failure scenarios (auth timeout, invalid connection ID, action not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., explaining what Agendor is, what CRM means to sales teams). The Membrane CLI setup instructions are repeated boilerplate that could be more condensed. | 2 / 3 |
Actionability | Provides fully executable bash commands for every operation - CLI installation, login, connection setup, action discovery, and running actions. The proxy request section includes concrete flag examples and the popular actions table gives specific action keys. | 3 / 3 |
Workflow Clarity | Steps are listed sequentially for setup and connection, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Agendor Overview' section with Contact/Task/Company hierarchy is cryptic and unexplained. The popular actions table is inline when it could be referenced externally given its length. | 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 | |
- 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.