Name: pushbots
Rating: 55.2 (1 reviews)
Author: membranedev

pushbots

PushBots integration. Manage data, records, and automate workflows. Use when the user wants to interact with PushBots data.

Quality

62%

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/pushbots/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 highly actionable with executable Membrane commands and a clear connection workflow including state-based feedback loops. Its main weakness is the padded marketing intro and occasional over-explanation that slightly dilute token efficiency.

Suggestions

Trim the opening paragraph to one line stating what PushBots does and the docs link; drop marketing language about retention and conversions.

Resolve the dangling 'Step 2' reference and renumber the connection substeps consistently so the sequence is unambiguous.

Cut conversational filler such as 'so you can focus on the integration logic rather than auth plumbing'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening marketing paragraph ('PushBots is a platform that allows developers and marketers...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' add explanation Claude does not need.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands for install, auth, connection, action search/run, and proxying, with only minor placeholder gaps (CONNECTION_ID, <agentType>).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling, though the dangling 'Step 2' reference and a minor numbering hiccup ('1b' before the search step) leave a small gap.	4 / 5
Progressive Disclosure	The single file is well organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Best practices) with no nested references; a few inlined sections like the proxy flag table could arguably live apart, so it is not a clean 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 has an explicit 'Use when' trigger and a distinctive brand name, but its action language is generic and it omits the core push-notification capability and natural terms users would say. Tightening the verbs and adding 'push notifications' would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records') with concrete PushBots actions such as 'Send push notifications, segment audiences, and run campaigns'.

Add natural trigger terms users actually say — e.g. 'Use when the user wants to send push notifications or manage PushBots campaigns and devices'.

Mention the core capability (push notifications) explicitly so the description reflects what PushBots actually does.

Dimension	Reasoning	Score
Specificity	The description names the domain (PushBots) but the actions are generic — 'Manage data, records, and automate workflows' — and it never mentions the actual capability (push notifications), so the actions are minimal/generic rather than concrete.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with PushBots data'), though the 'when' could be more specific about notification-related triggers.	4 / 5
Trigger Term Quality	It includes the brand keyword 'PushBots' and 'data', but misses the most natural user phrases like 'push notifications', 'notifications', or 'campaigns', so common variations are absent.	3 / 5
Distinctiveness Conflict Risk	The PushBots brand name gives it a clear niche and distinct trigger with only minor overlap risk against generic data-management skills.	4 / 5
	Total	13 / 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/pushbots/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.