Name: dripcel
Rating: 64.8 (1 reviews)
Author: membranedev

dripcel

Dripcel integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Dripcel data.

Quality

77%

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/dripcel/SKILL.md

Quality

Content

76%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.

A highly actionable, well-structured integration skill whose main weakness is missing validation/verification steps for its destructive and batch operations. Conciseness and progressive disclosure are solid.

Suggestions

Add an explicit validation/verification checkpoint before destructive or batch actions (e.g. confirm contact count, dry-run upserts, verify delete results) so workflow_clarity can exceed the destructive-ops cap of 3.

Trim mildly padded phrasing such as "so you can focus on the integration logic rather than auth plumbing" to tighten token efficiency.

Show a brief feedback loop for batch operations (run -> inspect output -> retry on partial failure) to mirror the good checkpoint pattern already used in the connection flow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with copy-paste commands and a tight best-practices list; minor trim opportunities exist (e.g. "so you can focus on the integration logic rather than auth plumbing" and the explanatory sentence on URL normalization).	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands (npm install, membrane login, connection ensure, action run with --input JSON, request proxy) plus a popular-actions table covering common cases.	5 / 5
Workflow Clarity	The connection flow has clear state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but batch/destructive operations ("Upsert Contacts up to 20,000", "Delete Contact", "Bulk Update Contacts", "Send Bulk Email") have no validation or verify-before-act feedback loops, capping this dimension at 3.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested or broken references and no bundle files; at ~158 lines it is self-contained and appropriately structured, though it carries no one-level-deep reference files that would warrant a 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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 clearly answers what the skill does and when to use it, with a distinct named-platform niche. It could improve by swapping the generic "Manage...and more" for distinct action verbs and adding user-natural synonyms like "contacts" and "campaigns".

Suggestions

Replace the umbrella verb "Manage" and the vague "and more" with a few distinct concrete actions (e.g. create, update, search, delete) to raise specificity.

Add natural synonyms users actually say ("contacts", "campaigns", "emails", "SMS") to broaden trigger-term coverage.

Sharpen the "when" clause with concrete trigger phrases (e.g. "Use when the user wants to manage Dripcel contacts, campaigns, or send bulk email").

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Projects, Activities" lists several concrete capability targets, though all are covered by the single umbrella verb "Manage" and the vague "and more" leaves a minor coverage gap.	4 / 5
Completeness	Both "what" (Dripcel integration managing named entities) and "when" ("Use when the user wants to interact with Dripcel data") are present and explicit, but the "when" trigger is slightly generic compared to a fully concrete trigger-phrase list.	4 / 5
Trigger Term Quality	"Dripcel" plus the entity names (Persons, Deals, Leads, etc.) give good keyword coverage and a natural trigger ("Use when the user wants to interact with Dripcel data"), but common synonyms users actually say like "contacts", "campaigns", and "emails" are absent.	4 / 5
Distinctiveness Conflict Risk	Dripcel is a specific named platform with entity-specific triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/dripcel/SKILL.md
Commit: f484c82

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