CtrlK
BlogDocsLog inGet started
Tessl Logo

inbox-exploration

Explore PostHog's Inbox and act on what it surfaces — the place where signal reports cluster into actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by ID or title, wants to act on / fix / implement a report (turn it into a PR), wants to resolve, dismiss, or snooze a report, or wants to see which signal sources are configured. Covers listing, filtering, drilling into, and acting on reports, plus pointers to the deeper `signals` skill when raw signals or semantic search are needed.

76

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tool calls and well-sequenced workflows that include validation for destructive and batch operations. It is slightly token-heavy due to repeated enumeration of the write tools, the only thing keeping conciseness off the top anchor.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — no padding about what PostHog or errors are — but the exposed-writes list is repeated across the tools table, body prose, and Tips, and the overall length is token-heavy, placing it just below the 5 anchor.

4 / 5

Actionability

Concrete JSON tool calls with real arguments appear throughout (inbox-reports-list, retrieve, set-state, claim, bulk-set-state), copy-paste ready and covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Sequenced workflows (empty/unconfigured check, triage, drill, act, resolve) with explicit validation checkpoints — confirm with user before suppressing, inspect per-id outcomes on bulk calls, verify diagnosis against code before implementing — and feedback loops for destructive/batch operations, matching the 5 anchor.

5 / 5

Progressive Disclosure

Single self-contained SKILL.md with well-organized sections and one-level, clearly signaled hand-offs to the sibling signals skill and product-specific MCP tools; no bundle files exist, so the simple-skill exception applies cleanly.

5 / 5

Total

19

/

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 specific, trigger-rich, and complete, answering both what the skill does and when to use it with concrete user phrases. It carves a clear niche distinct from the related signals skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "listing, filtering, drilling into, and acting on reports", "resolve, dismiss, or snooze a report", "see which signal sources are configured" — with comprehensive coverage matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both what ("Explore PostHog's Inbox and act on what it surfaces") and when ("Use when the user asks…") with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say — "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?" — plus act/fix/dismiss/snooze intents and report-by-ID, matching the 5 anchor including synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear PostHog Inbox niche with distinct triggers and explicit hand-off to the sibling signals skill, keeping conflict risk minimal; third-person voice ("Explore", "Use when") incurs no penalty.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (557 lines); consider splitting into references/ and linking

Warning

Total

15

/

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.