CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gemini-api-dev

Use this skill when writing code that calls the Gemini API for text generation, multi-turn chat, multimodal understanding, image generation, video generation, speech generation (TTS), voice design, voice replication, streaming responses, background research tasks, function calling, structured output, or migrating from the old generateContent API. Covers SDK usage and best practices for Gemini models and agents in Python and TypeScript.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, current, highly actionable API skill with executable dual-language examples and disciplined pointer-based delegation to hosted docs and references/migration.md. Its main weaknesses are inlined reference material (Data Model tables, full docs catalog) and version-specific migration detail that duplicates the migration reference, plus the absence of explicit in-body validation checkpoints.

Suggestions

Collapse the model-migration bullets (Omni 1.2, Nano Banana 2.1, TTS) to one-line pointers to references/migration.md instead of inlining version-specific durations, caps, and reference-media rules in SKILL.md.

Move the Data Model section (step types, content types, delta types, status values) into a references/ file such as references/data-model.md, keeping only a brief summary inline.

State the primary workflow as a short numbered sequence (fetch matching doc page → pick a current model → write code → verify parameters against the fetched page) so the process and its verification step are explicit.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic-concept explanations) and keeps examples minimal, but the ~90-word Omni 1.2 migration bullet detailing durations and reference-media rules and other version-specific migration notes duplicate detail that lives in references/migration.md, and the 65-line Documentation Pages catalog is inlined verbatim. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Fully executable, copy-paste-ready Python and TypeScript examples cover the common cases (quick start, stateful chat via previous_interaction_id, deep-research polling with failed/completed handling, managed and custom agents, streaming) using current model strings and current SDK versions. This matches the top anchor: specific examples cover the common cases.

5 / 5

Workflow Clarity

The primary workflow is explicit and unambiguous ('Before writing any code, you MUST fetch the relevant documentation page from the list below') and the polling examples include status checkpoints, but the body itself has no numbered sequence or explicit validation steps for its multi-feature workflows — migration scope confirmation is delegated to references/migration.md. This sits between 'clear sequence with most checkpoints' (4) and the explicit validation/checklist level (5).

4 / 5

Progressive Disclosure

Good structure with well-labeled sections, a real one-level-deep bundle file (references/migration.md) clearly signaled multiple times, and an organized hosted-docs catalog for navigation. However, the ~50-line Data Model section (step types, delta types, status values) and the full link directory are inlined in SKILL.md rather than split into reference files, which is a minor organization gap rather than fully 'appropriately split' content.

4 / 5

Total

17

/

20

Passed

Description

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

An excellent description that explicitly states both what the skill covers and when to use it, with comprehensive, natural trigger terms including synonyms and the legacy API name. The only weakness is minor overlap risk with closely related Gemini skills due to broad terms like 'streaming responses'.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — 'text generation, multi-turn chat, multimodal understanding, image generation, video generation, speech generation (TTS), voice design, voice replication, streaming responses, background research tasks, function calling, structured output, or migrating from the old generateContent API' — comprehensive coverage matching the top anchor, not merely 'several specific actions'.

5 / 5

Completeness

It explicitly answers both questions: 'Use this skill when writing code that calls the Gemini API for...' (explicit when with concrete trigger phrases) and 'Covers SDK usage and best practices for Gemini models and agents in Python and TypeScript' (clear what). This matches the anchor requiring both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are comprehensively covered: 'Gemini API', 'text generation', 'multi-turn chat', 'image generation', 'streaming', 'function calling', 'structured output', 'TTS' (paired with its synonym 'speech generation'), and 'generateContent' for migration requests. This matches 'comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

'Gemini API' with an enumerated capability list carves a clear niche, but broad triggers like 'streaming responses' and general Gemini model/agent coverage create minor overlap risk with closely related skills (e.g., a Gemini Live API skill). This fits 'mostly distinct; minor overlap risk' better than 'minimal conflict risk'.

4 / 5

Total

19

/

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

boranfurkan/discordlancer

Path

.claude/skills/gemini-api-dev/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.