CtrlK
BlogDocsLog inGet started
Tessl Logo

formatting-insight-axes

Pick the right y-axis unit when creating or updating a TrendsQuery insight via `posthog:insight-create` or `posthog:insight-update`. Use when the agent is about to add a `formula` purely to convert units (e.g. dividing seconds by 60 to display minutes), when a `math_property` is a duration, currency, ratio, or large count, or whenever the user mentions "format the y-axis", "duration", "seconds", "minutes", "hours", "milliseconds", "ms", "percentage", "currency", "decimals", "axis label", or "axis unit" in the context of a graph insight.

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.

A tight, highly actionable skill body: an anti-pattern callout, a complete format-value table, concrete JSON examples for every case, and sharp decision guidance including currency and seconds edge cases. It scores at the top on conciseness, actionability, workflow clarity, and organization.

DimensionReasoningScore

Conciseness

Lean and purpose-built — no PostHog primer or basic-concept padding — where every section (anti-pattern, format table, currency gotcha, seconds default) adds non-obvious, load-bearing guidance; above the score-2 case that retains unnecessary explanation.

3 / 3

Actionability

Provides copy-paste-ready JSON examples for each format plus exact field names and a value table, fully executable rather than the pseudocode/abstract guidance at score 2 or 1.

3 / 3

Workflow Clarity

The decision flow is unambiguous — anti-pattern to avoid, format table to pick from, currency nuance, and a silent 'default to duration' rule with explicit confirm-only-when-pinned guidance — plus a clear update sequence; as a single-task skill this meets the top anchor without needing separate validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist, so there is nothing to verify; the body is organized into clearly labeled, one-level sections with no nested references and short, load-bearing examples kept appropriately inline rather than split out, matching the well-organized top anchor.

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.

A precise, third-person description that pairs a concrete capability with an explicit, trigger-rich 'Use when' clause and a distinct, low-conflict niche. It hits the top anchor on all four dimensions with no verbosity or over-claiming.

DimensionReasoningScore

Specificity

Names concrete actions ('Pick the right y-axis unit') bound to specific tools ('via `posthog:insight-create` or `posthog:insight-update`'), matching the 'multiple specific concrete actions' anchor rather than the partial score-2 example.

3 / 3

Completeness

Explicitly answers both what (pick the right y-axis unit for a TrendsQuery insight) and when (an explicit 'Use when...' clause listing multiple triggers), matching the top anchor; not score 2 because the 'when' is stated, not merely implied.

3 / 3

Trigger Term Quality

Covers a broad set of natural terms users would say — 'format the y-axis', 'duration', 'seconds', 'minutes', 'hours', 'milliseconds', 'ms', 'percentage', 'currency', 'decimals', 'axis label', 'axis unit' — with no common variations missing.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — TrendsQuery y-axis formatting — with distinct, specific triggers unlikely to fire for unrelated skills, so it is well above the score-2 'could overlap' case.

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.