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

Blog Docs Log in Get started

pusher

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

Quality

63%

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

Quality

Content

68%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 highly actionable with thorough, executable Membrane CLI guidance and a solid connection-state workflow, but it is held back by an unnecessary introductory explanation of Pusher and a lack of validation checkpoints around destructive proxy and action operations.

Suggestions

Remove or heavily trim the opening paragraph explaining what Pusher is and the filler line 'Use action names and parameters as needed.'; assume Claude already knows the product.

Add a validation/verification checkpoint before destructive operations, e.g. recommend a dry-run or GET to confirm a resource before `membrane request ... -X DELETE`, and advise checking the `output`/`error` fields after every action run.

Fix the dangling 'Step 2' reference (the 'Connecting to Pusher' section references 'Step 2' but no steps are numbered) and flesh out the sparse 'Pusher Overview' section so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI commands, but the opening paragraph over-explains what Pusher is (a concept Claude already knows), the line 'Use action names and parameters as needed.' is filler, and the action-list invocation is restated with minor redundancy.	3 / 5
Actionability	The body provides copy-paste-ready, executable commands for every stage (install, login, connection ensure/get with --wait, action list/search, action run with --input, proxy request) plus a complete flags table, covering the common cases.	5 / 5
Workflow Clarity	A clear sequence exists with connection-state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but destructive proxy methods (DELETE) and action runs lack any validation/verification step, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	The single file is well-organized into clearly headed sections with no nested references, but at ~140 lines with no content split into reference files and a dangling 'Step 2' reference plus a sparse 'Pusher Overview' section, it has minor organization gaps rather than the clean one-level-deep split of a score-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 successfully pairs a clear product niche with an explicit trigger clause, but its capability verbs are generic rather than Pusher-specific. Tightening the actions to concrete Pusher operations and adding real-time/channel/event keywords would lift it from the middle of the scale.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Pusher actions such as 'trigger channel events, manage channels and users, and subscribe to real-time updates'.

Expand the trigger clause with natural synonyms a user would say, e.g. 'Use when the user wants to send or receive real-time messages, trigger Pusher channel events, or manage Pusher channels and users'.

Add file-format or product-specific trigger terms (channels, events, webhooks) to improve keyword coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Pusher integration') but its actions are generic ('Manage data, records, and automate workflows') rather than concrete Pusher capabilities like channels, events, or triggering messages.	2 / 5
Completeness	It has both a 'what' (manage data, records, automate workflows) and an explicit 'Use when...' trigger, but the 'what' is generic and the 'when' could be more specific, fitting the score-4 anchor better than score 5.	4 / 5
Trigger Term Quality	'Pusher' and the trigger phrase 'interact with Pusher data' are relevant, but common natural variations a user might say (channels, events, real-time messages, notifications) are absent.	3 / 5
Distinctiveness Conflict Risk	'Pusher' as a named product gives a clear, distinct niche with minimal conflict risk, though the generic action verbs ('manage data, records, automate workflows') create minor overlap with other data-integration 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/pusher/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.