Name: stannp
Rating: 56.8 (1 reviews)
Author: membranedev

stannp

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

Quality

65%

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

Quality

Content

67%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 delivers highly actionable, executable CLI guidance with a clear connection-readiness feedback loop and good section structure. Its main weaknesses are token waste from a marketing intro, a flat 50-item entity list, and a redundant Popular actions section.

Suggestions

Trim the marketing intro and collapse the 50-item flat entity bullet list into grouped categories (e.g., Mail, Commerce, Tracking) to save tokens.

Remove or merge the "Popular actions" section, which only repeats the action-list command already shown under "Searching for actions".

Label the connecting workflow steps consistently (add an explicit Step 1) so the "Skip to Step 2" reference resolves.

Dimension	Reasoning	Score
Conciseness	The CLI instructions are tight, but the marketing intro ("It allows businesses to design, print, and send physical mail campaigns…"), a flat 50-item entity bullet wall, and a redundant "Popular actions" section that repeats the search command add unnecessary tokens, matching anchor 3.	3 / 5
Actionability	Copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action run with --input JSON, request proxy) alongside a complete proxy flag table, with only minor gaps such as the --tenant flag shown without a value, fitting anchor 4.	4 / 5
Workflow Clarity	A clear install→auth→connect→poll→search→run sequence includes a real feedback loop over connection states (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), though it references "Step 2" with no labeled Step 1, matching anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline under well-organized section headers with no nested references; the flat entity list and duplicated "Popular actions" section are minor organization gaps rather than structural problems, fitting anchor 4.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers both what and when in third person with an explicit trigger, but its action vocabulary is limited to the generic verb "Manage" and it omits the natural niche terms that define Stannp. It is solidly competent yet leaves specificity and trigger coverage underdeveloped.

Suggestions

Replace the single verb "Manage" with concrete Stannp actions (e.g., "Design, send, and track direct mail campaigns; manage recipients, templates, and postcards").

Add the natural trigger phrases users actually say — "direct mail", "postcards", "mail campaigns" — to the Use-when clause instead of the generic "interact with Stannp data".

Align the entity list with Stannp's real domain (Campaigns, Recipients, Templates, Postcards) rather than the generic CRM entities currently named.

Dimension	Reasoning	Score
Specificity	Names six concrete entities ("Persons, Organizations, Leads, Deals, Projects, Activities") but the only action verb is the generic "Manage", so coverage sits above anchor 2 (minimal actions) yet below anchor 4 (several specific actions).	3 / 5
Completeness	Both "what" ("Manage Persons…") and "when" ("Use when the user wants to interact with Stannp data") are present and explicit, though the when-clause is generic rather than trigger-phrase rich, matching anchor 4.	4 / 5
Trigger Term Quality	The explicit trigger "Use when the user wants to interact with Stannp data" and brand name "Stannp" give some relevant keywords, but the natural niche terms (direct mail, postcards, campaigns) that appear in the body are missing from the description.	3 / 5
Distinctiveness Conflict Risk	The "Stannp" brand carves a clear niche with minimal conflict risk, but the generic CRM-style entity list (Persons, Leads, Deals) carries minor overlap risk with similar skills, fitting anchor 4.	4 / 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/stannp/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.