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

69%

Does it follow best practices?

Impact

91%

1.13x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/pipedrive-automation/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete tool sequences, parameter formats, and a thorough quick-reference table. Its weaknesses are duplicated pitfalls (conciseness) and missing validation feedback loops for batch/destructive workflows (workflow clarity).

Suggestions

Remove the duplicated pitfalls from the consolidated 'Known Pitfalls' section or convert it to cross-references, keeping each pitfall in one place to improve conciseness.

Add explicit verification/feedback steps to batch and destructive workflows (e.g., after creating deals in bulk, verify counts; if a tool call fails, re-search the entity and retry).

Consider moving the large Quick Reference table into a separate reference file to better follow progressive disclosure for a 230-line skill.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-like with no concept-explaining fluff, but pitfalls are duplicated both inline per-workflow and again in the consolidated 'Known Pitfalls' section, which is mild redundancy that could be tightened.	3 / 5
Actionability	Each workflow gives an explicit numbered tool sequence with required/optional/prerequisite tags, concrete parameter formats (YYYY-MM-DD, 3-letter ISO codes, HH:MM), array shapes, and a 25-row quick-reference table — the executable equivalent of copy-paste code for an MCP skill.	5 / 5
Workflow Clarity	Sequences are clearly annotated with an auth validation checkpoint in Setup, but the core create/update/delete and bulk workflows lack validate→fix→retry feedback loops, which caps workflow clarity at 3 for destructive/batch operations per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but the body is well-organized with clear section headers and an overview-to-detail flow; the bulky quick-reference table and consolidated pitfalls could be split into a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 specific and clearly niched to Pipedrive via Rube MCP, with strong capability enumeration. Its main weakness is the missing explicit 'Use when...' trigger guidance, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to automate Pipedrive CRM tasks such as creating deals, managing contacts, scheduling activities, or querying pipelines.'

Replace generic 'management' phrasing with a few concrete verbs (create, update, search, schedule) to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	Enumerates six concrete capability domains ('deals, contacts, organizations, activities, notes, and pipeline management') but leans on domain nouns plus 'management' rather than distinct discrete verbs, sitting just below the comprehensive-action anchor.	4 / 5
Completeness	The 'what' is clearly and concretely stated, but there is no 'Use when...' or equivalent explicit 'when' clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms a user would say ('Pipedrive', 'CRM', 'deals', 'contacts') are well-covered, but the description lacks an explicit 'Use when...' trigger phrasing and a few natural variations.	4 / 5
Distinctiveness Conflict Risk	Naming a specific CRM ('Pipedrive') plus a specific integration ('via Rube MCP (Composio)') establishes a clear niche with minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/pipedrive-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 20 hours 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.