CtrlK
BlogDocsLog inGet started
Tessl Logo

supabase-realtime

Supabase Realtime for live subscriptions, broadcasts, and presence. Use when implementing real-time features, live updates, chat, or online presence tracking.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-organized reference of executable Supabase Realtime patterns with good conciseness and useful status/cleanup checkpoints. Its main weakness is progressive disclosure: substantial detail is inlined in SKILL.md with only a single reference file linked.

Suggestions

Move the full React hook examples and advanced access-control/RLS detail into separate reference files, leaving SKILL.md as a tighter overview with clearly signaled links.

Consolidate the near-identical INSERT/UPDATE/DELETE postgres_changes examples into one parameterized example plus a small table of event variants to reduce redundancy.

Add a short validate/retry note for the subscription lifecycle (e.g. handling CHANNEL_ERROR by re-subscribing) to strengthen feedback-loop clarity.

DimensionReasoningScore

Conciseness

The body is mostly lean executable code with no concept-explanation padding, but the near-duplicate INSERT/UPDATE/DELETE subscription blocks add some redundancy that could be tightened, fitting the efficient-with-minor-trims anchor.

4 / 5

Actionability

Provides copy-paste-ready, executable code across all common cases (postgres changes, broadcast, presence, React hooks, cleanup), matching the fully-executable anchor covering common cases.

5 / 5

Workflow Clarity

As a catalog skill it has clear status checkpoints (acting only on SUBSCRIBED), an error-status section, and cleanup, but lacks explicit validate-fix-retry feedback loops, placing it at clear-sequence-with-minor-gaps rather than full checklists.

4 / 5

Progressive Disclosure

One reference (references/realtime-patterns.md) is clearly signaled at the bottom, but a large body inlines content that could be split (full React hooks, access-control detail), fitting the some-structure-but-content-should-be-separate anchor.

3 / 5

Total

16

/

20

Passed

Description

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

A strong, third-person description that clearly states both the capability set and explicit use-when triggers with natural language. It is specific and complete, with only minor overlap risk from broad trigger terms.

DimensionReasoningScore

Specificity

Names the Supabase Realtime domain plus three concrete capabilities ("live subscriptions, broadcasts, and presence"); lists several specific actions with only minor coverage gaps, so it sits above the 1-2-action anchor and below the fully-comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("live subscriptions, broadcasts, and presence") and when ("Use when implementing real-time features, live updates, chat, or online presence tracking") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"real-time features, live updates, chat, or online presence tracking" are natural phrases a user would say, with good coverage but missing common synonyms (e.g. websockets, subscriptions), fitting the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"Supabase Realtime" names a specific product niche with distinct triggers, though broad terms like "chat" and "live updates" carry minor overlap risk with generic realtime skills, placing it just below the minimal-conflict anchor.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.