pubnub/pubnub-scale

Scale PubNub applications for high-volume real-time events

1.45x

Quality

61%

Does it follow best practices?

Impact

96%

1.45x

Average score across 15 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides solid, actionable guidance for PubNub scaling with executable code examples and specific performance thresholds. The progressive disclosure is well-structured with clear references. Main weaknesses are some unnecessary introductory content and missing validation checkpoints in the workflow for what could be impactful production changes.

Suggestions

Remove the 'You are a PubNub scaling specialist' framing and 'When to Use This Skill' section - Claude can infer when to apply this skill

Add validation steps to the Core Workflow, such as 'Verify channel group creation with listChannels()' and 'Test message throughput before production deployment'

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary framing ('You are a PubNub scaling specialist') and the 'When to Use This Skill' section explains things Claude could infer. The core technical content is appropriately lean.	2 / 3
Actionability	Provides fully executable JavaScript code examples for channel groups and wildcard subscriptions. Includes specific numeric guidelines (10-15 msg/sec, 32KB limit, 2000 channels per group) that are copy-paste ready.	3 / 3
Workflow Clarity	The 6-step core workflow is listed but lacks validation checkpoints. For scaling operations that could impact production systems, there's no explicit verify/rollback guidance or feedback loops for error recovery.	2 / 3
Progressive Disclosure	Clean structure with a concise overview, well-organized reference table pointing to one-level-deep files (scaling-patterns.md, performance.md, persistence.md), and clear navigation between sections.	3 / 3
	Total	10 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and incomplete to effectively guide skill selection. While it mentions PubNub specifically, it fails to describe concrete actions the skill performs and lacks any explicit trigger guidance for when Claude should use it. The description reads more like a tagline than a functional skill description.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Configure channel groups, optimize message batching, implement presence detection, set up access management').

Add an explicit 'Use when...' clause with trigger terms like 'PubNub', 'real-time messaging', 'pub/sub scaling', 'websocket performance', or 'chat infrastructure'.

Include common user scenarios or file types that would trigger this skill (e.g., 'when working with PubNub SDKs, configuring real-time features, or troubleshooting message delivery').

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'scale' and 'high-volume real-time events' without specifying concrete actions. It doesn't list what specific tasks or operations the skill performs (e.g., configure channels, optimize message throughput, set up presence).	1 / 3
Completeness	The description only vaguely addresses 'what' (scaling PubNub apps) and completely lacks any 'when' clause or explicit trigger guidance. There's no 'Use when...' or equivalent to help Claude know when to select this skill.	1 / 3
Trigger Term Quality	Contains 'PubNub' which is a specific and useful trigger term, and 'real-time events' is somewhat relevant. However, it's missing common variations users might say like 'websockets', 'pub/sub', 'messaging', 'chat', or 'notifications'.	2 / 3
Distinctiveness Conflict Risk	'PubNub' provides some distinctiveness as a specific platform, but 'scale applications' and 'real-time events' are generic enough to potentially overlap with other scaling, performance, or real-time messaging skills.	2 / 3
	Total	6 / 12 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
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning

	Total	15 / 16 Passed

Reviewed

4 months ago

Table of Contents

Discovery Implementation Validation