agendor
Agendor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agendor data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agendor/SKILL.mdQuality
Discovery
57%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 benefits from naming the specific platform (Agendor) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what actions can be performed. The generic terms 'data', 'records', and 'workflows' provide almost no useful information for skill selection, and the description misses natural trigger terms related to CRM functionality that users would likely use.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific CRM actions such as 'create and update contacts, manage deals and pipelines, track sales activities, and generate reports'.
Add natural trigger terms users would say, such as 'CRM', 'sales pipeline', 'deals', 'contacts', 'leads', or 'customer management' to improve matching.
Expand the 'Use when' clause with more specific triggers, e.g., 'Use when the user mentions Agendor, needs to manage CRM contacts, track deals, or automate sales workflows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't clarify what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Agendor data) with an explicit 'Use when' clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'Agendor' as a key trigger term which is specific to the platform, and 'data' and 'workflows' are somewhat relevant. However, it misses natural terms users might say like 'CRM', 'deals', 'contacts', 'pipeline', 'sales', or 'leads' that would help match user requests. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agendor' as a proper noun provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with any CRM or data management skill. Without mentioning CRM-specific concepts, it could conflict with similar integration skills. | 2 / 3 |
Total | 8 / 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.
The skill provides strong actionable guidance with executable CLI commands and a well-structured connection workflow with explicit state handling. However, it suffers from some unnecessary introductory content, a largely useless popular actions table (all entries lack descriptions), and a cryptic overview section. The content would benefit from trimming filler and better organizing reference material.
Suggestions
Remove or significantly shorten the introductory paragraph about what Agendor is — Claude already knows this, and the skill description covers it.
Either add meaningful descriptions to the popular actions table or remove it entirely, as 20 rows of 'No description' waste tokens without adding value.
Clarify or remove the 'Agendor Overview' section (Contact → Task, Company → Task) which is cryptic and doesn't provide actionable guidance.
Consider extracting the proxy request flags table and detailed CLIENT_ACTION_REQUIRED handling into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Agendor is a CRM and sales management platform. It's used by small and medium-sized businesses...') and the overview section ('Contact → Task, Company → Task') is vague and adds little value. The popular actions table has 'No description' for every entry, wasting tokens. However, the CLI commands and workflow steps are reasonably lean. | 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 JSON parameter examples. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions with --wait flag, and clear branching logic for each state. The overall flow from install → auth → connect → discover → run is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. The popular actions table (20 rows, all without descriptions) and the detailed proxy request options could be split into separate reference files. The overview section ('Contact → Task, Company → Task') is cryptic and doesn't serve as useful navigation. | 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.