Name: salespype
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

salespype

Salespype integration. Manage Organizations. Use when the user wants to interact with Salespype data.

Quality

62%

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

Quality

Content

63%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 Membrane CLI workflow is concrete and well-sequenced with good validation on the connection phase, but the document is bloated by a huge inlined entity list and lacks progressive disclosure via reference files.

Suggestions

Remove the auto-generated entity list (many entries like Metaverse/Blockchain/IoT Integration are not real Salespype objects); instead point users to `membrane action list` to discover entities at runtime.

Move any retained entity/action reference into a separate REFERENCES.md and link to it one level deep from the body.

Add a verification step after `membrane action run` (e.g. check the `output`/`error` field and retry or surface the error) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The ~140-item entity list (running from Account to "Metaverse Integration", "Blockchain Integration", "IoT Device Integration") is heavy auto-generated padding; the CLI sections themselves are reasonably efficient.	2 / 5
Actionability	Copy-paste-ready commands cover install, login, connection, action search, action run, and proxy requests, with explained output fields and a flags table.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with explicit connection-state validation and a poll/handle feedback loop, but action-result verification is not addressed.	4 / 5
Progressive Disclosure	Sections are headed, but the ~140-line inlined entity list is content that belongs in a separate reference file (or should be removed), and no bundle files are used to offload detail.	3 / 5
	Total	14 / 20 Passed

Description

61%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 both what and when with a clear app-specific niche, but the action vocabulary is generic and trigger keywords are thin. It is distinctive but under-specific.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, update, and query Organizations, Leads, and Opportunities in Salespype."

Expand the trigger to include natural synonyms users say, e.g. "Use when the user wants to manage Salespype data — leads, opportunities, accounts, or pipeline records."

List 2-3 core entities beyond Organizations so the description reflects actual Salespype capabilities.

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names the domain and a target entity but uses a single generic verb; actions are minimal rather than concrete like create/update/delete.	2 / 5
Completeness	Both a "what" ("Salespype integration. Manage Organizations.") and an explicit "Use when the user wants to interact with Salespype data" trigger are present, though the when-clause is fairly generic.	4 / 5
Trigger Term Quality	"Salespype" and "Organizations" are relevant keywords, but common synonyms a user would say (leads, opportunities, sales pipeline) are absent.	3 / 5
Distinctiveness Conflict Risk	Binding to the named SaaS app "Salespype" gives a clear, unique niche with minimal overlap risk against other skills.	5 / 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/salespype/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.