Name: signals-scout-logs
Rating: 62.4 (1 reviews)
Author: PostHog

signals-scout-logs

Signals scout for PostHog logs. Watches for emerging and rate-shifted message patterns, volume bursts, severity-distribution shifts, service silence, and trace-correlated bursts.

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-logs/SKILL.md

Quality

Content

75%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 concrete MCP tool calls, explicit validation gates before writes, and well-structured sections. Its main weakness is verbosity from repeating the same firehose/sparkline/date-unit caveats across multiple sections.

Suggestions

Consolidate the repeated firehose-500, sparkline-ignore, and '-m = month' caveats into a single 'Footguns' callout and reference it once instead of restating each several times.

Consider moving the MCP tools reference list into a separate reference file so the run-workflow section stays lean.

Tighten the cyclical 'cycle between these moves' framing into a clearer ordered checklist for the core run loop.

Dimension	Reasoning	Score
Conciseness	The body is expert-level and free of concepts Claude already knows, but it repeats the same caveats several times (the sparkline-ignore warning, the firehose-500 warning, and the '-m = month' footgun each recur multiple times), so it could be tightened.	3 / 5
Actionability	Gives concrete, executable tool invocations with exact parameters (e.g. `logs-patterns-diff` with `query.dateRange`, `severityLevels=["fatal"]` over 24h) plus copy-ready scratchpad key formats like `pattern:logs:temporal-worker`, covering the common cases.	5 / 5
Workflow Clarity	A clear sequenced run (orient → explore → save memory → decide → close out) with explicit validation checkpoints (corroboration before writes, inbox dedupe search, `baseline.total_count` check) and checklists (Disqualifiers, When to stop); the deliberately cyclical 'cycle between these moves' framing keeps it just short of a crisp linear checklist.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references; the inline MCP-tools reference list could arguably live in a separate file, but placement is reasonable and navigation is easy.	4 / 5
	Total	16 / 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.

The description is specific and distinctive, listing a comprehensive set of log-anomaly capabilities in third person. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger situations (e.g. when the user asks about log volume, error spikes, or new message patterns in PostHog).

Soften jargon like 'rate-shifted message patterns' and 'trace-correlated bursts' with a few common synonyms users would actually say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete detection capabilities — "emerging and rate-shifted message patterns, volume bursts, severity-distribution shifts, service silence, and trace-correlated bursts" — covering the skill's scope comprehensively.	5 / 5
Completeness	The "what" is clearly stated (a signals scout that watches for these log patterns), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good coverage of natural domain terms ("PostHog logs", "volume bursts", "severity", "service silence", "patterns") a user would say, though it leans slightly jargon-heavy and omits a few common synonyms.	4 / 5
Distinctiveness Conflict Risk	"Signals scout for PostHog logs" carves a clear niche with distinct triggers (PostHog logs, signals scouting) and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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-logs/SKILL.md
Commit: b0fece0

Reviewed: 4 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.