CtrlK
BlogDocsLog inGet started
Tessl Logo

auditing-warehouse-source-coverage

Audit already-implemented Data warehouse import sources for endpoints, schemas, and tables the vendor's API offers but we never wired up. Use when asked whether a source is missing endpoints, to find new endpoints a vendor has added since a source was built, to refresh COVERAGE_GAPS.md, to prioritize which source to deepen next, or to check coverage before an integration review. Covers dumping our real endpoint inventory credential-free, ranking sources by production adoption, diffing against vendor OpenAPI/GraphQL specs, and recording findings. Not for implementing a source (use implementing-warehouse-sources), adding a vendor API version (warehouse-source-new-version), or writing source docs (documenting-warehouse-sources).

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is a tight, actionable, well-sequenced audit playbook with explicit validation checkpoints for its batch fan-out and a real, correctly-referenced helper script. Minor tightening of rationale prose and a more complete Python diff example would lift conciseness and actionability to 5.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — it never explains what a Data warehouse, OpenAPI, or GraphQL is, and quantitative facts ('~586 implemented sources', '6.8M subagent tokens', '4,540 findings') earn their tokens; a few rationale sentences could be trimmed.

4 / 5

Actionability

Provides copy-paste shell, SQL, Python, and grep snippets plus a real, executable linked script (scripts/dump_source_inventory.py); the Python diff snippet is a sketch rather than a full program, but that is explicitly justified.

4 / 5

Workflow Clarity

Six numbered steps are clearly sequenced with explicit validation checkpoints for this batch operation — bulk HTTP-status checks on cited doc_urls, end-to-end spot checks, and a blessed 'could-not-verify' answer — satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Well-organized into headed sections with a single real script referenced one level deep (verified present at scripts/dump_source_inventory.py) and a Related-skills navigation block; no nested reference chains, appropriate for its scope.

5 / 5

Total

18

/

20

Passed

Description

92%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 specific, trigger-rich, complete on both what and when, and clearly distinguished from sibling skills via explicit negative boundary guidance. The only minor gap is trigger-term synonym breadth, which keeps trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'dumping our real endpoint inventory credential-free', 'ranking sources by production adoption', 'diffing against vendor OpenAPI/GraphQL specs', and 'recording findings' — giving comprehensive coverage of the audit method.

5 / 5

Completeness

Explicitly answers both what (audit for missing endpoints/schemas/tables) and when (five concrete 'Use when...' triggers), with additional negative boundary guidance — matching the 5 anchor.

5 / 5

Trigger Term Quality

Strong natural triggers a user would actually say ('asked whether a source is missing endpoints', 'find new endpoints a vendor has added', 'refresh COVERAGE_GAPS.md', 'check coverage before an integration review'); just short of the exhaustive synonym/extension coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche plus an explicit 'Not for...' clause naming three sibling skills (implementing-warehouse-sources, warehouse-source-new-version, documenting-warehouse-sources) gives minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.