pipedrive-automation
Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.
75
66%
Does it follow best practices?
Impact
91%
1.13xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/pipedrive-automation/SKILL.mdQuality
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 is reasonably strong in specificity and distinctiveness, clearly identifying Pipedrive CRM as the target domain and listing the key entity types it manages. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and could benefit from more natural user-facing trigger terms beyond the entity names.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Pipedrive, CRM deals, sales pipelines, managing contacts or leads in Pipedrive.'
Include additional natural trigger terms users might say, such as 'sales', 'leads', 'follow-up', 'customer management', or 'update deal status'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: deals, contacts, organizations, activities, notes, and pipeline management. Also specifies the mechanism (Rube MCP/Composio) and includes a procedural instruction to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Pipedrive CRM operations across multiple entity types), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Pipedrive', 'CRM', 'deals', 'contacts', 'organizations', 'activities', 'notes', 'pipeline', but misses common user variations like 'lead', 'sales', 'follow-up', 'customer relationship', or action-oriented terms like 'create deal', 'add contact'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Pipedrive CRM specifically, with distinct platform name and entity types mentioned. Unlikely to conflict with other skills unless there were multiple Pipedrive-related skills. | 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 is a comprehensive and actionable Pipedrive automation skill with excellent specificity in tool names, parameters, and data formats. Its main weaknesses are redundancy across sections (pitfalls repeated in both workflow-specific and global sections), lack of validation/error-handling checkpoints in workflows, and being a monolithic document that could benefit from splitting into referenced sub-files for individual workflow domains.
Suggestions
Add explicit validation and error-handling steps to workflows (e.g., 'If search returns 0 results, create new entity; if multiple results, ask user to disambiguate') to improve workflow clarity.
Deduplicate pitfalls by keeping them only in the global 'Known Pitfalls' section and removing per-workflow repetitions (email format, done integer, visible_to) to improve conciseness.
Consider splitting detailed workflow sections (Deals, Contacts, Activities, Notes, Pipelines) into separate referenced files, keeping SKILL.md as a concise overview with the quick reference table and links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-organized but is quite long (~250 lines) with some redundancy. Pitfalls are repeated across sections and the Known Pitfalls section (e.g., email/phone format, done integer, visible_to values appear multiple times). The quick reference table duplicates information already covered in the workflows. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, exact parameter names and formats, concrete examples of data structures (e.g., email array format), specific values for enums (visible_to: 1/3/5, done: 0/1), and clear tool sequences with labeled steps. The guidance is directly executable against the Rube MCP tooling. | 3 / 3 |
Workflow Clarity | Tool sequences are clearly numbered with labeled steps (Required/Optional/Prerequisite), which is excellent. However, there are no explicit validation checkpoints or error recovery feedback loops. For operations like deal creation that depend on multiple prerequisite ID resolutions, there's no guidance on what to do if a search returns no results vs. multiple results, or how to handle API errors. | 2 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files to reference. For a skill this comprehensive covering 5 major workflows, the content would benefit from splitting detailed workflow sections into separate files. The structure within the file is good (clear headers, table), but everything is inline in one large document. | 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
- davepoon/buildwithclaude
- Commit
74c7031
- 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.