CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

exploring-scouts

How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, and assessing a scout's health and performance over time (cadence, success rate, report rate, signal-to-noise). Read-only and exploratory — to write or tune a scout, use `authoring-scouts` instead. Trigger on "what are my scouts doing", "how is my <x> scout performing", "show me recent scout runs", "why did this scout find/report nothing", "what has the fleet learned", "explore scout run <id>", "is my scout working".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./products/signals/skills/exploring-scouts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 well-sequenced workflows, but it is padded with repeated caveats and inlines reference-grade detail that should live in the missing bundle files it points to.

Suggestions

De-duplicate the emitted_count/last_run_at caveats: state each once in its workflow and reference it from the Tips section instead of re-explaining each time.

Move the scratchpad prefix table and the full metadata/failure-mode field enumeration into the existing references/scout-data-model.md and references/assessing-performance.md files so the body stays a lean overview.

Add the referenced bundle files (references/ and scripts/ directories) so the signaled one-level-deep navigation actually resolves.

DimensionReasoningScore

Conciseness

Noticeably verbose: several caveats are repeated across the body (the emitted_count/emitted_finding_ids legacy explanation at lines 30, 151, 186-188, 358-359; the last_run_at dispatch-stamp caveat at 97-102 and 366; 'Read the result against three cases' duplicated at 77-80), padding that could be tightened.

2 / 5

Actionability

Concrete MCP tool calls with arguments and executable script invocations with exact flags cover the common cases, but they are shown as pseudo-JSON blocks rather than directly runnable CLI commands, leaving minor gaps.

4 / 5

Workflow Clarity

Multiple named workflows are clearly sequenced with numbered steps and cross-check checkpoints ('Run this first', 'Cross-check them', three-case validation), though explicit error-recovery feedback loops are lighter than the top anchor.

4 / 5

Progressive Disclosure

Section structure and one-level-deep references (references/scout-data-model.md, references/assessing-performance.md, scripts/) are signaled, but those bundle files do not exist and large reference-grade content (scratchpad prefix table, full metadata enumeration, failure taxonomy) is inlined rather than split out.

3 / 5

Total

13

/

20

Passed

Description

100%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 excellent: it states concrete capabilities, provides a rich set of natural trigger phrases, answers both what and when explicitly, and clearly separates itself from adjacent write-side skills.

DimensionReasoningScore

Specificity

Lists many concrete actions — surveying the fleet and schedules, reading recent runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory, tracing a run to its reports, assessing health and performance — giving comprehensive concrete coverage rather than vague language.

5 / 5

Completeness

Clearly answers 'what' (explore and make sense of scouts across six observable things) and 'when' ('Use when a user wants to understand... Trigger on...'), both explicit and concrete.

5 / 5

Trigger Term Quality

Explicit natural trigger phrases in quotes ('what are my scouts doing', 'how is my <x> scout performing', 'show me recent scout runs', 'why did this scout find/report nothing', 'what has the fleet learned', 'explore scout run <id>', 'is my scout working') match what a user would actually say, with variations.

5 / 5

Distinctiveness Conflict Risk

Carves a clear read-only exploration niche and explicitly distinguishes itself from sibling skills ('to write or tune a scout, use authoring-scouts instead'; counterpart to inbox-exploration), so conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 17 missing

Warning

Total

13

/

16

Passed

Repository

PostHog/posthog

Path

products/signals/skills/exploring-scouts/SKILL.md

Reviewed

Table of Contents

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.