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

pipeliner

Pipeliner integration. Manage Leads, Deals, Persons, Organizations, Activities, Notes and more. Use when the user wants to interact with Pipeliner 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/pipeliner/SKILL.md

Quality

Content

75%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 a highly actionable, well-structured CLI integration guide with a strong sequenced connection workflow and feedback loop. Its main drag is conciseness — the redundant entity overview list and minor padded phrasing — rather than structure or actionability.

Suggestions

Remove or collapse the 21-item "Pipeliner Overview" bullet list since it duplicates the "Popular actions" table.

Trim explanatory filler such as "so you can focus on the integration logic rather than auth plumbing".

Add a brief validation/check step for create/update/delete action runs (e.g. verify the returned object or re-fetch) to strengthen workflow clarity for write operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-focused prose, but the 21-item "Pipeliner Overview" bullet list largely duplicates the "Popular actions" table, and phrases like "so you can focus on the integration logic rather than auth plumbing" add mild padding.	3 / 5
Actionability	Copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) with flags shown, plus a concrete actions table and a proxy-options table — fully executable and covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop after user action, though write/destructive action calls lack an explicit validation step.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and tables in a single cohesive CLI-guide file; no nested or buried references, and the content is appropriately inline for this kind of integration skill.	4 / 5
	Total	16 / 20 Passed

Description

73%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 cleanly names a distinct product and supplies both a capability summary and an explicit Use-when trigger, with natural entity keywords. Its main weakness is the generic verb "Manage ... and more" in place of concrete actions.

Suggestions

Replace the generic verb "Manage" with specific verbs (e.g. "Create, list, update, and delete Leads, Deals, Persons, Organizations, Activities, and Notes") to lift specificity.

Expand the trigger clause with concrete user phrases (e.g. "Use when the user wants to manage Pipeliner CRM leads, deals, contacts, or activities").

Drop the vague trailing "and more" or replace it with a named capability so the scope is bounded.

Dimension	Reasoning	Score
Specificity	It names the domain and many concrete entities ("Leads, Deals, Persons, Organizations, Activities, Notes") but uses the single generic verb "Manage" rather than listing concrete actions, so actions are minimal/generic rather than comprehensive.	3 / 5
Completeness	It states both the "what" ("Manage Leads, Deals, Persons...") and an explicit "when" ("Use when the user wants to interact with Pipeliner data"), but the trigger phrase is somewhat generic rather than packing concrete trigger phrases, so it sits just below the top anchor.	4 / 5
Trigger Term Quality	Natural entity terms a user would say ("Leads, Deals, Persons, Organizations, Activities, Notes") plus "Pipeliner data" give good keyword coverage, though a few common synonyms (e.g. "opportunities", "contacts") are missing relative to the body.	4 / 5
Distinctiveness Conflict Risk	"Pipeliner integration" names a specific CRM product, giving it a clear niche with minimal risk of triggering for the wrong skill.	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: membranedev/application-skills
Path: skills/pipeliner/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.