CtrlK
BlogDocsLog inGet started
Tessl Logo

review-hog-blind-spots-general

The general blind-spot check for PostHog Review, the final sweep that runs after every enabled review perspective has reviewed a chunk. Hunts for real, high-value issues that ALL of the perspectives missed, conditioned on what they actually found; returns an empty list over padding.

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./products/review_hog/skills/review-hog-blind-spots-general/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 content is a concise, well-structured instruction skill that gives Claude a clear, actionable hunting procedure and an explicit good-outcome (empty list when nothing was missed). Tightening the output-format specification and adding an explicit novelty-verification checkpoint would push it to full marks.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no concept padding or restating of what Claude already knows; directives like 'hunt where they did not look instead of re-walking their ground' make every token earn its place.

5 / 5

Actionability

As an instruction-only skill, code absence is not penalized, and the guidance is concrete ('Study the covered findings first', 'Dig into... untested edge cases, error and failure paths, unhandled inputs, cross-file interactions', 'return an empty issues list'); the only minor gap is that the exact output format/schema is implied rather than specified.

4 / 5

Workflow Clarity

There is a clear sequence (study covered findings -> dig into untouched ground -> report only new issues or return empty), and this is a read-only analysis task so the destructive/batch validation cap does not apply; the only minor gap is the absence of an explicit verification step that reported issues are truly novel.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is well-organized with clear headers ('How to hunt', 'What to report'), meeting the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

46%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 clearly conveys a distinctive, well-scoped role and a couple of concrete behaviors, but it leans on internal jargon and omits an explicit 'Use when...' trigger clause. Adding natural trigger terms and a when-to-use clause would lift the weaker dimensions.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when running the final review sweep over a PR chunk after the specialist perspectives have reported.'

Swap some internal jargon ('chunk', 'review perspective') for natural phrasings a user would say, and add synonyms like 'missed issues', 'review gaps', or 'second-pass review'.

Optionally enumerate the concrete capabilities (e.g. 'finds missed issues, deduplicates against prior findings, returns an empty list when nothing was missed') to broaden specificity.

DimensionReasoningScore

Specificity

Names the domain ('blind-spot check for PostHog Review') and two concrete actions ('Hunts for real, high-value issues that ALL of the perspectives missed' and 'returns an empty list over padding'), but does not enumerate a comprehensive set of distinct capabilities, matching the 'domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

The 'what' is clear (a final sweep that hunts issues all perspectives missed), but there is no 'Use when...' or equivalent explicit 'when' guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'blind-spot check', 'final sweep', 'review perspective', and 'chunk' are internal PostHog jargon rather than natural phrases a user would say; only 'blind-spot check' approaches a natural keyword, leaving common variations and synonyms absent.

2 / 5

Distinctiveness Conflict Risk

It carves a specific niche ('the final sweep that runs after every enabled review perspective has reviewed a chunk') with minimal conflict risk, though it lives within a review suite where minor overlap with related review perspectives remains.

4 / 5

Total

12

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

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.