CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-expensive-users

Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.

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

Low

Low-risk findings worth noting

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 high-quality, executable skill: lean prose, copy-paste SQL, a clearly sequenced workflow with comparison baselines and a causal decision tree, and well-organized sections with a one-level reference pointer.

DimensionReasoningScore

Conciseness

Lean and instruction-dense: assumes Claude's competence, skips general LLM/cost concepts, and lets executable SQL blocks carry the guidance rather than prose padding.

3 / 3

Actionability

Provides fully executable SQL queries with exact field names and a copy-paste-ready trace-reading JSON call, plus a concrete decision tree for interpreting results.

3 / 3

Workflow Clarity

Six numbered, clearly sequenced steps with explicit checkpoints (bounded time range, identified-user filter, baseline comparison, read traces before claiming causality) and decision-tree feedback for ambiguous aggregates.

3 / 3

Progressive Disclosure

No bundle files are present, but the body is well-organized into overview + Tools + Core rules + numbered Workflow + response shape; the one inline reference to exploring-llm-costs/references/cache-accounting.md is a single-level, clearly signaled external skill pointer.

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 strong, third-person description that names concrete capabilities, natural trigger terms, and an explicit Use-when clause. It carves out a clear niche distinct from related cost/trace skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions from the body's framing — rank users by cost and explain the drivers via volume, model choice, prompt/output size, cache behavior, retries, trace type, and custom dimensions.

3 / 3

Completeness

Clearly answers what (analyze the most expensive users and explain why they cost so much) and when via the explicit 'Use when the user asks about...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Uses natural phrasing a user would actually say ('top spenders', 'expensive users', 'per-user LLM cost', 'user-level cost drivers') with good coverage of variations for high spend.

3 / 3

Distinctiveness Conflict Risk

Niche is clear (per-user AI observability cost analysis) and triggers are distinct from general cost or trace skills; the body explicitly cross-references the adjacent skills, lowering conflict risk.

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.