CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnosing-failed-warehouse-syncs

Diagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks "why isn't my Stripe/Postgres/Hubspot sync working?", "this table has been stuck for hours", "the data in the warehouse looks wrong", or wants to troubleshoot a specific source or schema. Covers source-level vs schema-level failures, stuck Running states, credential and schema-drift errors, incremental-field misconfig, CDC prerequisite failures, and the cancel / reload / resync / delete-data recovery actions.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is highly actionable with a clear, validated workflow and concrete tool calls throughout; its only weakness is mild repetition between the workflow steps and the Important notes section, plus a single-file structure that could shed some reference material.

Suggestions

Remove the redundancy between 'Important notes' and the workflow steps — e.g. 'Resync is destructive' already appears in Step 5 and 'Running isn't always healthy' in Step 2 — keeping one authoritative location.

Consider moving the Step 3 error-substring mapping table and the Step 4 A–I recovery catalog into a references/ file, leaving SKILL.md as a tighter overview that points to the detailed tables.

Tighten the webhook Step I narration by leading with the tool call sequence and pruning the explanatory prose around each branch.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence without explaining basics, but the 'Important notes' section restates points already made in Step 5 (resync is destructive) and Step 2 (Running isn't always healthy), which could be trimmed.

4 / 5

Actionability

Provides exact tool names with parameters (e.g. external-data-sources-partial-update({id}, {job_inputs: {stripe_secret_key: ...}})), an error-substring to root-cause to fix mapping table, and a numbered webhook call sequence — fully executable and copy-paste ready.

5 / 5

Workflow Clarity

A clear 5-step sequence (locate → classify → interpret error → pick recovery → confirm before destructive) with an explicit approval gate before destructive actions and feedback loops (cross-check last_synced_at; retrieve detail when latest_error is null), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with clear headers and inline tables that are needed at decision time, though the sizable error and recovery-action tables could optionally be split into a reference file to shorten the overview.

4 / 5

Total

18

/

20

Passed

Description

100%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 is exemplary: it states concrete capabilities, embeds natural trigger phrases users would actually say, and cleanly separates what from when, all in a distinct niche with minimal conflict risk.

DimensionReasoningScore

Specificity

Names multiple concrete actions (diagnose the failing sync, recommend the recovery action, troubleshoot a source/schema) and comprehensively enumerates failure types and the cancel/reload/resync/delete-data recovery verbs.

5 / 5

Completeness

Explicitly answers both what (diagnose failures and recommend recovery, covering named failure categories) and when (a 'Use when...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Embeds verbatim user phrasings ('why isn't my Stripe/Postgres/Hubspot sync working?', 'this table has been stuck for hours', 'the data in the warehouse looks wrong') plus source synonyms, covering the natural terms users actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — warehouse sync diagnosis for named sources with specific recovery actions — making it unlikely to trigger for unrelated skills.

5 / 5

Total

20

/

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
PostHog/posthog
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.