Name: pumble
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pumble

Pumble integration. Manage Workspaces. Use when the user wants to interact with Pumble data.

Quality

61%

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

Quality

Content

61%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 strong executable CLI commands and a reasonable connection workflow with state feedback, but it is padded with marketing fluff, has a dangling 'Step 2' reference, and omits validation for action execution. Structure is good for a single-file skill with minor redundancy.

Suggestions

Remove the marketing description of Pumble ('used by businesses of all sizes to streamline internal communications...'); keep only the orienting 'similar to Slack' fact if needed.

Fix the dangling 'skip to Step 2' reference by labeling the workflow steps (Step 1, Step 2) or removing the cross-reference.

Add a validation/verification step after running actions (e.g., check the `output` field for errors or confirm the action's effect), since actions can be destructive such as sending or deleting messages.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational guidance, but the opening marketing paragraph ('used by businesses of all sizes to streamline internal communications, manage projects, and improve team productivity') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding.	3 / 5
Actionability	Provides concrete, copy-pasteable bash commands for install, auth, connect, search, run, and proxy, with only minor gaps — generic <actionId> placeholders and no Pumble-specific action example.	4 / 5
Workflow Clarity	The connection flow has good state-based checkpoints and polling feedback, but the 'skip to Step 2' reference points to no labeled Step 2, and action execution lacks output validation.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references, though it is a single ~140-line file with some redundant sections ('Searching for actions' vs 'Popular actions') and no progressive file split.	4 / 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 is clearly tied to a distinct product niche and includes an explicit trigger clause, but its capability list is minimal ('Manage Workspaces') and omits most of what the skill actually does. Trigger terms cover the brand but miss common entity-level variations.

Suggestions

Expand the 'what' beyond 'Manage Workspaces' to mention the key entities you actually handle (users, channels, messages, direct messages) so capabilities are concrete.

Add natural trigger terms users would say — e.g., 'send messages', 'manage channels', or 'team chat' — alongside 'Pumble' to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Pumble domain and only one generic action ('Manage Workspaces'), omitting channels, messages, and users — actions are minimal and generic rather than concrete.	2 / 5
Completeness	Has both a 'what' ('Manage Workspaces') and an explicit 'when' ('Use when the user wants to interact with Pumble data'), though the 'what' is thin and could be more specific.	4 / 5
Trigger Term Quality	Includes 'Pumble' and 'Workspaces' as relevant keywords but misses common variations a user would naturally say, such as channels, messages, or team chat.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product (Pumble) with a clear trigger, giving it a distinct niche and minimal conflict risk with 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/pumble/SKILL.md
Commit: f484c82

Reviewed: 5 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.