CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roboflow-inference

Interactive image/video previews, deployment option comparison (serverless, dedicated, self-hosted, batch), Workflow publishing, device management and Vision Events. For raw API URL patterns, auth, and request/response formats, see roboflow-api-reference.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./chatgpt/skills/roboflow-inference/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is a well-structured, highly actionable overview: exact tool and command tables, a decision matrix for deployment options, and clearly sequenced authoring and batch workflows with validation checkpoints. Detail is consistently deferred one level deep to named reference files, with only minor conciseness padding, slightly inlined batch CLI tables, and implicit rather than explicit error-recovery loops keeping it from top marks.

DimensionReasoningScore

Conciseness

The body is dense and operational — tables of exact MCP tools, CLI subcommands, and decision guidance that assumes Claude's competence — with only minor trimmable padding such as the "similar to the extensibility benefits of a microservice over a point-to-point call" analogy and the "What it is" prose that restates the deployment table row. It is not 5 because those few over-explanations exist, and not 3 because nearly every section carries non-redundant actionable guidance.

4 / 5

Actionability

Concrete, executable guidance throughout: a copy-paste-ready end-to-end batch CLI block ("inference rf-cloud data-staging create-batch-of-images --images-dir ./my-images --batch-id my-batch"), exact MCP tool names with parameters ("Run the published Workflow by workflow_id (URL slug) ... Optional parameters"), and specific commands like "pip install inference-cli && inference server start". The examples cover the common cases (preview, run, author, batch) with no significant gaps, so it exceeds the "minor gaps" level of 4.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with validation checkpoints: the authoring path ("workflows_list, then workflows_get ... Validate with workflow_specs_validate before saving with workflows_create or workflows_update, then run") and the 5-step batch flow ending in "Monitor — poll job status or register a webhook". It is not 5 because error-recovery feedback loops are only implied via table entries (restart-job, abort-job) rather than woven into the flows as explicit fix-and-retry steps.

4 / 5

Progressive Disclosure

References are one level deep and well signaled with section anchors ([workflows](./workflows.md#preview-images-and-videos), [devices](./devices.md), [batch-staging](batch-staging.md) "for nuances"), keeping the body an overview. It is not 5 because two full CLI command tables are inlined in the batch section rather than deferred, and link styles are inconsistent (relative ./paths, skill:// URIs, ../ cross-skill paths); also, no bundle files are present in this review directory to verify the referenced files exist.

4 / 5

Total

17

/

20

Passed

Description

71%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 comprehensive about capabilities and clearly delineates its boundary with the sibling API-reference skill, but it omits any explicit "when to use this" trigger guidance and lacks core natural keywords like "inference" and "deploy". These gaps leave trigger-based routing under-specified despite a strong capability listing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to run or preview a Roboflow model or Workflow on images/videos, compare deployment options, publish Workflows, or manage devices and Vision Events."

Include the natural keywords users would actually say — "inference", "run a model", "deploy", "Roboflow" — to improve trigger-term coverage and distinctiveness.

State the platform (Roboflow) explicitly in the description text so generic phrases like "deployment option comparison" cannot collide with non-Roboflow skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "Interactive image/video previews, deployment option comparison (serverless, dedicated, self-hosted, batch), Workflow publishing, device management and Vision Events" — that comprehensively map onto the skill body's sections. It is not 4 because there are no gaps in coverage; each named capability is a specific, concrete function.

5 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance; the second sentence ("For raw API URL patterns, auth, and request/response formats, see roboflow-api-reference") is a cross-reference to another skill, not usage timing. Per the rubric guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("previews", "serverless", "self-hosted", "batch", "Workflow publishing", "device management", "Vision Events"), but common user phrasings like "inference", "run a model", "deploy", and "streaming" are absent. It is not 5 because synonym/variation coverage is incomplete, and not 3 because coverage goes well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

Domain-specific terms ("Vision Events", "Workflow publishing", the four enumerated deployment options) and an explicit boundary against roboflow-api-reference make it mostly distinct with minor overlap risk. It is not 5 because fairly generic phrases like "deployment option comparison" and "device management" could overlap with other deployment or device-management skills.

4 / 5

Total

16

/

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: 10 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository

roboflow/computer-vision-skills

Path

chatgpt/skills/roboflow-inference/SKILL.md

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.