Name: signals
Rating: 72 (1 reviews)
Author: PostHog

signals

How to query the document_embeddings table for raw signal data using HogQL. Use when you need to perform semantic search over signals, fetch every signal that contributed to a specific report, or list signal types. For browsing the curated report layer (the Inbox) — listing reports, filtering by status/source, drilling into a single report by ID — use the `inbox-exploration` skill first; drop into this skill afterwards if the user wants the underlying observations.

Quality

87%

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

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 query skill with five executable examples and thorough reference tables. Minor conciseness gains are available by de-duplicating the Gotchas section against the prose above, and the long single-file form could optionally split reference material out.

Suggestions

Collapse the Gotchas list to only net-new warnings, cross-referencing the Mandatory Filters and Deduplication sections instead of restating them, to reduce redundancy.

Consider moving the column reference and metadata-field tables into a reference file linked from the body, shortening SKILL.md and aiding progressive disclosure.

Add a one-line 'prerequisite' note that these queries run via the posthog:execute-sql MCP tool near the first example, since the tool is only mentioned once early in the prose.

Dimension	Reasoning	Score
Conciseness	Tight and technical with no basic-concept padding, but the Gotchas section restates the mandatory filters, dedup pattern, and JSON-dot-access caveats already covered above, leaving minor redundancy that could be trimmed.	4 / 5
Actionability	Five complete, copy-paste-ready HogQL examples plus column and metadata-field reference tables give fully executable guidance covering the common query cases.	5 / 5
Workflow Clarity	A clear typical-pattern sequence (inbox-exploration then this skill), explicit MUSTs for filters and dedup, and a Gotchas checklist provide most checkpoints; read-only queries do not require a validate-fix-retry loop.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (table reference, mandatory filters, dedup, metadata, examples, gotchas) with no bundle files to reference; structure is good though all reference content is inlined in a single ~316-line file.	4 / 5
	Total	17 / 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.

A strong, specific description that clearly answers both what the skill does and when to use it, with explicit boundary guidance against a sibling skill. Trigger phrasing is natural and concrete, with only minor room for additional synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — query document_embeddings via HogQL, semantic search over signals, fetch all signals for a report, list signal types — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states what the skill does (query the table for raw signal data via HogQL) and when to use it with concrete triggers, plus boundary guidance on when to prefer inbox-exploration.	5 / 5
Trigger Term Quality	Natural trigger phrases ('semantic search over signals', 'fetch every signal that contributed to a specific report', 'list signal types') are present, but synonym/variation coverage is limited rather than exhaustive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (raw signal layer via HogQL) and explicitly distinguishes itself from the sibling inbox-exploration skill, minimizing wrong-skill triggering.	5 / 5
	Total	19 / 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: products/signals/skills/signals/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.