CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gemini-3-pro-api

Gemini 3 Pro API/SDK integration for text generation, reasoning, and chat. Covers setup, authentication, thinking levels, streaming, and production deployment. Use when working with Gemini 3 Pro API, Python SDK, Node.js SDK, text generation, chat applications, or advanced reasoning tasks.

Quality

76%

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/gemini-3-pro-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers genuinely actionable, well-sequenced integration guidance for both SDKs, but it is significantly over budget: generic boilerplate and restatement sections pad roughly a third of the file, and the SDK package/module mismatch makes the flagship quick-start snippet non-executable as written. Progressive disclosure is undercut by a missing referenced file and production detail inlined rather than split into existing reference files.

Suggestions

Cut the 'Summary', 'Next Steps', 'When to Use This Skill', and streaming 'Benefits' sections, and move the RateLimiter class, logging configuration, and monitored_generate boilerplate into references/best-practices.md — Claude can write generic Python logging/retry code unaided; only Gemini-specific parameters and gotchas belong in SKILL.md.

Fix the SDK mismatch so the quick start is executable as written: either 'pip install google-generativeai' with 'import google.generativeai', or the current 'google-genai' package with 'from google import genai' (and the '@google/genai' JS package instead of the deprecated '@google/generative-ai').

Create references/thought-signatures.md (currently cited but missing), and add explicit executable validation checkpoints — e.g. assert response.text is non-empty and print usage_metadata — in place of the checklist-style 'Verify Success' step.

DimensionReasoningScore

Conciseness

The 613-line body contains several padded sections Claude does not need — a 'Summary' checklist restating the description, 'Next Steps', streaming 'Benefits', a 'When to Use This Skill' list duplicating the description — plus ~60 lines of generic boilerplate (a RateLimiter class, logging.basicConfig, monitored_generate) that any competent engineer already knows, matching 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Concrete, mostly copy-paste-ready code in both Python and Node.js across quick start, chat, streaming, and error handling. Not a 5 because the quick start fails as written: 'pip install google-genai' is paired with 'import google.generativeai' (and '@google/generative-ai' with the deprecated JS SDK), mixing package and module names so the snippet errors on first run.

4 / 5

Workflow Clarity

Three workflows present clear numbered sequences with goals and expected outcomes, plus a 'Verify Success' step in Workflow 1 and error-handling/retry steps in Workflows 2–3. Validation is shallow (checklist-style 'verify text output' rather than executable checks), so it fits 'clear sequence with most checkpoints present; minor validation gaps' rather than the explicit validate-fix-retry loops of a 5.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled in a References section, but 'references/thought-signatures.md' is cited in Workflow 2 and does not exist in the bundle (a broken link), and large production content (rate limiting, logging, cost-estimation code) is inlined in SKILL.md instead of living in references/best-practices.md — 'some structure but... content that should be separate is inline'.

3 / 5

Total

13

/

20

Passed

Description

88%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 clear third-person statements of what the skill covers and an explicit, concrete 'Use when...' trigger clause. Its only weaknesses are a few missing natural trigger synonyms and mild overlap risk from generic LLM-related trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning the full domain — 'text generation, reasoning, and chat', 'setup, authentication, thinking levels, streaming, and production deployment' — giving comprehensive coverage with no notable gaps, matching the top anchor rather than the 'minor gaps' of a 4.

5 / 5

Completeness

Explicitly answers both what it does ('API/SDK integration... Covers setup, authentication, thinking levels, streaming, and production deployment') and when to use it ('Use when working with Gemini 3 Pro API, Python SDK, Node.js SDK, text generation, chat applications, or advanced reasoning tasks'), mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

Triggers like 'Gemini 3 Pro API, Python SDK, Node.js SDK, text generation, chat applications' are natural user phrases, but common variations such as 'Gemini API', 'Google AI Studio', or the model ID 'gemini-3-pro-preview' are missing, matching the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Gemini 3 Pro specifically), but generic trigger phrases like 'text generation, chat applications, or advanced reasoning tasks' and 'Python SDK, Node.js SDK' create minor overlap risk with other LLM/Gemini skills, fitting 'mostly distinct; minor overlap risk' rather than minimal conflict.

4 / 5

Total

18

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

skills/gemini-3-pro-api/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.