Name: serply
Rating: 52 (1 reviews)
Author: membranedev

serply

Serply integration. Manage Leads, Persons, Organizations, Deals, Projects, Pipelines and more. Use when the user wants to interact with Serply data.

Quality

57%

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

Quality

Content

68%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 well-structured and actionable with executable CLI commands and a clear, validated connection workflow, but it is monolithic for a skill that could benefit from separating the proxy/flag reference and action catalog into bundle files.

Suggestions

Move the proxy request flag table and the action-discovery material into a reference file (e.g. references/README.md) and link to it from SKILL.md to improve progressive disclosure.

Add one fully worked end-to-end example that substitutes a real QUERY and CONNECTION_ID so the workflow is unambiguous.

Tighten the opening overview and the duplicated 'Discover before you build' guidance to remove the remaining padding.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, using short prose with executable commands and a compact flag table; the main padding is a one-line overview of what Serply is and a redundant restatement of 'Discover before you build', which is minor.	4 / 5
Actionability	Concrete, copy-paste-ready membrane CLI commands with --json flags and parameter examples cover the common cases; the only gap is that the placeholder QUERY and CONNECTION_ID are not fully tied to a worked end-to-end example.	4 / 5
Workflow Clarity	The connection setup is a clear sequenced flow (ensure -> poll --wait -> inspect state -> branch on READY/CLIENT_ACTION_REQUIRED/ERROR), with explicit polling feedback loops; the connection state handling reads as a genuine validate-then-branch checkpoint, with only minor gaps elsewhere.	4 / 5
Progressive Disclosure	There are no bundle files, so all reference material is inlined into SKILL.md; the content is sectioned, but the proxy flag table and popular-actions material that could live in a separate reference are all inline with no one-level-deep references to point to.	3 / 5
	Total	15 / 20 Passed

Description

46%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 identifies the domain and a useful list of entity types, and includes a trigger clause, but the actions are generic and the trigger language does not use the natural terms (keyword rankings, SERP, SEO) that users would actually say.

Suggestions

Replace generic 'Manage' with concrete actions a user wants, e.g. 'track keyword rankings, analyze SERP results, and manage Projects'.

Add natural trigger terms users say, such as 'keyword rankings', 'SERP tracking', or 'SEO position monitoring'.

Make the 'when' clause concrete: 'Use when the user wants to monitor keyword rankings or track SERP positions in Serply'.

Dimension	Reasoning	Score
Specificity	Names the domain (Serply) and lists concrete entity types ('Leads, Persons, Organizations, Deals, Projects, Pipelines') but stops short of concrete actions, relying on the generic 'Manage' and 'interact with Serply data'.	3 / 5
Completeness	It states a clear 'what' ('Manage Leads, Persons, Organizations...') and includes a 'Use when the user wants to interact with Serply data' trigger, but the 'when' is generic and not anchored to concrete user phrasing; per the boundary guidance a weakly-explicit when caps completeness at 3.	3 / 5
Trigger Term Quality	Only the domain name 'Serply' and 'interact with Serply data' are present; there are no natural keywords or synonyms a user would actually say when they need rank tracking, such as 'keyword rankings', 'SERP', or 'SEO'.	2 / 5
Distinctiveness Conflict Risk	The skill is anchored to a specific third-party product (Serply) and its named entities, making it largely distinct from other skills with only minor overlap risk with general CRM/SEO tooling.	4 / 5
	Total	12 / 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/serply/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.