CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging-ci-failures

Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (aggregated cross-run CI intelligence), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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 well-structured, highly actionable CI-triage skill body with dense classification/repro tables, explicit safety gates, and clean navigation. The only minor weakness is light repetition of the 'start with insights' directive.

Suggestions

Collapse the repeated 'start with hogli ci:insights' guidance between the intro and section 1 into a single statement to tighten conciseness from 4 to 5.

Consider moving the full signal→class classification table into a references file if the skill grows, keeping only the most common rows inline for progressive disclosure.

DimensionReasoningScore

Conciseness

Lean, high-signal tables and commands with no padding about basic CI/GitHub-Actions concepts; the only slack is mild restatement of the 'start with hogli ci:insights' directive across the intro and section 1, which keeps it just below the lean-and-efficient anchor 5.

4 / 5

Actionability

Fully executable guidance — concrete `hogli ci:insights`/`gh run view` commands, a signal→class→first-action classification table, a class→exact-repro-command table, and a copy-paste report template covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced workflow (insights → find failing run → classify → reproduce → report) with explicit checkpoints and stop conditions — 'Stop at the first failing step', confirm against master history, fallback when the insights backend is unavailable, and approval-gated safety rules before any irreversible action.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep external pointers (hogli SKILL.md, hogli --help, the fixing-flaky-tests skill) rather than nested bundle references; no monolithic inline reference material that belongs in separate files.

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 high-quality description that is specific, trigger-rich, complete on both what and when, and clearly scoped to a distinct niche. Third-person voice is used correctly throughout with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Debugs failing GitHub Actions CI runs', 'answers broad CI-health questions', 'read-only inspection', 'failure classification', 'smallest local reproduction', 'safe reporting' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (debug/classify/reproduce/report CI failures) and 'when' via a concrete 'Use when the user asks why CI is red...' clause with multiple trigger conditions.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say — 'is CI red?', 'is master green today?', 'what's broken right now?', plus failing check, GitHub Actions run, Depot runner, workflow, job, shard, flaky test, lint/typecheck failure, snapshot diff, migration check, generated types drift, skills build failure.

5 / 5

Distinctiveness Conflict Risk

A clearly delineated PostHog-CI-debugging niche with specific triggers and an explicit handoff boundary to the separate fixing-flaky-tests skill, minimizing 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.