CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roboflow-plans-and-pricing

Use when answering questions about Roboflow plans, credit usage, or cost estimation; fetches current official pricing and credit rates and fills a fixed response template.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent instructional content: concrete URLs, commands, verbatim fallback wording, and explicit validation/error-recovery paths for a fetch-and-render workflow, with details properly split into a template asset and a renderer script. Only minor conciseness trimming (slight repetition of the no-stale-values rule) keeps it from a perfect profile.

DimensionReasoningScore

Conciseness

The body is lean and operational, assuming Claude's competence (no explanation of what Roboflow or credits are), e.g. "An empty cell is not zero or free." Minor trimming is possible: the no-stale-data rule is repeated across "Never guess at prices", "Do not use this file, remembered values, previous answers, or search snippets as pricing evidence", and "Do not substitute old values". Fits the 4 anchor (efficient with minor over-explanation) better than 5, where every token would earn its place.

4 / 5

Actionability

Fully executable guidance: exact URLs to fetch, a runnable command ("python3 scripts/render_pricing.py /absolute/path/to/current-pricing.json"), verbatim fallback strings to emit on failure, and per-placeholder fill specifications (plan_rows, extra_credits, checked_at, etc.). Copy-paste ready and covers the common cases; not a 4 since there are no gaps in the concrete instructions.

5 / 5

Workflow Clarity

A clear sequence (fetch both pages, verify each field type, read/retrieve the template, fill placeholders or run the renderer, return the rendered text) with explicit validation and error-recovery paths: the fetch-failure fallback wording, source-conflict handling ("explain the discrepancy and do not calculate a definitive total"), and exclusion of unverified rates. Checkpoints are explicit, matching the top anchor.

5 / 5

Progressive Disclosure

The body is a concise overview, with the fixed wording split into assets/pricing-template.md and the deterministic substitution into scripts/render_pricing.py — both real files, one level deep, clearly linked with their purpose stated. No nesting, no buried references, easy navigation; the top anchor fits.

5 / 5

Total

19

/

20

Passed

Description

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

A strong description with an explicit 'Use when' trigger clause, concrete natural keywords, and a clearly distinct Roboflow-pricing niche. Its only weakness is moderate action coverage — it names two behaviors rather than a fuller inventory of what the skill does.

DimensionReasoningScore

Specificity

Names the domain ("Roboflow plans, credit usage, or cost estimation") and two concrete actions ("fetches current official pricing and credit rates and fills a fixed response template"), matching the anchor for domain plus 1-2 concrete actions. Not a 4 because only two actions are listed and coverage of the skill's behavior (e.g., rendering, cost breakdowns) is not comprehensive.

3 / 5

Completeness

Explicitly answers both: an explicit trigger clause ("Use when answering questions about Roboflow plans, credit usage, or cost estimation") and a clear what ("fetches current official pricing and credit rates and fills a fixed response template") with concrete trigger phrases. Clearly matches the top anchor rather than 4, where the 'when' would be less specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "plans", "credit usage", "cost estimation", "pricing" — phrased as things a user would actually say. Not a 5 because common variations like "billing", "how much does X cost", or "subscription" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Roboflow pricing and credits) with distinct, vendor-specific triggers; minimal overlap risk with any other skill. Anchor 5 is the best fit — no neighboring anchor describes it better.

5 / 5

Total

17

/

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-plans-and-pricing/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.