Name: roboflow-api-reference
Rating: 82 (1 reviews)
Author: roboflow

roboflow-api-reference

Protocol-level facts for Roboflow REST and Inference APIs — URL patterns, auth, parameters, error codes, and SDK quick-start. For deployment strategy and Workflow execution patterns, see roboflow-inference.

1.42x

Quality

73%

Does it follow best practices?

Impact

98%

1.42x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/api-reference/SKILL.md

Quality

Content

76%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 API reference with executable code and clear navigation to sibling pages, with only minor verbosity in the intro callouts and no multi-step workflow to sequence.

Suggestions

Tighten the two leading blockquote callouts; the MCP/Plugin guidance could be condensed without losing the key redirect instruction.

Since the description promises 'error codes', add a compact error-code table or link to where they are documented to close that gap.

Dimension	Reasoning	Score
Conciseness	Dense, table-driven reference content that assumes Claude's competence and avoids explaining concepts it already knows; the two leading blockquote callouts are slightly verbose but earn their place.	4 / 5
Actionability	Provides copy-paste-ready code for both the inference-sdk and roboflow SDK, concrete host URLs, exact auth formats, and a task-to-host selection table covering common cases.	5 / 5
Workflow Clarity	As a reference skill it has no multi-step process to sequence; content is well-organized into sections but lacks any explicit step sequence or validation checkpoints, so it sits at the midpoint.	3 / 5
Progressive Disclosure	SKILL.md functions as an overview with clear section headers and a Related Pages list pointing one level deep to sibling resources (inference, rest-api, api-key-management); minor gaps as some detailed tables are inlined rather than split out.	4 / 5
	Total	16 / 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 well-differentiated with concrete content areas and explicit boundary guidance, but it lacks an affirmative 'Use when...' trigger clause, leaving the activation condition only weakly implied.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases users would say (e.g. 'Use when calling Roboflow REST or Inference APIs, handling auth/API keys, or debugging API errors').

Surface 'API key' and 'endpoints' as natural trigger terms alongside the existing keywords.

Dimension	Reasoning	Score
Specificity	Lists several concrete content areas — 'URL patterns, auth, parameters, error codes, and SDK quick-start' — giving specific coverage with only minor gaps (e.g. pagination/headers not enumerated).	4 / 5
Completeness	The 'what' is clear (protocol-level facts enumerated), but there is no explicit 'Use when...' trigger clause; the only guidance is a negative redirection to roboflow-inference, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Roboflow REST and Inference APIs', 'auth', 'SDK quick-start') with good coverage; a few common variants like 'API key' or 'endpoints' are implicit rather than named.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Roboflow API protocol reference) and explicitly disambiguates from the sibling roboflow-inference skill, minimizing conflict risk.	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: roboflow/computer-vision-skills
Path: skills/api-reference/SKILL.md
Commit: f3b2cbd

Reviewed: 10 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.