Name: documenting-warehouse-sources
Rating: 70.39999999999999 (1 reviews)
Author: PostHog

documenting-warehouse-sources

Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source. Use when adding a new source doc, fixing an inconsistent or stub source doc, or standardizing the docs at contents/docs/cdp/sources. Covers the canonical template, shared snippets, the auto-rendered <SourceParameters /> and <SourceTables /> components, frontmatter, and the docsUrl/slug rule that prevents 404s.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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.

A highly actionable, well-structured body built around a copy-paste canonical template and an explicit audit/validation step. It loses points only on minor conciseness trimming, an implicit rather than numbered validation retry loop, and a monolithic layout that could benefit from a bundled reference file.

Suggestions

Make the validation feedback loop explicit: after `audit_source_docs`, add a numbered 'if it fails, fix the flagged sourceId/docsUrl and re-run until it passes' step instead of only stating the failure mode.

Consider extracting the canonical template and shared-snippets catalog into a bundled reference file (e.g. references/template.md) so SKILL.md stays a lean overview rather than a ~150-line monolith.

Trim the inline <SourceTables /> opt-in explanation (the static-endpoint-catalog caveat) and link to /implementing-warehouse-sources for the detail instead of restating it here.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence, sticking to repo-specific facts (template, frontmatter, snippet names, audit command), but explanatory prose such as the <SourceTables /> static-endpoint-catalog caveat could be trimmed by deferring to /implementing-warehouse-sources.	4 / 5
Actionability	It provides a copy-paste-ready canonical template with real frontmatter and imports, concrete file paths, named shared snippets, and an executable validation command (`python manage.py audit_source_docs --docs-dir ...`), covering the common authoring cases.	5 / 5
Workflow Clarity	The "Essential sections" list gives a clear section sequence and the audit command plus closing checklist provide explicit validation, but the validate -> fix -> re-run feedback loop is described by its failure mode ("It fails if...") rather than spelled out as numbered recovery steps, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	Structure is good with clear section headers and well-signaled pointers to the sibling /implementing-warehouse-sources skill and repo files, but the ~150-line body is monolithic with no bundle reference files; the template/snippet catalog could be split out to keep SKILL.md a leaner overview.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

A strong, well-scoped description that clearly states what the skill does and when to use it with concrete, repo-specific triggers. The only soft spot is specificity, where the action verbs are limited even though the coverage list is comprehensive.

Dimension	Reasoning	Score
Specificity	"Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source" names the domain and two concrete actions, and the "Covers the canonical template, shared snippets, the auto-rendered <SourceParameters /> and <SourceTables /> components, frontmatter, and the docsUrl/slug rule" list gives broad concrete coverage, though the verbs themselves are limited to write/update.	4 / 5
Completeness	It explicitly answers both what ("Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source") and when ("Use when adding a new source doc, fixing an inconsistent or stub source doc, or standardizing the docs"), with concrete trigger phrases — a clear 5-anchor match.	5 / 5
Trigger Term Quality	"Use when adding a new source doc, fixing an inconsistent or stub source doc, or standardizing the docs at contents/docs/cdp/sources" supplies several natural trigger phrases a user would plausibly say, with good though not exhaustive keyword/synonym coverage.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to PostHog Data warehouse import sources and the posthog.com cdp/sources doc path, with repo-specific triggers that make overlap with unrelated skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: .agents/skills/documenting-warehouse-sources/SKILL.md
Commit: 6fca5f8

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.