CtrlK
BlogDocsLog inGet started
Tessl Logo

establishing-code-ownership

Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed `owners.yaml`, `products/*/product.yaml`, and `.github/CODEOWNERS`). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work, scoping a team-wide audit, or answering "who owns X" / "what does team Y own".

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.

An efficient, highly actionable skill body that leads with executable commands, sequences the resolution path and fallback hierarchy clearly, and stays self-contained and well-sectioned without padding. It assumes Claude's competence and adds only non-obvious domain semantics.

DimensionReasoningScore

Conciseness

Lean and dense — concrete commands and resolver semantics with no concept-padding Claude already knows; every line (e.g. the inherit:false / owners:null distinctions) earns its place.

3 / 3

Actionability

Fully executable, copy-paste-ready commands throughout — 'hogli owners:who', 'hogli owners:resolve --json', the jq pipeline, and the dependency-light PYTHONPATH fallback.

3 / 3

Workflow Clarity

Clear fast-path → resolution-algorithm → fallback escalation, with explicit flagging checkpoints ('flag the gap', 'flag as possibly stale', 'flag as Slack-sourced'); read-only lookup work needs no destructive-validation cap.

3 / 3

Progressive Disclosure

No bundle files exist; the self-contained SKILL.md is organized into clearly signaled sections with no nested external references, satisfying the well-organized single-file bar.

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 pairs concrete capabilities with an explicit, multi-trigger 'Use when' clause and a clear niche. It is concise without padding and uses natural terms a user would say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (resolve/enumerate ownership via the three named sources) and when via a clear 'Use when...' clause with multiple triggers.

3 / 3

Trigger Term Quality

Covers natural user phrasing — 'assigning a reviewer', 'attributing a bug or slow query to a team', 'routing work', 'scoping a team-wide audit', 'who owns X' / 'what does team Y own' — terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to PostHog code ownership with distinctive triggers; unlikely to fire for unrelated skills.

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.