CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pubnub-scale

Scale PubNub applications for high-volume real-time events using channel groups, wildcard subscriptions, sharding, and large-event readiness. Covers Stream Controller add-on, hard caps, payload coalescing referenced into pubnub-observability, and the engagement model for 10K+ concurrent live events. Persistence/history is owned by pubnub-history.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pubnub-scale/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

Well-structured and token-efficient with strong progressive disclosure and a clear workflow, but actionability is held back because the headline channel-group and sharding patterns point to MCP retrieval and reference files instead of providing concrete executable examples in the body.

Suggestions

Add a minimal executable channel-group subscribe/create example inline (analogous to the wildcard snippet) so the most common scaling action is copy-paste ready.

Tighten the 'When PubNub MCP tools are absent' blockquote to the essential fallback rule to recover a point on conciseness.

Insert one explicit validation checkpoint in the Core Workflow (e.g. 'Verify Stream Controller is enabled on the keyset before subscribing to groups') to push workflow clarity to 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no boilerplate about what PubNub is — with only minor padding in the 'When PubNub MCP tools are absent' blockquote that could be tightened.

4 / 5

Actionability

One executable snippet (wildcard subscribe) and concrete constraints (max two dots, must end with .*) are present, but the core channel-group and sharding patterns defer to 'retrieve via get_sdk_documentation' and reference files rather than giving copy-paste code, leaving key details implicit.

3 / 5

Workflow Clarity

The 6-step Core Workflow (Assess → Design → Optimize → Enable Stream Controller → Plan Large Events → Monitor) is a clear sequence with a monitoring checkpoint; this is a design/planning skill so the destructive-batch cap does not apply, though explicit validate-before-proceeding loops are absent.

4 / 5

Progressive Disclosure

SKILL.md acts as an overview with a Reference Guide table and inline links to verified one-level-deep bundle files (references/scaling-patterns.md, references/large-events.md) plus a clearly signaled See Also section, giving easy navigation.

5 / 5

Total

16

/

20

Passed

Description

70%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 specific, well-triggered, and clearly distinct from sibling skills, but it omits an explicit 'when to use' clause, which limits its completeness score. Adding a 'Use when...' sentence would lift it into the top band.

Suggestions

Add an explicit 'Use when...' clause naming the triggering scenarios (e.g. 'Use when designing for 10K+ concurrent users, high publish rates, or sharded feeds').

Lead with the concrete action verbs (e.g. 'Design channel-group topologies, shard feeds, plan large live events') rather than a single 'Scale' verb to push specificity to 5.

DimensionReasoningScore

Specificity

Names multiple concrete techniques — 'channel groups, wildcard subscriptions, sharding, and large-event readiness' — giving broad coverage of the scaling domain, though the single verb 'Scale' keeps it just shy of a fully comprehensive action list.

4 / 5

Completeness

The 'what' is clear ('Scale PubNub applications for high-volume real-time events using...'), but there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Strong natural keywords ('PubNub', 'scale', 'channel groups', 'wildcard subscriptions', 'sharding', '10K+ concurrent live events') that users would plausibly say, with good synonym coverage, but a few common phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (PubNub scaling) with distinct triggers, and it explicitly carves out boundaries against pubnub-history and pubnub-observability, minimizing conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 18 suspicious

Warning

Total

15

/

16

Passed

Repository

pubnub/skills

Path

pubnub-scale/SKILL.md

Reviewed

Table of Contents

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.