CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

90

1.42x
Quality

Does it follow best practices?

Impact

98%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 lean, highly actionable API reference — dense tables, executable code, a host-selection decision guide, and clean one-level-deep navigation to detail pages. It respects the token budget while remaining copy-paste ready.

DimensionReasoningScore

Conciseness

Dense, table-driven reference with no padding or explanation of concepts Claude already knows; the two lead blockquotes are slightly verbose but earn their place as agent-routing guidance, so every token adds value.

3 / 3

Actionability

Two complete executable Python examples with real imports and calls, plus concrete URLs, auth formats, install commands, and a host-selection decision table — copy-paste ready.

3 / 3

Workflow Clarity

For a reference skill the Host Selection Guide table makes the single action (pick host → make call) unambiguous and well-organized, with no destructive or batch operations requiring validation checkpoints.

3 / 3

Progressive Disclosure

The body is a concise overview that points to clearly signaled one-level-deep detail pages (inference, rest-api, api-key-management) at the bottom, with no nested-reference chains; no bundle directories are present to verify.

3 / 3

Total

12

/

12

Passed

Description

72%

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 distinctive with good natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 2. Adding a when-to-use phrase would round it out.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when you need Roboflow API URL patterns, auth formats, error codes, or SDK quick-start snippets.'

Reframe the content list with action verbs (e.g. 'Look up URL patterns, authenticate requests, interpret error codes, and call the SDK') to strengthen the specificity of capabilities.

DimensionReasoningScore

Specificity

Lists concrete content items ('URL patterns, auth, parameters, error codes, and SDK quick-start') but the framing is noun-based facts rather than action verbs, so it names the domain and specifics without comprehensive concrete actions.

2 / 3

Completeness

Clearly states what the skill contains, but there is no 'Use when...' trigger clause; the second sentence is a cross-reference to roboflow-inference rather than explicit when-to-use guidance, capping completeness at 2.

2 / 3

Trigger Term Quality

Strong coverage of natural terms users would say — 'Roboflow REST and Inference APIs', 'auth', 'error codes', 'SDK quick-start' — matching the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Roboflow API-reference niche and explicitly defers deployment strategy and Workflow execution to roboflow-inference, making conflicts unlikely.

3 / 3

Total

10

/

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
roboflow/computer-vision-skills
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.