CtrlK
BlogDocsLog inGet started
Tessl Logo

finding-experiments

Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a relative reference ("latest", "most recent", "the one I created yesterday"), filters by status (running, draft, paused, exposure frozen, stopped, archived), or otherwise refers to an experiment by anything other than its concrete ID.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured guide: it specifies the tool and fields, sequences the workflow with disambiguation and a destructive-action checkpoint, and stays concise with clean sectioning. It is a strong example of a simple, single-purpose skill.

DimensionReasoningScore

Conciseness

Lean and focused throughout with no padding or explanation of concepts Claude already knows; every section (tool guidance, matching fields, disambiguation, examples, guardrails) earns its tokens.

3 / 3

Actionability

Names the exact tool (`experiment-list`), enumerates the specific fields to scan (name, status, feature_flag_key, recency), and prescribes the follow-up `experiment-get` call — concrete and copy-ready despite being instruction-only.

3 / 3

Workflow Clarity

Clear sequence from search to match handling with explicit one/multiple/no-match branches and a validation checkpoint ("Confirm with the user by name before destructive actions") plus a "When NOT to search" guardrail.

3 / 3

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no need for external references; it is well-organized into clearly signaled sections, qualifying for the top anchor under the simple-skills note.

3 / 3

Total

12

/

12

Passed

Description

100%

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 exemplary: concrete actions, third-person voice, an explicit and detailed "Use when" trigger clause, and a clear negative boundary against feature-flag tools. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — resolving natural-language references to concrete experiment IDs, browsing `experiment-list`, and disambiguating multiple matches — all in third-person voice, matching the top anchor.

3 / 3

Completeness

Explicitly answers both what (resolve references to experiment IDs) and when via a detailed "Use when..." clause enumerating named, loose, relative, and status-filtered references, satisfying the top anchor.

3 / 3

Trigger Term Quality

Rich coverage of natural user phrasing including quoted examples ("split test demo", "the signup experiment", "my pricing test") plus relative references ("latest", "most recent") and status filters, matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Clear experiment-resolution niche with an explicit carve-out ("not feature-flag tools") and distinct triggers, making misfires for other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.