CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-hog-validation-criteria

The validation criteria for PostHog Review, the bar for deciding whether a flagged PR issue is worth keeping. Keeps real, user-affecting correctness / security / data-loss / contract / performance problems; drops overengineering, speculation, paranoia, never-gonna-happen edge cases, and style.

64

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./products/review_hog/skills/review-hog-validation-criteria/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, actionable decision framework with concrete examples, a clearly sequenced workflow, and well-organized self-contained sections. It assumes Claude's competence and avoids padding.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — it names SSRF, IDOR, unsafe deserialization and path traversal without explaining them — with only minor framing in the opening paragraphs that could be trimmed.

4 / 5

Actionability

Provides concrete decision criteria with worked examples ('if `items` is empty this raises `IndexError`', 'this query runs once per row -> N+1 on the dashboard'), an explicit skepticism test ('If you can't name both, be skeptical'), and named output fields (is_valid, argumentation, category) — fully actionable for a judgment skill.

5 / 5

Workflow Clarity

A clear 5-step sequence with an explicit reachability-validation step (step 2: trace call sites, types, validation) and a tie-break rule (step 4: on the fence -> drop); no retry loop is present, but the verdict task does not require one and is not destructive or batch.

4 / 5

Progressive Disclosure

Self-contained and well-organized into three clear sections (Keep, Drop, How to decide) with no need for external references or file splitting, satisfying the well-organized-sections exception for skills that need no bundle files.

5 / 5

Total

18

/

20

Passed

Description

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

The description is specific and well-scoped to a clear niche, with strong concrete categorization of what to keep versus drop. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when triaging flagged PR issues from PostHog Review to decide which to surface to the author.'

Surface the natural phrases a user would say when invoking this (e.g. 'is this PR finding worth keeping', 'should I drop this review issue') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete keep/drop categories (correctness, security, data-loss, contract, performance vs overengineering, speculation, paranoia, edge cases, style), giving comprehensive coverage of the decision space, though the core action is a single keep/drop verdict rather than several distinct actions.

4 / 5

Completeness

Clearly states what it does ('the bar for deciding whether a flagged PR issue is worth keeping') but provides no explicit 'Use when...' trigger clause, so 'when' is only weakly implied and completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Uses natural review-domain terms engineers actually say ('flagged PR issue', 'correctness', 'security', 'data loss', 'overengineering', 'speculation'), with only minor synonym variations missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a distinct niche (PostHog Review issue triage) with specific triggers, with only minor overlap risk against general code-review / security-review skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PostHog/posthog

Path

products/review_hog/skills/review-hog-validation-criteria/SKILL.md

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.