Orchestrates long-running Edge Function work via waitUntil, pg_cron, and pgmq patterns.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that clearly articulates specific technical capabilities, includes a well-formed 'Use when' clause with natural trigger terms, and occupies a distinct niche. It uses proper third-person voice, avoids vague language, and provides enough detail for Claude to confidently select this skill when users need background processing patterns with Supabase Edge Functions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring Edge Functions with EdgeRuntime.waitUntil, returning immediate 200 OK, routing workloads through pg_cron discovery, and pgmq task queuing. These are precise, technical, and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (configures Edge Functions with waitUntil, routes workloads through pg_cron and pgmq) and 'when' (explicit 'Use when' clause covering background processing, async third-party calls, long-running tasks, webhook-driven pipelines). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'background processing', 'async', 'long-running edge function tasks', 'webhook-driven pipelines', 'Edge Functions', 'pg_cron', 'pgmq', 'waitUntil'. Good coverage of both high-level concepts and specific technology terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: the combination of Edge Functions, EdgeRuntime.waitUntil, pg_cron, and pgmq creates a very specific domain. Unlikely to conflict with general edge function or database skills due to the precise architectural pattern described. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and workflow clarity. The decision gate cleanly separates two implementation paths, each with complete executable examples and explicit constraints. The only minor weakness is that all content is inline, though the overall length is reasonable enough that this is a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Edge Functions, pg_cron, or pgmq are, assuming Claude's competence. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript and SQL code examples that are copy-paste ready. The decision gate table, specific constraints (e.g., 'NEVER set pg_cron interval below 10 seconds'), and concrete commands make guidance highly actionable. | 3 / 3 |
Workflow Clarity | Clear four-phase sequence with explicit decision gate, validation checkpoints in Phase 4, and HALT-on-failure instruction. Each phase has numbered steps with clear transitions ('proceed to Phase 4'). The verification phase includes specific checks for both implementation paths. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a decision gate table, but everything is inline in a single file. The pg_cron + pgmq pattern and the waitUntil pattern could potentially be split into separate reference files for better navigation, though the current length is manageable. | 2 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents