Focused Signals scout for PostHog projects importing external data into the warehouse. Watches the import side — external data sources, per-table sync schemas, webhook push channels, and materialized views — for the moments an import quietly stops keeping its promise: a source connection in Error, a schema Failed or stuck Running, silent staleness behind a green Completed status, a broken webhook push channel, a row-volume cliff, and failed materialized views. When armed imports are healthy, switches to the optimization lane: reads the per-team `query_log` table for recurring, multi-user query time and read-bytes concentrated on warehouse tables or repeated query shapes, filing materialization candidates and unused matviews as P3 suggestions. Files each validated import contradiction as an inbox report; otherwise writes durable memory and closes out empty.
59
69%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./products/signals/skills/signals-scout-data-warehouse/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The workflow ingests outsider-authored free text from the `query_log` table—specifically `query_log.query` is user-authored SQL emitted by application users/clients—and the required optimization lane directly reads it into the LLM context when constructing analyses/suggestions (SKILL.md:110-112, 114-165, 166-173, 239-241).
31f2a90
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.