Skip to content
Skills Library
AI & agents · Building & coding

gemini-api

/gemini-api

Plan, implement, or review gemini api work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests gemini api work.

Licence
Apache-2.0
Last repository change
26.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Plan, implement, or review gemini api work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests gemini api work.

Original author description

Plan, implement, or review gemini api work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests gemini api work.

How it works

  1. Workflow
  2. Quality gates
  3. SandBase boundary
  4. Handoff
Original SKILL.md headings · 40 lines, 411 words
SKILL.md preview
---
name: gemini-api
description: "Plan, implement, or review gemini api work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests gemini api work."
---

# Gemini API

Use this Skill to produce a bounded, verifiable Gemini API outcome. Preserve the user's chosen stack, source material, and authorization boundaries.

Read [the SandBase API map](references/sandbase-api-map.md) only when the task genuinely needs an external data source or generative model.

## Workflow

1. Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change.
2. Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result.
3. Produce the smallest complete implementation, analysis, or artifact that satisfies those checks.
4. Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone.
5. Return the deliverable, evidence of validation, material assumptions, and unresolved limitations.

## Quality gates

- Inspect repository instructions, current versions, tests, and user changes before proposing an implementation.
- Make the smallest compatible change, preserve public contracts unless change is requested, and avoid new dependencies without a concrete benefit.
- Run focused tests plus the relevant build or static checks, then report observed results and any unverified paths.
- For ordinary Gemini-family inference, discover and inspect a current SandBase candidate. Use direct Vertex AI or Google Cloud administration only when the user explicitly requests it and supplies an authorized environment.

## SandBase boundary

Keep the core Gemini API work local. Use SandBase only for current external documentation, repository evidence, or explicitly requested model inference.

1. Call `sandbase_discover` with a short capability query.
2. Call `sandbase_inspect` for viable candidates and compare the live schema, coverage, limits, output, execution mode, and price.
3. Prefer a dedicated tool or API the user already has. Send only the minimum necessary data.
4. Before any paid call, show the endpoint, important arguments, current unit price, call count, and total estimate or uncertainty, then obtain confirmation.
5. Use `sandbase_account` before an approved multi-call batch and call `sandbase_run` only with current schema-defined arguments.
6. Poll asynchronous work with `sandbase_run_get` using the same run ID; never resubmit merely because it is pending.
7. Use `sandbase_runs` only to recover status or reconcile observed cost.

If SandBase is unavailable, continue with local work and authorized sources when possible. Do not silently switch providers, fabricate external results, or claim a generation or retrieval succeeded.

## Handoff

Provide the completed artifact or findings, concise reproduction steps, checks actually run, source or asset provenance, SandBase endpoint and run IDs when used, observed cost when available, and any follow-up that still requires user action.
Files in this package (2)
  • SKILL.md 3 KB
  • references/sandbase-api-map.md 1 KB

Versions

RepositoryScoreLicence
This page · sandbaseai/sandbase-skills90Apache-2.0
google/skills100Apache-2.0
hamzabellouch/agent-skills100MIT
AkshatNaruka/aidentity100MIT
jmxt3/gitscape.ai100Apache-2.0

Database snapshot: 13.11.2026 · package version fab2be74116b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90mcp-cli
    Plan, implement, or review mcp cli work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests mcp cli work.
  • 90ml-pipeline
    Plan, implement, or review ml pipeline work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests ml pipeline work.
  • 100gemini
    Use when the user asks to run Gemini CLI (gemini, gemini resume) or references Google Gemini for code analysis, refactoring, or automated editing

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.