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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill pipedrive-automation72
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
50%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 communicates specific Pipedrive CRM capabilities and is highly distinctive due to platform-specific naming. However, it critically lacks a 'Use when...' clause that would help Claude know when to select this skill, and could benefit from more natural user-facing trigger terms beyond technical CRM terminology.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Pipedrive, sales pipelines, CRM data, or managing customer relationships'
Include natural user terms like 'sales pipeline', 'lead tracking', 'customer management', 'sales data' that users would actually say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deals, contacts, organizations, activities, notes, and pipeline management' plus the instruction to 'search tools first for current schemas'. This provides clear, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes good domain terms like 'Pipedrive', 'CRM', 'deals', 'contacts', 'organizations', but missing common user variations like 'sales pipeline', 'lead management', 'customer data', or 'sales tracking' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche with 'Pipedrive CRM' and 'Rube MCP (Composio)' as distinct identifiers. Unlikely to conflict with other skills due to the specific platform and integration mentioned. | 3 / 3 |
Total | 9 / 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.
This is a well-structured, highly actionable skill for Pipedrive automation with clear tool sequences, specific parameters, and helpful pitfall warnings. The main weakness is length—the comprehensive inline content could benefit from splitting detailed workflows into separate reference files. The redundancy between workflow sections and the quick reference table adds tokens without proportional value.
Suggestions
Consider moving detailed workflow sections (Create Deals, Manage Contacts, etc.) to separate reference files, keeping SKILL.md as a concise overview with links
Consolidate parameter documentation—the quick reference table duplicates information from workflow sections; choose one authoritative location
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy—parameter lists are repeated across workflows and the quick reference table, and some explanations could be tighter. However, it avoids explaining basic CRM concepts Claude already knows. | 2 / 3 |
Actionability | Provides specific tool slugs, exact parameter names with formats (e.g., 'YYYY-MM-DD', 'HH:MM'), concrete examples of data structures (email arrays), and clear sequences. Everything is copy-paste ready for API calls. | 3 / 3 |
Workflow Clarity | Each workflow has numbered steps with clear labels ([Required], [Optional], [Prerequisite]), explicit tool sequences, and pitfalls sections that serve as validation guidance. The ID resolution pattern and pagination handling provide error prevention. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~300 lines) with all content inline. The quick reference table helps, but detailed workflows could be split into separate files with SKILL.md serving as an overview. | 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 | |
- 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.