Name: pipeline-crm
Rating: 53.6 (1 reviews)
Author: membranedev

pipeline-crm

PipelineCRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with PipelineCRM data.

Quality

60%

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

Quality

Content

57%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 body is executable and the connection workflow is well-sequenced, but it is dragged down by a large padded entity list, missing validation before destructive action/proxy calls, and a broken Step 2 reference. Splitting reference material into bundle files and adding verification steps would meaningfully improve it.

Suggestions

Move the 130-item entity list and the proxy flag reference table into a separate references file (e.g. ENTITIES.md) and link to it from the overview.

Add a validation/verification step before running or proxying mutating actions (e.g. dry-run, confirm destructive operations, check the returned state).

Fix the dangling "Step 2" reference by either defining the step or removing the cross-reference.

Dimension	Reasoning	Score
Conciseness	CLI command blocks are lean, but the ~130-item undecorated entity bullet list is substantial padding (including duplicates and entities unrelated to PipelineCRM) and the intro lightly re-explains what a CRM is.	3 / 5
Actionability	Provides copy-paste-ready membrane commands for install, auth, connection, action list/run, and proxy requests with flags, with only minor gaps such as unresolved <actionId> placeholders.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state branching and polling feedback, but running/proxying actions can be destructive or batch with no validation step, and "Step 2" is referenced but never defined.	3 / 5
Progressive Disclosure	Single-file monolith with some section structure, but the long entity list and full flag reference table clearly belong in separate reference files, and the broken "Step 2" reference hurts navigation.	3 / 5
	Total	13 / 20 Passed

Description

62%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 covers what and when and is clearly tied to PipelineCRM, but its actions are generic and it lacks the natural CRM trigger terms users would say. Tightening the wording with concrete CRM verbs would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete CRM actions, e.g. "create and update deals, contacts, and leads; track pipeline stages".

Add natural trigger terms users say: "deals", "contacts", "leads", "sales pipeline", "PipelineCRM records".

Make the when-clause more explicit, e.g. "Use when the user wants to manage deals, contacts, or sales workflows in PipelineCRM."

Dimension	Reasoning	Score
Specificity	Names the PipelineCRM domain plus a few generic actions ("Manage data, records, and automate workflows"), but the actions are abstract rather than concrete CRM verbs like create deals or update contacts.	3 / 5
Completeness	States both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with PipelineCRM data"), though the when-clause could name concrete triggers.	4 / 5
Trigger Term Quality	Includes "PipelineCRM" and "interact with PipelineCRM data" but omits the natural terms users actually say (deals, contacts, leads, pipeline), relying on generic language.	3 / 5
Distinctiveness Conflict Risk	Tied to the specific PipelineCRM niche with a distinct trigger, with only minor overlap risk against other CRM skills.	4 / 5
	Total	14 / 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/pipeline-crm/SKILL.md
Commit: f484c82

Reviewed: 5 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.