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

Blog Docs Log in Get started

showpad

Showpad integration. Manage Organizations. Use when the user wants to interact with Showpad 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/showpad/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 content is actionable and well-structured, with real executable Membrane commands, a useful flag table, and a sequenced connection workflow that includes polling and state-handling checkpoints. Its main weaknesses are an unnecessary background paragraph, a dangling "Step 2" reference with unnumbered steps, and no progressive file-splitting despite some content that could live in references.

Suggestions

Remove the opening background paragraph about what Showpad is and who uses it; Claude does not need it to run the integration.

Fix the step numbering: either number the workflow steps (1, 2, 3...) and define "Step 2", or replace the "skip to Step 2" references with concrete section anchors.

Move the proxy flag table and the detailed connection-state handling into a separate reference file (e.g., references/proxy.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands and a flag table, but opens with an unnecessary background paragraph ("Showpad is a sales enablement platform that helps sales and marketing teams improve buyer engagement...") and a few padded prose asides that Claude does not need, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action run, request) plus a flag table, but examples rely on placeholders and the "Popular actions" section points back to discovery rather than listing any, leaving minor gaps that keep it from a 5.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checks and a poll-until-ready feedback loop (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but it references a non-existent "Step 2" and uses unnumbered steps (only "1b" appears), a minor clarity gap below a 5.	4 / 5
Progressive Disclosure	The single-file skill is well-organized with clear section headers and no nested references, but no bundle files exist and content is not split into separate reference files (e.g., the proxy flag table or connection-state details), so it does not reach the well-signaled one-level-deep references ideal of a 5.	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 correctly uses third-person voice and includes an explicit "Use when" trigger, but it is sparse: it names only one action (Manage Organizations) while the body reveals several resource types, and its trigger phrasing is generic. Distinctiveness is strong mainly because of the Showpad brand name.

Suggestions

Expand the "what" to enumerate the actual capabilities shown in the body (e.g., manage Files, Folders, Shares, Users, and Tags) instead of only "Manage Organizations".

Make the "when" trigger more concrete with natural phrases a user would say, e.g., "Use when the user wants to query or manage Showpad files, shares, users, or tags."

Add synonyms/variations of trigger terms (e.g., "Showpad data", "Showpad content") to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Showpad integration") and one concrete action ("Manage Organizations"), matching the anchor for naming a domain plus 1-2 actions without comprehensive coverage; it does not list the several specific actions (Files, Folders, Shares, Users, Tags) shown in the body.	3 / 5
Completeness	Provides both a "what" ("Showpad integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Showpad data."), but the what is narrow and the when is generic rather than a concrete trigger phrase, so it falls short of a 5.	4 / 5
Trigger Term Quality	Includes the natural primary keyword "Showpad" and "interact with Showpad data", but lacks synonyms, variations, or file extensions, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The "Showpad" brand gives it a distinct niche with low conflict risk, but the sparse, generic action wording ("Manage Organizations", "interact with Showpad data") leaves minor overlap risk with generic data-management skills, keeping it just below a clean 5.	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/showpad/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.