Name: signals-scout-health-checks
Rating: 66.4 (1 reviews)
Author: PostHog

signals-scout-health-checks

Signals scout over PostHog's own health checks. Reads the project's active health issues, bundles them by kind, weights by blast radius, and files the ones genuinely worth acting on as reports in the inbox.

Quality

81%

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

88%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 high-quality, deeply actionable scouting playbook with concrete tooling, real query examples, and a well-sequenced workflow backed by validation checkpoints and feedback loops. Its only weaknesses are mild repetition of the core doctrine and a referenced report-contract.md that is not present in this skill's bundle.

Suggestions

Consolidate the "bundle by root cause, not one report per issue" doctrine into one authoritative statement and reference it, rather than restating it across four sections.

Either include references/report-contract.md in the skill's bundle (references/) or make clear it lives in the parent authoring-scouts skill, so the progressive-disclosure pointer resolves within reach.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence throughout (no basic-concept padding) and stays high-signal, but the core discriminator ("bundle by root cause, not one report per issue") is restated across the intro, Explore, Decide, and Disqualifiers sections, which could be tightened.	4 / 5
Actionability	Fully executable: names specific tools with parameters (health-issues-list status=active dismissed=false), a copy-paste HogQL query for SDK-version share, concrete scratchpad key schemas (dedupe:health:<issue_id>), and exact priority/actionability mappings — covering the common cases.	5 / 5
Workflow Clarity	Clear sequence (Get oriented → Profile shape → Explore → Save memory → Decide → Close out) with explicit validation checkpoints (confirm $pageview collapse, confirm non-trivial traffic before web-instrumentation warnings, check inbox before authoring) and feedback loops (edit-vs-author dedupe, scratchpad-instead-of-report when in doubt).	5 / 5
Progressive Disclosure	Well-sectioned body with a clearly signaled one-level-deep pointer to references/report-contract.md for the generic contract, but no bundle files (references/scripts/assets) exist in this skill, so the reference target cannot be verified and the body is fairly dense rather than split.	4 / 5
	Total	18 / 20 Passed

Description

75%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 sharp, third-person description that names several concrete actions and carves out a distinct niche, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Adding a natural trigger clause would raise it.

Suggestions

Add an explicit "Use when..." clause naming the natural trigger situations (e.g. reviewing PostHog setup health, triaging active health issues, surfacing inbox-worthy findings).

Include a couple of synonyms or user-phrased variants ("setup health", "health check findings") alongside "health checks" to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Reads the project's active health issues, bundles them by kind, weights by blast radius, and files the ones...as reports in the inbox" — covering the workflow comprehensively within its niche, matching the multiple-specific-actions anchor.	5 / 5
Completeness	The "what" is explicit (reads, bundles, weights, files reports) but there is no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3 — clear what, missing when.	3 / 5
Trigger Term Quality	Carries domain-natural terms ("health checks", "health issues", "blast radius", "reports in the inbox") a user would say in a PostHog context, but lacks synonyms or variations, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (PostHog health-checks scouting) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: PostHog/posthog
Path: products/signals/skills/signals-scout-health-checks/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.