CtrlK
BlogDocsLog inGet started
Tessl Logo

python-bootstrap

Install Python dependencies before running verification or test steps. Choose the correct path depending on whether the agent builds OpenVINO from source or not.

62

Quality

72%

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 ./.github/agents-prototype/skills/python-bootstrap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, highly actionable, and well-structured for a simple bootstrap skill; its only gap is the absence of an explicit post-install verification checkpoint before tests run.

Suggestions

Add a verification step after install, e.g. `python -c "import openvino; print(openvino.__version__)"` to confirm the bindings resolve before proceeding to verification/test steps.

Make the install-failure feedback loop explicit with a retry path for required deps (distinct from optional ones) rather than only "note and continue".

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — it never explains what OpenVINO or pip is, and the blockquote on release-wheel/source-build shadowing earns its place as a non-obvious gotcha rather than padding.

3 / 3

Actionability

Guidance is fully executable: concrete `pip install` commands with the correct `--extra-index-url`, a `PYTHONPATH` export, and a wheel-install line, all copy-paste ready.

3 / 3

Workflow Clarity

The two-path decision sequence is clear and there is an error-handling rule ("If a package install fails, note it ... and continue"), but there is no explicit verification checkpoint (e.g. `python -c "import openvino"`) before the verification/test steps the skill prepares for.

2 / 3

Progressive Disclosure

It is a self-contained, single-purpose skill with well-organized sections (Path A, Path B, General rules) and no need for external bundle references, which satisfies the simple-skill guideline for the top anchor.

3 / 3

Total

11

/

12

Passed

Description

57%

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 concrete and clearly scoped to an OpenVINO Python-bootstrap niche, but it lacks a dedicated "Use when..." trigger clause and lists only one main action, leaving its trigger and completeness below the top level.

Suggestions

Add an explicit trigger clause, e.g. "Use before running verification or test steps that need OpenVINO, or when an agent must install Python deps for an OpenVINO task."

Enumerate common trigger phrasings users/agents would say (e.g. "OpenVINO source build", "pip install openvino", "Python bindings for tests") to improve trigger-term coverage.

Surface the two concrete actions more visibly (install release-wheel deps vs. install source-build deps) so multiple specific capabilities read at a glance.

DimensionReasoningScore

Specificity

It names the OpenVINO/source-build domain and the concrete action "Install Python dependencies" with a branching decision ("Choose the correct path depending on whether the agent builds OpenVINO from source"), but it does not list multiple distinct concrete actions, so it stops short of the top anchor.

2 / 3

Completeness

The "what" is explicit (install Python dependencies), but the "when" is embedded in the action ("before running verification or test steps") rather than a dedicated explicit trigger clause, so completeness is capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

Relevant natural terms are present ("Python dependencies", "verification or test steps", "OpenVINO", "builds ... from source") but coverage is limited and there is no "Use when..." phrasing or common variation list.

2 / 3

Distinctiveness Conflict Risk

The OpenVINO-specific framing plus the distinctive source-build-vs-release-wheel two-path trigger give it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

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
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.