CtrlK
BlogDocsLog inGet started
Tessl Logo

manage-dashboard-widgets

Guides PostHog engineers through dashboard widget platform work — ship a new widget_type (WIDGET_REGISTRY, catalog, run_widgets, WidgetCard) or update a shipped type (config, query, layout, RBAC, tile filter bar, list footer, titleHref, throttles). Use for WidgetSpec, widget_specs/, widget-configs.zod.ts, hogli build:openapi, error_tracking_list, session_replay_list, widgetFilters, formatWidgetListCountFooter, widget_query_throttle, or WidgetCard composition. New types need widget-intake confirmation first. Not for MCP batch-add of existing types or adding tiles to a dashboard.

79

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%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 tightly structured, highly actionable skill body that routes by request type, sequences work with explicit validation gates, and pushes detail into verified one-level reference files. It rewards Claude's intelligence while staying executable.

DimensionReasoningScore

Conciseness

Telegraphic, dense prose that assumes Claude's competence — routing tables, file paths, and section anchors instead of explanatory padding; no concept explanations and every line carries actionable signal.

5 / 5

Actionability

Provides copy-paste-ready commands ('hogli test products/dashboards/backend/api/test/test_run_widgets.py', 'hogli build:openapi'), exact file/symbol targets, and a concrete §1→§8 checklist sequence covering the common ship and update cases.

5 / 5

Workflow Clarity

Sequenced intake steps (1–4) with an explicit 'spec confirmation before checklist §1' checkpoint, plus a separated 'MVP smoke (not a ship point)' vs 'Ship gate (required before the PR)' validation tier with feedback into §5b ordering.

5 / 5

Progressive Disclosure

Clear overview with one-level-deep references to real files in references/ (all 13 linked docs exist), well-signaled inline and consolidated in a navigable 'Reference appendix' table; no nested/deep chaining.

5 / 5

Total

20

/

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.

An exceptionally specific, third-person description that pairs concrete capabilities with explicit trigger terms and a clear negative scope boundary. It tells Claude exactly when to activate and when not to.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across two paths — 'ship a new widget_type (WIDGET_REGISTRY, catalog, run_widgets, WidgetCard)' and 'update a shipped type (config, query, layout, RBAC, tile filter bar, list footer, titleHref, throttles)' — giving comprehensive coverage rather than generic verbs.

5 / 5

Completeness

Explicitly answers both 'what' (ship or update a widget_type) and 'when' ('Use for ...'), plus an explicit negative boundary ('Not for MCP batch-add ... or adding tiles to a dashboard') and a precondition ('New types need widget-intake confirmation first').

5 / 5

Trigger Term Quality

Densely packed natural trigger terms for the target audience — 'WidgetSpec, widget_specs/, widget-configs.zod.ts, hogli build:openapi, error_tracking_list, session_replay_list, widgetFilters, formatWidgetListCountFooter, widget_query_throttle, WidgetCard composition' — covering file paths, symbols, and commands an engineer would actually name.

5 / 5

Distinctiveness Conflict Risk

A narrow, repo-specific niche (PostHog dashboard widget platform) with concrete distinguishing triggers and an explicit 'Not for' clause, minimizing overlap with neighboring skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

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.