CtrlK
BlogDocsLog inGet started
Tessl Logo

signals-scout-conversations

Signals scout for PostHog Conversations (support inbox). Watches `$conversation_*` ticket- lifecycle events for SLA breach steps, first-response latency blowouts, backlog imbalance, and channel or assignment concentration.

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./products/signals/skills/signals-scout-conversations/SKILL.md
SKILL.md
Quality
Evals
Security

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 strong, highly actionable analytics-scout skill: executable SQL, explicit validation guards, a clear sequenced workflow, and a sharp signal-vs-noise framing. The only gap is structural — all content lives in one inlined file with no progressive disclosure via references.

DimensionReasoningScore

Conciseness

Mostly efficient and information-dense, with prose that earns its place by capturing genuinely non-obvious signal-vs-noise reasoning (e.g. why anchor on message_received, why net re-adds reopened); only minor framing flourishes ("You are a focused Conversations scout.") could be trimmed.

4 / 5

Actionability

Three complete, copy-paste-ready SQL blocks, a precise events-and-properties table, concrete tool calls, and exact scratchpad key patterns cover the common cases fully and execute as written.

5 / 5

Workflow Clarity

A clearly sequenced run (orient → profile → explore → save memory → decide → close out) with explicit validation guards — minimum-volume guard, same-weekday baseline, corroborate-before-report, rule-out-capture-gap — plus a disqualifiers checklist and a "When to stop" termination section.

5 / 5

Progressive Disclosure

Well-organized with clear ## / ### section headers enabling easy navigation, but it is a single monolithic ~220-line file with no one-level-deep references, so it stops short of the cleanly split, reference-signaled anchor 5.

4 / 5

Total

18

/

20

Passed

Description

70%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 specific, well-scoped, third-person description of a Conversations support-inbox signals scout, but it omits any explicit "Use when…" trigger guidance, which caps its completeness. Adding a trigger clause naming the natural user phrases would lift the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. "Use when reviewing PostHog Conversations support-inbox health, SLA attainment, first-response latency, backlog, or channel/assignment concentration," to satisfy the 'when' half of completeness.

Soften the most jargon-y phrases ("latency blowouts", "assignment concentration") toward language users actually say, and add synonyms (e.g. "first-response time", "routing") to broaden trigger-term coverage.

Vary the verb beyond the single "Watches" to surface the distinct actions (detect, flag, report) for a more comprehensive specificity anchor.

DimensionReasoningScore

Specificity

Names the domain (PostHog Conversations support inbox) and several concrete detection targets — "SLA breach steps, first-response latency blowouts, backlog imbalance, and channel or assignment concentration" — but all are framed under a single repeated "Watches" verb rather than varied actions, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

The description gives a clear "what" but no "when"/"Use when…" trigger clause, which per the judging guidelines caps completeness at 3 even though the capability statement itself is specific.

3 / 5

Trigger Term Quality

Good coverage of natural terms a user would say ("support inbox", "SLA breach", "first-response", "backlog") plus the `$conversation_*` event family, though some phrasing ("latency blowouts", "assignment concentration") leans technical and no file extensions or synonyms round it out.

4 / 5

Distinctiveness Conflict Risk

A clear, narrow niche — operational health of the PostHog Conversations support inbox — with triggers that are unlikely to fire for sibling scouts (emission pipeline, error-tracking, logs), giving minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.