ci

A specialized skill for Gemini CLI that provides high-performance, fail-fast monitoring of GitHub Actions workflows and automated local verification of CI failures. It handles run discovery automatically—simply provide the branch name.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/ci/SKILL.md

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 highly actionable with concrete executable commands and a well-structured, appropriately split overview. The main gaps are minor: a duplicate '### 1.' heading numbering and slight redundancy between capability and workflow sections.

Suggestions

Fix the duplicate heading numbering so the two workflows are '### 1' and '### 2' (or use distinct titles) to remove the sequencing ambiguity.

Express the default 'replicate' workflow as a numbered step sequence with an explicit validation checkpoint rather than only a behavior description.

Trim the overlap between 'Core Capabilities' and the 'Workflow' section to tighten the token budget further.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of GitHub Actions, npm, and gh; minor redundancy between 'Core Capabilities' and the 'Workflow' sections and repeated 'automatically' phrasing keep it just short of fully efficient.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across common cases ('node .gemini/skills/ci/scripts/ci.mjs [branch]', 'npm test -w <pkg> -- <path>', 'npm run lint:all', 'gh run view --job <job_id> --log').	5 / 5
Workflow Clarity	The status workflow has a clear numbered Step 1-3 sequence with a 'confirm the failure' checkpoint, but the default replicate workflow is described as behavior rather than sequenced steps and both workflows are numbered '### 1.', introducing minor sequencing gaps.	4 / 5
Progressive Disclosure	Well-organized sections with a single clearly-signaled one-level-deep reference to scripts/ci.mjs (which exists in the bundle), appropriate split of guidance in SKILL.md and logic in the script.	5 / 5
	Total	18 / 20 Passed

Description

70%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 distinct, naming concrete capabilities and a clear niche for GitHub Actions CI monitoring. Its main weakness is the absence of an explicit 'when to use' clause, which limits completeness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user pushes changes and needs to monitor GitHub Actions or reproduce CI failures locally').

Include common natural trigger terms like 'build', 'pipeline', or 'CI run' alongside 'workflows' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('monitoring of GitHub Actions workflows', 'automated local verification of CI failures', 'run discovery automatically'), placing it at the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	Has a clear 'what' (monitoring, local verification, auto run discovery) but no explicit 'Use when...' or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms present ('GitHub Actions', 'workflows', 'CI', 'branch name') that users would say, but common variations like 'build', 'pipeline', or 'CI run' are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (GitHub Actions CI monitoring and local replication) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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: google-gemini/gemini-cli
Path: .gemini/skills/ci/SKILL.md
Commit: 85aca16

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.