CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

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 ./skills/roboflow-api-reference/SKILL.md
SKILL.md
Quality
Evals
Security

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 an efficient, highly actionable overview: exact hosts and auth formats, executable SDK quick-starts for the common cases, and a task-to-host routing table. Structure and progressive disclosure are excellent, with details correctly deferred to clearly signaled one-level-deep reference files; only minor trims and the vague rate-limits line keep conciseness and workflow clarity just short of full marks.

DimensionReasoningScore

Conciseness

The body is dense fact tables (API hosts, auth methods, SDKs, host selection) with no explanations of concepts Claude already knows, but the provenance blockquote ("This skill is authored in roboflow/computer-vision-skills...") and justifications like "It handles auth, retries, and response parsing" are minor instances that could be trimmed.

4 / 5

Actionability

Two copy-paste-ready executable snippets (InferenceHTTPClient.infer and the roboflow SDK upload/predict flow) cover the common cases, alongside exact base URLs, auth formats ("?api_key=YOUR_KEY", "x-api-key: YOUR_KEY"), install commands, and a task-to-host lookup table.

5 / 5

Workflow Clarity

The Host Selection Guide plus the auth table give an unambiguous decision path from task to host to client, and the tricky WebRTC case is explicitly flagged ("Not a plain HTTP call"), but there is no error-recovery guidance and the rate-limits line ("rate limits vary by plan") leaves a minor validation gap.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep references: a "Related Pages" section lists inference.md, rest-api.md, and api-key-management.md with per-file descriptions, and the bulk detail (URL patterns, endpoints, error codes) is appropriately split into those files rather than inlined.

5 / 5

Total

18

/

20

Passed

Description

62%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 clearly differentiated, with a well-defined niche and an explicit boundary against the sibling roboflow-inference skill. Its main weaknesses are the absence of any "Use when..." trigger clause and missing natural task-level keywords, which leave the "when to use this" question unanswered and limit trigger-term quality.

Suggestions

Add an explicit trigger clause such as "Use when calling Roboflow REST or Inference APIs, uploading images, checking auth or error codes, or working with the inference SDKs".

Include natural user phrasings and synonyms (upload images, train a model, object detection, API key, model inference) so the description matches what users actually say.

Name the concrete actions the facts enable (e.g., CRUD projects, upload images, run inference, manage API keys) to lift specificity from topic-listing to comprehensive action coverage.

DimensionReasoningScore

Specificity

"URL patterns, auth, parameters, error codes, and SDK quick-start" lists several specific content areas, but they name topics rather than actions and omit upload/training/project CRUD, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The "what" is clear ("Protocol-level facts for Roboflow REST and Inference APIs — URL patterns, auth, parameters, error codes, and SDK quick-start"), but there is no "Use when..." clause or equivalent trigger guidance; the pointer to roboflow-inference marks a boundary without stating when this skill applies, capping the score at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like "Roboflow", "REST", "Inference APIs", "auth", and "SDK" are present, but natural task phrases a user would say ("upload images", "train a model", "object detection", "API key") are missing, so common variations and synonyms are not covered.

3 / 5

Distinctiveness Conflict Risk

"Protocol-level facts for Roboflow REST and Inference APIs" carves out a clear niche, and the explicit delegation "For deployment strategy and Workflow execution patterns, see roboflow-inference" disambiguates its closest sibling skill, minimizing conflict risk.

5 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

roboflow/computer-vision-skills

Path

skills/roboflow-api-reference/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.