Name: pipefy
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pipefy

Pipefy integration. Manage Organizations, Users, Filters. Use when the user wants to interact with Pipefy data.

Quality

63%

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

Quality

Content

61%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 real CLI commands and a clear connection workflow including feedback loops, but it is held back by an unnecessary product-overview paragraph and a lack of validation guidance around destructive actions. Tightening the prose and adding a pre-deletion confirmation step would lift the weakest dimensions.

Suggestions

Add a validation/confirmation checkpoint before running destructive actions (e.g. "Before delete-card or delete-table-record, confirm the target ID with the user and prefer a get-* call to verify first").

Trim the opening "Pipefy is a workflow management software..." paragraph and "focus on the integration logic rather than auth plumbing" asides, keeping only what the integration task requires.

Include one fully worked end-to-end example with concrete sample values (connection ensure → action list --intent → action run) to make the placeholder usage explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Pipefy is and asides like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation Claude does not need.	3 / 5
Actionability	It provides many concrete, copy-paste CLI commands (login, connection ensure, action list/run, request) plus a popular-actions table, but there is no end-to-end worked example and placeholders like "QUERY" and "<agentType>" are left abstract without sample values.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state checks and a poll-again feedback loop, but destructive actions (delete-card, delete-table-record) are offered with no validation or confirmation step, which caps workflow clarity per the destructive-operations rule.	3 / 5
Progressive Disclosure	Clear section headers and a logical flow organize the content well with no nested references, though the sizable 20-row popular-actions table is inline reference material that could live in a separate file.	4 / 5
	Total	14 / 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 cleanly answers both what and when for a distinct, named-product niche, but its capability list is narrow and its trigger phrasing is generic. Adding concrete task verbs and natural user terms (cards, pipes, tasks) would raise specificity and trigger quality.

Suggestions

Replace the generic verb "Manage" with concrete actions the skill supports (e.g. "Search and create cards, move cards between phases, manage table records").

Expand the "Use when..." clause with natural trigger phrases users actually say, such as "when the user mentions Pipefy cards, pipes, phases, or table records".

Include the most common user-facing nouns (cards, pipes, tables, records) so the description reflects the breadth of actions shown in the body.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Filters" names the Pipefy domain and a few concrete entities, but the verb "Manage" is generic and the description omits most capabilities (cards, pipes, tables, records) shown in the body, so coverage is not comprehensive.	3 / 5
Completeness	It states both a "what" ("Manage Organizations, Users, Filters") and an explicit "when" ("Use when the user wants to interact with Pipefy data"), but the trigger clause is generic rather than concrete, fitting the anchor where 'when' could be more specific.	4 / 5
Trigger Term Quality	The brand term "Pipefy" and "interact with Pipefy data" are relevant, but common natural task phrases users would actually say (cards, pipes, tasks, workflows) are missing, leaving only some relevant keywords.	3 / 5
Distinctiveness Conflict Risk	"Pipefy integration" and "interact with Pipefy data" target a single named product, giving a clear niche with distinct triggers and minimal conflict risk with 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/pipefy/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.