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.

1.13x

Quality

65%

Does it follow best practices?

Impact

91%

1.13x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/pipedrive-automation/SKILL.md

Quality

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 strong in specificity and distinctiveness, clearly identifying Pipedrive CRM as the domain and listing concrete entity types it manages. However, it lacks an explicit 'Use when...' clause which hurts completeness, and could benefit from more natural user-facing trigger terms beyond the CRM entity names.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Pipedrive, CRM deals, managing sales pipelines, or tracking contacts and activities in Pipedrive.'

Include more natural user trigger terms such as 'sales', 'leads', 'follow-up', 'customer tracking', or 'sales pipeline' that users might say without specifically naming Pipedrive.

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 concrete 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 keywords like 'Pipedrive', 'CRM', 'deals', 'contacts', 'organizations', 'activities', 'notes', 'pipeline', but misses common user variations like 'leads', 'sales', 'follow-up', or phrases users might naturally say. The technical terms 'Rube MCP' and 'Composio' are not user-facing trigger terms.	2 / 3
Distinctiveness Conflict Risk	Very clearly scoped to Pipedrive CRM specifically, with distinct entity types and a named integration mechanism (Rube MCP/Composio). Unlikely to conflict with other skills unless there are multiple Pipedrive skills.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

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 Pipedrive automation skill with excellent workflow structure and clear tool sequencing, but it suffers from significant redundancy (pitfalls repeated across sections and in a consolidated section) and lacks concrete executable examples showing actual tool call payloads. The monolithic structure would benefit from splitting reference material into separate files.

Suggestions

Add at least one concrete, copy-paste ready tool invocation example per workflow showing actual parameter payloads (e.g., a complete PIPEDRIVE_ADD_A_DEAL call with sample values)

Eliminate duplicated pitfalls—either keep them only in per-workflow sections or only in the consolidated 'Known Pitfalls' section, not both

Split the quick reference table and detailed parameter/pitfall documentation into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with workflow sequences

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~250 lines) with significant repetition—pitfalls are listed per workflow AND again in a consolidated 'Known Pitfalls' section (e.g., email arrays, done integer, auto-merge). The quick reference table duplicates information already covered in each workflow. However, the content is mostly non-trivial API-specific knowledge that Claude wouldn't inherently know.	2 / 3
Actionability	Tool names and parameter details are specific and concrete, which is good. However, there are no executable code examples or copy-paste ready tool invocations showing actual parameter payloads. The guidance is structured as tool sequences with parameter lists rather than concrete call examples with sample JSON bodies.	2 / 3
Workflow Clarity	Each workflow has clearly numbered tool sequences with explicit labels ([Required], [Optional], [Prerequisite]), logical ordering, and prerequisite steps like ID resolution before entity creation. The setup section includes a verification flow. The ID resolution pattern and pagination handling serve as validation/verification guidance.	3 / 3
Progressive Disclosure	The content is entirely monolithic—everything is in one file with no references to separate detailed documents. For a skill this long, the detailed parameter lists, pitfalls, and the large quick reference table could be split into separate reference files. The single external link to Composio docs is helpful but insufficient for the volume of content.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days ago

Table of Contents

Discovery Implementation Validation

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.