CtrlK
BlogDocsLog inGet started
Tessl Logo

pubnub

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

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/pubnub/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, largely executable guide to driving PubNub through the Membrane CLI, with strong command coverage and a clear connection state machine. Its main weaknesses are the missing verification around destructive proxy/run operations and a few minor structural and conciseness nits.

Suggestions

Add a verification step after running actions or issuing proxy requests, especially for destructive methods (DELETE/PUT/POST), so the workflow validates results before proceeding.

Fix the numbering inconsistency: "skip to Step 2" references a step that is never labeled, so explicitly number the connect/search/run sequence.

Trim the opening paragraph explaining what PubNub is, since it restates concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete commands and a flag table, with only minor over-explanation such as the opening paragraph describing what PubNub is and "It's used by companies needing scalable and reliable real-time data streaming."

4 / 5

Actionability

It provides concrete, executable CLI commands (install, login, connection ensure, action run, request) and a proxy flag table, but examples lean on placeholders like CONNECTION_ID and "QUERY" rather than fully copy-paste-ready concrete cases.

4 / 5

Workflow Clarity

The connection phase has good state-driven checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the proxy and action-run paths support destructive methods (DELETE/PUT) with no verification step, and there is a dangling "Step 2" reference with no labeled Step 1 or 2.

3 / 5

Progressive Disclosure

The content is organized into clear sections with no external bundle files (none are needed), though the sparse "PubNub Overview" hierarchy and the >50-line length keep it just short of the lean well-organized ideal.

4 / 5

Total

15

/

20

Passed

Description

66%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 cleanly answers both what and when and is highly distinct thanks to the named PubNub trigger, but it is weakened by generic, non-concrete action verbs and thin synonym coverage. Tightening the action list to real PubNub operations would lift it further.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete PubNub actions such as publishing/subscribing to messages, managing channels and channel groups, and fetching message history.

Add natural trigger synonyms users would actually say, e.g. real-time messaging, pub/sub, live updates, or chat, alongside "PubNub data".

DimensionReasoningScore

Specificity

The description names the domain ("PubNub integration") and enumerates actions, but the verbs are generic and abstract ("Manage data, records, and automate workflows") rather than concrete PubNub actions like publishing messages or managing channels.

3 / 5

Completeness

It states both what it does ("PubNub integration. Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with PubNub data"), with the 'what' side being generic enough to leave room for improvement.

4 / 5

Trigger Term Quality

The natural keyword "PubNub" is present ("interact with PubNub data"), but coverage of synonyms or common variations a user might say is thin, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

PubNub is a specific named platform and the trigger ("interact with PubNub data") is a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.