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".

76

Quality

95%

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

90%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 tight, highly actionable skill body that gives executable commands, a clear fallback chain, and the PostHog-specific semantics needed to interpret results. It loses only minor points for lacking an explicit verification checkpoint and for keeping all detail inline in one file.

Suggestions

Add an explicit verification checkpoint after the fast path (e.g. 'If owners is empty, confirm via owners:unowned or the handbook before reporting unowned') to close the workflow-clarity gap.

Consider splitting the Resolution algorithm section into a short reference file and keeping SKILL.md as an overview, which would let progressive_disclosure reach 5.

DimensionReasoningScore

Conciseness

Lean and dense: it assumes Claude's competence and explains only PostHog-specific semantics (the resolver, file formats, slug vs handle) — every section earns its place with no generic padding about what ownership or code ownership means.

5 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — 'hogli owners:who', 'hogli owners:resolve --json', the 'git ls-files | hogli owners:resolve --json | jq ...' pipeline, and a dependency-light PYTHONPATH fallback — covering the common cases concretely.

5 / 5

Workflow Clarity

A clear escalation sequence is present (hogli fast path -> pyyaml fallback -> feature-ownership handbook -> Slack) plus generated-file source tracing, but there is no explicit verify-the-result checkpoint; since the operations are read-only the destructive-cap does not apply, keeping this just below 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Fast path, Resolution algorithm, team->code, Generated files, Last resort, Slug vs handle) with no external references needed, but the ~58-line body keeps the resolution-algorithm detail inline in a single self-contained file rather than demonstrating a split overview-to-detail structure.

4 / 5

Total

18

/

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 excellent description: it states concrete capabilities in third person, names the exact mechanism, and gives an explicit 'Use when' clause with natural trigger phrases and synonyms. It is distinguishable from any generic code-search skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Determine which PostHog team owns a file, directory, or code path' and 'enumerate all code a team owns' — and names the exact mechanism (owners.yaml, products/*/product.yaml, .github/CODEOWNERS), giving comprehensive coverage of both lookup directions.

5 / 5

Completeness

Explicitly answers both 'what' (determine/enumerate ownership via the named files) and 'when' via a concrete 'Use when ...' clause enumerating real trigger scenarios, matching the anchor's two-part requirement.

5 / 5

Trigger Term Quality

Includes natural user phrases such as 'who owns X' / 'what does team Y own', 'assigning a reviewer', 'attributing a bug or slow query', 'routing work', and 'scoping a team-wide audit' — the exact wording a user would say, with synonym coverage.

5 / 5

Distinctiveness Conflict Risk

A clear PostHog-specific niche resolved through named internal files, with distinctive triggers ('who owns X') that would not fire for unrelated skills, yielding minimal conflict risk.

5 / 5

Total

20

/

20

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.