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

Blog Docs Log in Get started

bump

Bump integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bump 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/bump/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 is a strong, command-driven integration guide with a well-instrumented connection state machine and good actionability. Its main weaknesses are an unnecessary introductory background paragraph and a couple of minor workflow/consistency gaps.

Suggestions

Delete or trim the opening historical paragraph about what Bump is; Claude does not need product background to drive the CLI.

Label the workflow steps consistently (define 'Step 1' and 'Step 2') so 'skip to Step 2' has a real target.

Standardize on one invocation form ('membrane' vs 'npx @membranehq/cli@latest') throughout to avoid confusion.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening paragraph explaining what Bump is and its history ('popular among smartphone users... before more advanced sharing methods became commonplace') is unnecessary background Claude does not need; not a 4 because that filler is more than minor.	3 / 5
Actionability	Provides many copy-paste-ready commands (install, login, connection ensure, action list/run, request) covering common cases; not a 5 because of placeholders (CONNECTION_ID, actionId) and inconsistent invocation ('membrane' vs 'npx @membranehq/cli').	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop; not a 5 because 'skip to Step 2' references a Step 2 that is never labeled.	4 / 5
Progressive Disclosure	Content is organized into clear sections with no nested external references and no bundle files to navigate; not a 5 because some inline material (the proxy options table, popular actions) could be split out for a cleaner overview.	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 covers both what the skill does and when to use it with an explicit trigger clause, and the named app gives it a clear niche. It is held back by generic action verbs and thin trigger-term coverage.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete Bump-specific actions (e.g., 'send contact info, share photos and files between phones').

Expand the trigger clause with natural synonyms users might say (e.g., 'Use when the user mentions Bump, wants to bump phones to share contacts/photos, or transfer files via Bump').

Dimension	Reasoning	Score
Specificity	Names the Bump domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not a 2 because multiple action areas are named.	3 / 5
Completeness	Both 'what' (Bump integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Bump data') are present; not a 5 because the 'what' is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	Includes relevant natural terms ('Bump', 'interact with Bump data') but offers no synonyms or variations users might say; not a 4 because keyword coverage is thin for the niche.	3 / 5
Distinctiveness Conflict Risk	Bump is a specific named app giving it a clear niche with minimal conflict risk; not a 5 because the generic action phrasing ('manage data, records') could overlap with other integration skills.	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/bump/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.