Claude Code Plugins

Community-maintained marketplace

Feedback

gemini-extensions

@majiayu000/claude-skill-registry
2
0

Use Gemini Extensions to connect models to Google services and external tools.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name gemini-extensions
description Use Gemini Extensions to connect models to Google services and external tools.
allowed-tools Read, Write, Edit, Bash, Glob, Grep, Task, TodoWrite
model sonnet
x-version 3.2.0
x-category platforms
x-vcl-compliance v3.1.1
x-cognitive-frames HON, MOR, COM, CLS, EVD, ASP, SPC

Purpose

Plan and execute Gemini Extension calls with consent, scoping, and auditability.

Trigger Conditions

  • Use this skill when: Need Gemini to interact with Drive, Gmail, Calendar, or third-party tools via extensions.
  • Reroute when: If doing pure text/chat without tools, standard Gemini usage suffices.

Guardrails (Inherited from Skill-Forge + Prompt-Architect)

  • Structure-first: every platform skill keeps SKILL.md, examples/, and tests/ populated; create resources/ and references/ as needed. Log any missing artifact and fill a placeholder before proceeding.
  • Confidence ceilings are mandatory in outputs: inference/report 0.70, research 0.85, observation/definition 0.95. State as Confidence: X.XX (ceiling: TYPE Y.YY).
  • English-only user-facing text; keep VCL markers internal. Do not leak internal notation.
  • Adversarial validation is required before sign-off: boundary, failure, and COV checks with notes.
  • MCP tagging for runs: WHO=gemini-extensions-{session}, WHY=skill-execution, namespace skills/platforms/gemini-extensions/{project}.

Execution Framework

  1. Intent & Constraints — clarify task goal, inputs, success criteria, and risk limits; extract hard/soft/inferred constraints explicitly.
  2. Plan & Docs — outline steps, needed examples/tests, and data contracts; confirm platform-specific policies.
  3. Build & Optimize — apply platform playbook below; keep iterative checkpoints and diffs.
  4. Validate — run adversarial tests, measure KPIs, and record evidence with ceilings.
  5. Deliver & Hand off — summarize decisions, artifacts, and next actions; capture learnings for reuse.

Platform Playbook

  • Workflow patterns:
    • Map user intent to required extensions and scopes
    • Design consent + audit prompts before execution
    • Validate outputs and redact sensitive data before returning
  • Anti-patterns to avoid: Requesting broad scopes unnecessarily, Skipping consent before tool execution, Returning raw extension payloads without filtering
  • Example executions:
    • Draft emails via Gmail Extension with explicit approval
    • Summarize Drive docs using Drive + Vertex search combo

Documentation & Artifacts

  • SKILL.md (this file) is canonical; keep quick-reference notes in README.md if present.
  • examples/ should hold runnable or narrative examples; tests/ should include validation steps or checklists.
  • resources/ stores helper scripts/templates; references/ stores background links or research.
  • Update metadata.json version if behavior meaningfully changes.

Verification Checklist

  • Trigger matched and reroute considered
  • Examples/tests present or stubbed with TODOs
  • Constraints captured and confidence ceiling stated
  • Validation evidence captured (boundary, failure, COV)
  • MCP tags applied for this run

Confidence: 0.70 (ceiling: inference 0.70) - Standardized platform skill rewrite aligned with skill-forge + prompt-architect guardrails.