CtrlK
BlogDocsLog inGet started
Tessl Logo

running-ci-preflight

Catch the deterministic CI failures reachable from your diff before pushing, with `hogli ci:preflight`. Use when the pre-push hook blocks a push, before reporting a task done, or after editing Python, serializers, migrations, workflows, or dependency manifests — to avoid burning a CI matrix on a failure you could catch locally (formatting, lint, broken lockfiles, OpenAPI drift, migration conflict, stale branch). Trigger terms: ci:preflight, preflight, pre-push checks, pre-push hook failed, "will this break CI".

77

Quality

97%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.md body with a clear validate-and-retry loop, concrete executable commands, and well-organized inline sections. The only minor weakness is a few rationale passages that slightly over-explain.

Suggestions

Trim the explanatory rationale in the staleness and type-check Notes bullets to the operational facts, keeping the mechanism details only where they change the action.

Consider moving the long env-tunable threshold detail (5 commits / 2 days, HOGLI_PREFLIGHT_STALE_*) into a short reference list format to reduce prose density.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence with dense, token-efficient operational detail, but a few rationale passages (e.g. the staleness risk-modeling explanation and type-check cost justification) are over-explanation that could be trimmed slightly.

4 / 5

Actionability

Fully executable: gives the exact command 'hogli ci:preflight --fix', per-symbol resolution steps ('openapi advisory → run hogli build:openapi and commit the drift'), named env vars with thresholds, and concrete commands for each skipped-capability case.

5 / 5

Workflow Clarity

The numbered loop is clearly sequenced with an explicit validation/recovery feedback checkpoint ('Re-run until clean, then push') and distinguishes blocking fails from non-blocking advisories, so the multi-step process is unambiguous.

5 / 5

Progressive Disclosure

No bundle files exist; the single self-contained file is organized into clearly signaled sections (The loop, Notes, Why it matters) with all content appropriately inline and easy to navigate — fitting the simple/well-organized-skill case.

5 / 5

Total

19

/

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.

A strong, specific description with concrete actions, comprehensive natural trigger terms, and an explicit what-and-when structure. It is well-distinguished from the sibling ci:insights skill and unlikely to trigger for the wrong skill.

DimensionReasoningScore

Specificity

Names concrete actions ('Catch the deterministic CI failures reachable from your diff') and enumerates concrete failure classes (formatting, lint, broken lockfiles, OpenAPI drift, migration conflict, stale branch), giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what ('Catch the deterministic CI failures...with hogli ci:preflight') and when ('Use when the pre-push hook blocks a push, before reporting a task done, or after editing Python, serializers, migrations, workflows, or dependency manifests') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger terms users would say — 'ci:preflight, preflight, pre-push checks, pre-push hook failed, "will this break CI"' — including synonyms and the natural phrasing 'before reporting a task done'.

5 / 5

Distinctiveness Conflict Risk

Carves a clear pre-push niche and explicitly distinguishes itself from the related skill ('the pre-push counterpart to hogli ci:insights'), with distinct trigger terms and minimal overlap 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.

Validation — 16 / 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.