CtrlK
BlogDocsLog inGet started
Tessl Logo

warehouse-source-new-version

Add support for a new vendor API version to an existing Data warehouse import source, or deprecate an old one. Use when a vendor ships a new API version (Stripe date versions, Shopify quarterly versions, header-pinned revisions, /vN/ URL bumps), when implementing a version-update or deprecation task for a source under products/warehouse_sources/backend/temporal/data_imports/sources, or when repinning an ExternalDataSource to a different version. Covers deciding whether a newly announced version needs supporting at all, version declaration, dispatch, pinning semantics, deprecation metadata, and migration scripts.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a dense, domain-specific instruction set with concrete paths, dispatch patterns, and a gated multi-step workflow, but it leans verbose and ships as one large monolith with no progressive disclosure into separate reference files.

Suggestions

Tighten the densest sections (e.g. step 3's nested sub-bullets and the 'Common pitfalls' list) by collapsing redundant caveats and merging opposing-case pairs into single conditional statements.

Extract large reference blocks — 'Common pitfalls' and 'Pinning semantics' — into separate referenced files (e.g. references/pitfalls.md) so the body stays an overview.

Add a short validation feedback loop in the deprecation workflow (e.g. verify deprecated ⊆ supported and default-not-deprecated via test_source_versions.py before opening the PR) to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and avoids generic concept explanation, but is densely qualified with heavy hedging and redundant caveats (e.g. the many 'Conversely'/'The opposite holds' branches) that could be tightened without losing meaning.

3 / 5

Actionability

Concrete file paths, named dispatch patterns (Stripe's resolve_api_version chain), specific test files (test_source_versions.py), and explicit migration rules give mostly executable guidance; minor gaps as it is instruction-only without runnable code.

4 / 5

Workflow Clarity

A clear two-track sequence ('Adding a new version, step by step' and 'Deprecating a version') with an explicit decision gate ('First: does the version need to exist at all?') and a tests checkpoint; minor validation gaps keep it below 5.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a single ~28KB monolith with all material inline; sections like 'Common pitfalls' and 'Pinning semantics' could be split into referenced files for easier navigation, though the in-file sectioning is reasonable.

3 / 5

Total

14

/

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 strong across all dimensions: it names a precise niche, enumerates concrete capabilities, and supplies explicit, natural 'Use when' triggers covering several versioning schemes. It is third-person and free of vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'version declaration, dispatch, pinning semantics, deprecation metadata, and migration scripts' — with comprehensive coverage of the version lifecycle, matching the 5-anchor example.

5 / 5

Completeness

Explicitly answers both what ('Add support for a new vendor API version... or deprecate an old one') and when ('Use when a vendor ships a new API version...', 'when implementing a version-update or deprecation task...', 'when repinning...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural triggers including 'vendor ships a new API version', 'Stripe date versions', 'Shopify quarterly versions', 'header-pinned revisions', '/vN/ URL bumps', 'repinning an ExternalDataSource' — covering synonyms and concrete versioning schemes.

5 / 5

Distinctiveness Conflict Risk

Clear niche — vendor API versioning for warehouse import sources under a specific product path — with distinct triggers and minimal conflict risk against 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.

Validation — 16 / 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.