CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

72

Quality

91%

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

88%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 written routing/orchestration skill that sequences ship-vs-update paths with explicit validation gates and lean, command-oriented guidance. Progressive-disclosure design is strong but the referenced files are missing from the bundle, and the deepest execution steps are delegated rather than inline.

Suggestions

Bundle the referenced files (references/widget-intake.md, checklist-new-widget-type.md, architecture.md, etc.) so the well-designed one-level-deep navigation is actually resolvable.

Inline a minimal executable sketch of the §2 ship execute steps (beyond test commands) so the skill is more self-sufficient before delegating to the checklist.

Add a short validate→fix→retry loop note in §6 Verify so the error-recovery feedback loop is explicit rather than implied by the referenced checklist.

DimensionReasoningScore

Conciseness

Lean and link/command-driven throughout — routing table, invariant list, and copy-paste test commands with no padding about what a widget or dashboard is; every line earns its place and Claude's competence is assumed.

5 / 5

Actionability

Provides concrete executable commands (e.g. `hogli test products/dashboards/backend/api/test/test_run_widgets.py`, `hogli build:openapi`) and specific file routing, but the core build execution lives in referenced checklists rather than inline, leaving minor gaps versus fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

Clear sequencing (Intake 4 steps → spec confirmation → checklist §1→§8) with explicit validation gates — "§5b sequenced once MVP tests are green" and "Ship gate (required before the PR)" — plus a referenced checklist for the complex ship path; matches the explicit-checkpoint anchor.

5 / 5

Progressive Disclosure

Excellent one-level-deep structure with a dedicated Reference appendix table and well-signaled inline links with section anchors, but the referenced bundle files (references/*.md) are not present in the skill bundle, so the navigation is not actually resolvable — a structure gap that keeps it below the top anchor.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A precise, third-person description that clearly states both what the skill does and when to use it, with concrete trigger identifiers and explicit out-of-scope boundaries. Slightly code-symbol heavy on triggers, which keeps trigger-term quality just short of the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "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 of the platform work surface; not below because no major capability is unnamed.

5 / 5

Completeness

Explicitly answers what ("Guides PostHog engineers through dashboard widget platform work") and when ("Use for WidgetSpec, widget_specs/… or WidgetCard composition") with concrete trigger phrases, plus intake and negative-boundary notes; clearly matches the both-answered-with-concrete-triggers anchor.

5 / 5

Trigger Term Quality

Strong concrete triggers (widget_type, WidgetSpec, widget_specs/, widget-configs.zod.ts, hogli build:openapi, WidgetCard) but they skew toward code identifiers and file paths rather than the natural-language synonyms a user would voice, so it sits just below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

Narrow PostHog dashboard-widget niche with an explicit "Not for MCP batch-add of existing types or adding tiles to a dashboard" boundary, minimizing overlap with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 33 missing, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 33 missing

Warning

Total

14

/

16

Passed

Repository

PostHog/posthog

Path

.agents/skills/manage-dashboard-widgets/SKILL.md

Revision

130f3a1

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill