CtrlK
BlogDocsLog inGet started
Tessl Logo

fireworks-ai-inference

Fast inference and fine-tuning platform with serverless and on-demand GPU deployments. OpenAI-compatible API for chat completions, embeddings, function calling, vision, and structured output. Supports SFT, DPO, and RL fine-tuning. SOC2 + HIPAA compliant.

56

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/cloud-compute/fireworks-ai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable, copy-paste-ready code across all features, but it is monolithic and somewhat redundant, with no external reference files and missing validation checkpoints for batch/destructive workflows.

Suggestions

Split the model catalog, pricing tables, and full API reference into a bundled REFERENCE.md and link to it from SKILL.md to improve progressive disclosure.

Remove the duplicated chat/streaming/embedding examples in the 'OpenAI Compatibility' section (already covered under 'Inference') and reduce it to a one-line drop-in note.

Add explicit validation checkpoints to batch inference and deployment-deletion workflows (e.g. verify batch status before relying on output; confirm deployment name before DELETE).

DimensionReasoningScore

Conciseness

Mostly efficient and concrete with no pedagogy, but there is notable redundancy — the 'OpenAI Compatibility' section repeats basic chat/streaming/embedding examples already shown under 'Inference', and the 'Quick Start' overlaps with later sections — so it could be tightened.

2 / 3

Actionability

Throughout the body, code is fully executable and copy-paste ready (e.g. the chat completion, function-calling, SFT job creation, deployment, and embedding snippets all include real endpoints, model IDs, and complete payloads).

3 / 3

Workflow Clarity

Processes are sequenced and labeled (fine-tuning create→monitor, deployment create→scale→delete), but batch and destructive operations (batch inference, deployment delete) lack explicit validation or verification checkpoints, which caps this at 2 per the guidelines.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is a single monolithic document; substantial reference material (model catalog, pricing tables, full API examples) is inline rather than split into one-level-deep referenced files, so structure is present but not appropriately offloaded.

2 / 3

Total

9

/

12

Passed

Description

67%

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 but omits any explicit 'when to use' trigger guidance, which caps completeness and weakens trigger-term quality.

Suggestions

Append a 'Use when ...' clause naming natural triggers (e.g. open-model inference, OpenAI SDK drop-in replacement, serverless/on-demand GPU, SFT/DPO/RL fine-tuning).

Add common user-facing terms alongside acronyms (e.g. 'supervised fine-tuning (SFT)' and 'Llama/Qwen/DeepSeek') to improve trigger-term quality.

Mention a concrete cost/latency trigger to distinguish from cheaper alternatives like Groq or self-hosted vLLM.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'serverless and on-demand GPU deployments', 'chat completions, embeddings, function calling, vision, and structured output', 'SFT, DPO, and RL fine-tuning' — matching the anchor for listing several specific actions.

3 / 3

Completeness

It thoroughly answers 'what does this do' but never states when Claude should use it; there is no 'Use when...' or equivalent explicit trigger clause, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

'inference', 'fine-tuning', 'chat completions', and 'embeddings' are natural terms, but acronyms like 'SFT, DPO, RL' are jargon-heavy and common variations users would say (e.g. 'open models', 'Llama/Qwen') are absent, so coverage is partial rather than full.

2 / 3

Distinctiveness Conflict Risk

The Fireworks-specific feature set (serverless/on-demand GPU, OpenAI-compatible API for open models, SFT/DPO/RL fine-tuning, SOC2/HIPAA) carves a clear niche unlikely to trigger for a wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (679 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
synthetic-sciences/openscience
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.