Name: gemini-api-integration
Rating: 63.2 (1 reviews)
Author: administrakt0r

gemini-api-integration

Use when integrating Google Gemini API into projects. Covers model selection, multimodal inputs, streaming, function calling, and production best practices.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/gemini-api-integration/SKILL.md

The canonical home for this skill is gemini-api-integration in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

71%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 highly actionable, well-sectioned integration guide with copy-paste code for every common Gemini use case. Its weaknesses are mild redundancy with the description, time-sensitive version pins outside a deprecation section, and a monolithic single-file structure that offloads nothing to reference files.

Suggestions

Move hard-coded model version strings (gemini-1.5-flash, gemini-2.0-pro) into a clearly labeled 'current models' or 'deprecated/old patterns' section so time-sensitive info is isolated and easy to update.

Trim the Overview and 'When to Use This Skill' sections so they do not restate the frontmatter description verbatim.

Extract the per-feature code examples and model-selection table into one-level-deep reference files (e.g. references/examples.md, references/models.md) and have SKILL.md serve as a concise overview with signaled links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with well-chosen code examples, but the Overview and 'When to Use' sections restate the description, and time-sensitive model version identifiers (gemini-1.5-flash, gemini-2.0-pro) appear outside any 'deprecated/old patterns' section, which the rubric penalizes.	3 / 5
Actionability	Fully executable, copy-paste-ready code across installation, text generation, streaming, multimodal input, function calling, multi-turn chat, and error handling — specific examples cover the common integration cases.	5 / 5
Workflow Clarity	A clear numbered sequence (1 Installation → 7 Model Selection) with supporting Best Practices and Troubleshooting sections; no explicit validation checkpoints, but the operations are non-destructive API calls so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and all seven code examples, the model table, error handling, and troubleshooting are inlined into a single ~180-line SKILL.md rather than offloaded to one-level-deep reference files, fitting the 'content that should be separate is inline' anchor despite good section headers.	3 / 5
	Total	15 / 20 Passed

Description

78%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, third-person description with an explicit 'Use when...' trigger and a concrete list of covered capabilities. It is distinct and unlikely to misfire, with only minor gaps in synonym coverage and trigger specificity keeping it just below ceiling.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — 'model selection, multimodal inputs, streaming, function calling, and production best practices' — but 'production best practices' is somewhat generic, leaving minor coverage gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ('Covers model selection, multimodal inputs, streaming, function calling...') and when ('Use when integrating Google Gemini API into projects'); the 'when' trigger is present and clear but single-scenario rather than the rich multi-trigger phrasing of anchor 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('integrating Google Gemini API', 'streaming', 'function calling', 'multimodal inputs') with good coverage, but misses common synonyms such as 'Google AI', 'Gemini Pro/Flash', or SDK package names.	4 / 5
Distinctiveness Conflict Risk	'Integrating Google Gemini API' carves a clear provider-specific niche with distinct triggers and minimal overlap risk against general LLM-integration skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/gemini-api-integration/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.