CtrlK
BlogDocsLog inGet started
Tessl Logo

using-the-console-ui

How to drive PostHog Desktop's read panel as the user works with you — focus_* etiquette, when to call toast, how to handle 'follow mode' being off. Load when the session client kind is `posthog-code`.

68

Quality

83%

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

92%Weight 40%Scale 1-3

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 single-file skill with clear sequenced workflows and error handling; its main weakness is repeated references to a 'secrets-and-integrations' playbook that is not present in the bundle.

Suggestions

Either add the referenced 'secrets-and-integrations' file to references/ and link it explicitly, or inline the minimal needed loop and drop the dangling reference.

The opening line restates the frontmatter description almost verbatim — consider trimming it to avoid redundancy with the description field.

DimensionReasoningScore

Conciseness

Dense and instructional throughout — tool tables, concrete arg shapes, and return envelopes with no concept-explanation filler; assumes Claude's competence, so nearly every token earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance: exact tool args ('{ slug: "<agent>", path: "skills/research.md" }'), return envelopes, and fully-qualified URL patterns with query params.

3 / 3

Workflow Clarity

Clear numbered sequence (announce → focus → call → report) with explicit branching on the focus result ('focused:true' vs 'focused:false' reasons) and an error-recovery path for client_tool_unsupported.

3 / 3

Progressive Disclosure

Sections are well-organized, but 'secrets-and-integrations' is referenced three times as a playbook while no references/ bundle directory exists, leaving that navigation ambiguous and unsignaled as a real file.

2 / 3

Total

11

/

12

Passed

Description

75%Weight 40%Scale 1-3

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 specific, well-scoped description that clearly answers what and when, but its trigger guidance is technical rather than natural-user-language, and second-person phrasing costs it a specificity point.

Suggestions

Rewrite in third person ('Drives PostHog Desktop's read panel alongside the user') to avoid the second-person specificity penalty.

Add a natural-language trigger alongside the technical one (e.g. 'Use when the user wants to follow along in PostHog Desktop as you work').

DimensionReasoningScore

Specificity

Names multiple concrete actions ('focus_* etiquette, when to call toast, how to handle follow mode being off'), which would warrant a 3, but the second-person phrasing 'as the user works with you' triggers the rubric's one-point penalty.

2 / 3

Completeness

Explicitly answers both what ('drive PostHog Desktop's read panel... focus_* etiquette, when to call toast, how to handle follow mode being off') and when ('Load when the session client kind is posthog-code').

3 / 3

Trigger Term Quality

The load trigger is a technical condition ('Load when the session client kind is posthog-code') rather than natural user phrasing, though relevant domain keywords (focus, toast, follow mode, read panel) are present.

2 / 3

Distinctiveness Conflict Risk

Scoped tightly to PostHog Desktop's read panel with a single specific load condition, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.