CtrlK
BlogDocsLog inGet started
Tessl Logo

ov-github-actions-ci

Author, edit, debug, and review the OpenVINO GitHub Actions CI infrastructure — regular (non-agentic) workflows under .github/workflows, reusable job_*.yml workflows, custom composite actions under .github/actions, CI helper scripts under .github/scripts, Dockerfiles under .github/dockerfiles, and the Smart CI / labeler / components configuration. Use when a user wants to add or change a build/test job or step, create or modify a reusable workflow, write or fix a custom action, adjust runners/containers/caches, wire up Smart CI for a component, pin action versions, fix workflow permissions/security, or debug a failing CI workflow's YAML. Do NOT use for gh-aw agentic workflows (*.md with gh-aw frontmatter — use ov-agentic-workflows), for diagnosing a specific product/test failure's root cause in C++/Python code, or for non-CI GitHub configuration.

76

Quality

96%

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

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-architected checklist skill: actionable, with concrete snippets and commands, clearly sequenced workflows backed by validation and pitfall checklists, and disciplined progressive disclosure that links out rather than duplicating the authoritative docs. The only nit is that a few rationale/meta passages could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic GitHub Actions explanations — with every section carrying repo-specific knowledge; however at ~200 lines a few rationale passages (the 'Choosing the implementation environment' prose and the meta 'Skill self-improvement' section) could be tightened, landing just below the lean 'every token earns its place' anchor.

4 / 5

Actionability

Copy-paste-ready YAML ('uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2'), concrete env vars ('PIP_CACHE_PATH: /mount/caches/pip/linux'), explicit commands ('actionlint .github/workflows/<file>.yml'), and the pip-freeze pinning recipe make the guidance fully executable across common cases.

5 / 5

Workflow Clarity

Multi-step tasks are numbered ('Wire up Smart CI for a component', 'Add / edit a reusable workflow'), with an explicit 'Validation before finishing' checklist and a 'Pitfalls to check' error-recovery checklist providing the validation steps and feedback guidance the top anchor requires.

5 / 5

Progressive Disclosure

The body is an overview that defers detail to one-level-deep external docs, clearly signaled in a topic table and inline links, and is explicitly self-aware ('prefer linking to the doc over duplicating detail; this file is a short actionable checklist, not a second copy of the documentation').

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.

An exemplary description: highly specific, with natural trigger phrases, explicit use-when guidance, and clear boundary exclusions that distinguish it from sibling skills. The length is justified by the breadth of the CI domain rather than padding.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'Author, edit, debug, and review', 'add or change a build/test job or step', 'create or modify a reusable workflow', 'write or fix a custom action', 'pin action versions', 'fix workflow permissions/security' — giving comprehensive coverage of the CI surface, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers 'what' (the OpenVINO CI infrastructure and its components) and 'when' ('Use when a user wants to...'), with concrete trigger phrases and an explicit 'Do NOT use for...' exclusion list — clearly matching the anchor that requires both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Phrases a user would naturally say ('debug a failing CI workflow's YAML', 'pin action versions', 'adjust runners/containers/caches') plus synonyms and file patterns (job_*.yml, *.md, .github/workflows) give comprehensive coverage of natural terms.

5 / 5

Distinctiveness Conflict Risk

A sharply scoped niche (OpenVINO GitHub Actions CI) with an explicit boundary against the sibling ov-agentic-workflows skill and non-CI config gives a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

20

/

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

relative_links

Relative link issues: 17 suspicious

Warning

Total

15

/

16

Passed

Repository
openvinotoolkit/openvino
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.