Name: pipedrive
Rating: 62.4 (1 reviews)
Author: membranedev

pipedrive

Pipedrive integration. Manage crm and sales data, records, and workflows. Use when the user wants to interact with Pipedrive data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/pipedrive/SKILL.md

Quality

Content

82%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 and well-structured with a clear, checkpointed connection workflow; its main gaps are a slightly over-explanatory opening and the absence of result-verification guidance for destructive CRUD actions.

Suggestions

Cut the opening paragraph defining what Pipedrive/CRM is and the 'auth plumbing' aside to assume Claude's existing knowledge.

Add a verification step after running create/update actions (e.g. re-fetch the record or check the `output` field for the returned id) to close the feedback loop on destructive operations.

Consider moving the full Popular-actions and proxy-flag tables into a short reference file (e.g. ACTIONS.md) and linking to it, keeping only the most common examples inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, code-driven commands, but it opens by explaining what Pipedrive/CRM is ('Pipedrive is a CRM and sales management tool...') and includes minor padding like 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.	4 / 5
Actionability	Every workflow step is backed by copy-paste-ready, executable commands (npm install, membrane login, connection ensure, action list/run, request) with concrete flags, --json output, and an input-passing example, covering the common cases.	5 / 5
Workflow Clarity	The connect-and-wait flow is clearly sequenced with explicit checkpoints and feedback loops (poll --wait, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling), but the destructive create/update action steps lack a verify-the-result checkpoint.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly labeled sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices), though the 20-row action table and proxy-flag table are bulk reference material kept fully inline with no offloaded reference file.	4 / 5
	Total	17 / 20 Passed

Description

66%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 distinct and answers both what and when, but its action language is generic ('manage') and its trigger terms lack common Pipedrive synonyms like deals, leads, and pipeline.

Suggestions

Replace the generic verb 'Manage' with concrete operations, e.g. 'Create and update deals, leads, persons, and organizations'.

Expand the trigger clause to surface natural user terms: 'Use when the user wants to manage Pipedrive deals, leads, contacts, pipelines, or sales workflows'.

Add file/record-level terms (records, activities, notes) so the description matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	Names the domain (Pipedrive/CRM/sales) and several action areas ('Manage crm and sales data, records, and workflows'), but the verb 'manage' is generic rather than naming concrete operations like create/update/extract, so it is not comprehensive.	3 / 5
Completeness	Provides both a 'what' ('Manage crm and sales data, records, and workflows') and an explicit 'when' ('Use when the user wants to interact with Pipedrive data'), though the trigger clause could name more specific use cases.	4 / 5
Trigger Term Quality	Includes relevant natural terms (Pipedrive, crm, sales) but misses common synonyms and objects users would actually say such as deals, leads, contacts, pipeline, or organizations.	3 / 5
Distinctiveness Conflict Risk	Names the specific application Pipedrive and a clear CRM/sales niche, giving it a distinct trigger surface with minimal overlap risk against other skills.	5 / 5
	Total	15 / 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: membranedev/application-skills
Path: skills/pipedrive/SKILL.md
Commit: f484c82

Reviewed: ~19 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.