CtrlK
BlogDocsLog inGet started
Tessl Logo

pubnub/pubnub-order-delivery-driver

Build real-time order tracking and delivery driver systems with PubNub

Does it follow best practices?

Evaluation94%

1.84x

Agent success when using this tile

Validation for skill structure

Overview
Skills
Evals
Files

Discovery

33%

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 identifies a clear domain (delivery/order tracking with PubNub) but lacks the specificity and completeness needed for reliable skill selection. It fails to list concrete actions the skill enables and critically omits any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when building delivery apps, tracking driver locations, or implementing real-time order status updates with PubNub'

List specific concrete actions such as 'track driver GPS location, send delivery ETAs, broadcast order status changes, implement geofencing alerts'

Include additional natural trigger terms users might say: 'delivery status', 'fleet management', 'logistics tracking', 'live location', 'courier tracking'

DimensionReasoningScore

Specificity

Names the domain (order tracking, delivery driver systems) and mentions PubNub, but lacks specific concrete actions like 'track driver location', 'send delivery notifications', or 'update order status in real-time'.

2 / 3

Completeness

Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

Includes relevant terms like 'order tracking', 'delivery driver', 'real-time', and 'PubNub', but misses common variations users might say like 'delivery status', 'driver location', 'fleet tracking', 'logistics', or 'live updates'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'order tracking', 'delivery driver', and 'PubNub' provides some distinctiveness, but 'real-time systems' is broad enough to potentially overlap with other real-time or messaging skills.

2 / 3

Total

7

/

12

Passed

Implementation

73%

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

This skill provides strong actionable guidance with executable code examples and good progressive disclosure through well-organized reference files. However, it could be more concise by removing the persona framing and 'When to Use' section, and the workflow would benefit from explicit validation checkpoints for a system handling real-time location data and order state transitions.

Suggestions

Remove the opening persona paragraph and 'When to Use This Skill' section - Claude can infer appropriate usage from the content itself

Add explicit validation steps to the Core Workflow, such as 'Verify GPS accuracy before publishing' and 'Confirm status transition was accepted before proceeding'

Include error handling feedback loops in the workflow for failed publishes, invalid state transitions, and reconnection scenarios

DimensionReasoningScore

Conciseness

The skill includes some unnecessary framing ('You are a specialist...') and the 'When to Use This Skill' section explains scenarios Claude could infer. The code examples are efficient, but the introductory sections add tokens without proportional value.

2 / 3

Actionability

Provides fully executable JavaScript code examples for GPS publishing, order tracking subscriptions, and status updates. Code is copy-paste ready with realistic patterns like adaptive publishing and channel naming conventions.

3 / 3

Workflow Clarity

The 6-step Core Workflow provides a clear sequence, but lacks explicit validation checkpoints. For a system involving real-time data and state machines, there's no feedback loop for verifying GPS accuracy, status transition validation results, or error recovery steps.

2 / 3

Progressive Disclosure

Well-structured with a clear overview, reference table pointing to three focused documents (delivery-setup.md, delivery-status.md, delivery-patterns.md), and inline code for key concepts. Navigation is one level deep and clearly signaled.

3 / 3

Total

10

/

12

Passed

Validation

94%

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

description_trigger_hint

Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')

Warning

Total

15

/

16

Passed

Install with Tessl CLI

npx tessl i pubnub/pubnub-order-delivery-driver

Reviewed

Table of Contents