Name: signals-scout-data-pipelines
Rating: 63.2 (1 reviews)
Author: PostHog

signals-scout-data-pipelines

Signals scout for PostHog data pipelines — CDP destinations and transformations, batch exports, and hog flows. Watches for delivery failures, degraded functions, and stalled exports against each pipeline's baseline, and files each validated delivery contradiction as a report in the inbox.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./products/signals/skills/signals-scout-data-pipelines/SKILL.md

Quality

Content

81%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 highly actionable with a clear, checkpointed workflow and dense domain-specific gotchas; its main weakness is moderate verbosity in the framing prose. It is a strong, operationally ready skill.

Suggestions

Tighten the opening framing paragraph and a few explanatory asides to reduce token cost without losing the signal-vs-noise mental model.

Consider extracting the MCP tools reference block into a references file so the core run workflow stays lean and scannable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dense with non-obvious domain knowledge (tool params, thresholds, state codes, footguns), but the opening framing paragraph and several prose explanations could be tightened without losing the mental model.	3 / 5
Actionability	Fully executable guidance throughout: copy-paste-ready SQL queries, exact tool calls with parameters, numeric thresholds (≥10% share, ≥50 triggered), state-code enumerations, and concrete key-naming conventions.	5 / 5
Workflow Clarity	A clearly sequenced run lifecycle (orient → profile → explore → save memory → decide → close out) with explicit validation checkpoints (fleet normalization, inbox search before authoring, dedupe gates) and feedback loops (edit-vs-author rules, edit-or-skip on relapse).	5 / 5
Progressive Disclosure	Well-organized single file with clear section headers and a reference-like MCP tools block; no bundle files exist, and most content is appropriately inline, though the tools reference and disqualifiers could arguably live in separate files.	4 / 5
	Total	17 / 20 Passed

Description

70%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, domain-rich, and clearly distinct, but it omits an explicit 'Use when' trigger clause, which caps its completeness. Adding a concrete trigger sentence would lift it into the top band.

Suggestions

Append an explicit 'Use when...' clause naming the situations that should invoke this skill (e.g. 'Use when monitoring PostHog data pipeline delivery health or investigating destination/transformation/batch-export/flow failures').

Broaden trigger-term coverage with a couple of natural user phrasings or synonyms (e.g. 'data delivery', 'event routing') so the skill surfaces for varied wording.

Dimension	Reasoning	Score
Specificity	Names the domain concretely ('PostHog data pipelines — CDP destinations and transformations, batch exports, and hog flows') and lists several specific actions ('Watches for delivery failures, degraded functions, and stalled exports', 'files each validated delivery contradiction as a report'), though the actions cluster around two verbs rather than a broad set.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Strong domain-natural terms a PostHog user would say ('data pipelines', 'CDP destinations', 'batch exports', 'hog flows', 'delivery failures'), but a few common trigger phrasings or synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	A sharply defined niche (PostHog CDP destinations/transformations, batch exports, hog flows) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: PostHog/posthog
Path: products/signals/skills/signals-scout-data-pipelines/SKILL.md
Commit: 31f2a90

Reviewed: about 21 hours 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.