Configures Postgres triggers and database webhooks for event-driven architectures in Supabase.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
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 capabilities (Postgres triggers, pg_net configuration, webhook firing on DML events), includes natural trigger terms users would use, and provides explicit 'Use when' guidance. It occupies a well-defined niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating Postgres triggers, firing database webhooks to Edge Functions or external endpoints, handling INSERT/UPDATE/DELETE events, configuring pg_net for HTTP callouts and payload serialization. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates Postgres triggers for webhooks, configures pg_net) and 'when' with an explicit 'Use when' clause covering event-driven workflows, database webhooks, trigger-based notifications, and automated pipelines on table changes. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Postgres triggers', 'database webhooks', 'Edge Functions', 'INSERT/UPDATE/DELETE', 'event-driven workflows', 'trigger-based notifications', 'automated pipelines', 'table changes', 'pg_net'. Good coverage of both technical and conceptual terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Postgres triggers, pg_net, and database webhooks to Edge Functions. Unlikely to conflict with general database skills or general webhook skills due to the specific Postgres + trigger + webhook intersection. | 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 phased approach with pre-conditions, executable SQL examples for all event types, and a validation phase with HALT conditions makes it very robust. The only minor weakness is that all content is inline with no progressive disclosure to supplementary materials, though the skill's scope is focused enough that this is a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—pre-conditions, execution phases, examples, and validation. There's no explanation of what triggers or webhooks are, appropriately assuming Claude's competence with Postgres concepts. | 3 / 3 |
Actionability | Provides fully executable SQL examples for trigger functions, trigger creation across all three event types (INSERT/UPDATE/DELETE), and specific validation queries. The MCP tool usage is explicitly specified, and examples are copy-paste ready with clear substitution notes. | 3 / 3 |
Workflow Clarity | Clear three-phase sequence (Define Function → Create Trigger → Validate Deployment) with explicit validation in Phase 3 that checks both the trigger and function existence, plus HALT on failure. Pre-conditions also include explicit HALT directives for missing dependencies. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and phases, but it's entirely self-contained with no references to external files for advanced topics like custom payload formatting, retry logic, error handling patterns, or Edge Function setup. For its length (~80 lines of substantive content), some separation could improve organization. | 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