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

conveyor

Conveyor integration. Manage Organizations, Projects, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Conveyor 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conveyor/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 content is strongly actionable with concrete Membrane CLI commands and a useful connection-state workflow, but it is held back by an inlined bulk action-reference table, an undefined "Step 2" reference, and missing verification steps for destructive action runs.

Suggestions

Move the 20-row popular-actions table into a references/ file (e.g. ACTIONS.md) and link to it, keeping only a few representative examples inline to improve progressive disclosure and conciseness.

Add a verification step after running destructive/batch actions (e.g. re-fetch the resource to confirm the delete/update took effect) and fix the dangling "Step 2" reference by numbering the workflow steps explicitly.

Trim the marketing-style Conveyor background paragraph to a single line of domain context.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands, but the opening SaaS-marketing paragraph ("helps software teams automate the process of packaging and distributing... streamline releases") and the 20-row inline actions table add padding that could be trimmed.	3 / 5
Actionability	Concrete executable commands appear throughout (install, login, connection ensure, action list/run, request) with real flags and a table of specific action keys, but unresolved placeholders (CONNECTION_ID, <actionId>, <agentType>) and the absence of a full worked example leave minor gaps.	4 / 5
Workflow Clarity	The connection flow has good state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but the text references an undefined "Step 2", and destructive actions (delete-document, update-authorization) are run without any verification step, capping this at 3.	3 / 5
Progressive Disclosure	Section headers organize the body reasonably, but the 20-row popular-actions reference table is inlined rather than split into a separate reference file, and no bundle files or external references exist to offload the bulk detail.	3 / 5
	Total	13 / 20 Passed

Description

70%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 names the domain and provides an explicit use-when trigger with good entity-level keyword coverage. Its main weakness is reliance on the single generic verb "Manage" rather than enumerating concrete actions, and a somewhat generic "when" clause.

Suggestions

Replace the single verb "Manage" with specific concrete actions (e.g., "List, create, update, and delete Organizations, Projects, Pipelines, Users, Goals, and Filters") to raise specificity.

Tighten the "when" clause with concrete trigger phrases, e.g. "Use when the user wants to list or update Conveyor pipelines, projects, users, or goals."

Dimension	Reasoning	Score
Specificity	The description enumerates concrete Conveyor entities ("Organizations, Projects, Pipelines, Users, Goals, Filters") but bundles them all under the single generic verb "Manage", so actions are minimal rather than varied and comprehensive.	3 / 5
Completeness	Both the "what" ("Manage Organizations, Projects, Pipelines, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with Conveyor data") are present, but the "when" could be more concrete with specific trigger phrases.	4 / 5
Trigger Term Quality	Named entities like Projects, Pipelines, Users, Goals, and Filters are natural terms a user would say, giving good keyword coverage; the "Use when the user wants to interact with Conveyor data" trigger is slightly generic, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Being scoped to the named app Conveyor makes it mostly distinct with minimal conflict risk, though generic entity names like Projects, Pipelines, and Users carry minor overlap risk with project-management or CI/CD skills.	4 / 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/conveyor/SKILL.md
Commit: f484c82

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