Call Gemini 2 5 Pro Llm
v0.1.0AI agent for call gemini 2 5 pro llm tasks
⭐ 0· 947·4 current·4 all-time
by@urrrich
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (an agent wrapper for 'call_gemini_2_5_pro_llm') align with the provided instructions: role-playing a creative team member and producing task-focused outputs. There are no unexpected env vars, binaries, or installs requested.
Instruction Scope
The instructions demand the agent 'must' read attached meeting minutes as its sole memory source but do not define how those minutes are supplied (no file path, input name, or API). The primary language rules are internally contradictory: they require matching the user's initial challenge language, honor explicit user language, but also forbid inferring language from the meeting minutes or system prompt—this creates ambiguous or conflicting precedence. Template variables like $SHOW_NAME$ or $DATE$ are referenced but may be undefined at runtime. These ambiguities can lead to unpredictable or incorrect behavior.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing will be written to disk or downloaded during install.
Credentials
The skill requests no environment variables, credentials, or config paths. No disproportionate access is requested.
Persistence & Privilege
Defaults are used (not always:true). The skill does not request permanent presence or modify other skills. Autonomous invocation is allowed by platform default but is not combined with other concerning privileges here.
What to consider before installing
This skill appears low-risk from a credential/install perspective, but the SKILL.md has contradictory and vague runtime rules that can make the agent behave unpredictably. Before installing or using it: 1) Provide the 'meeting minutes' explicitly as part of the agent input (don't rely on implicit file delivery). 2) Define any template variables ($SHOW_NAME$, $DATE$, etc.) in the runtime context. 3) Test with explicit language instructions to ensure the language-selection behavior matches your expectations. 4) Be cautious if you rely on system-level prompts or safety controls—this skill's 'No Language Inference' rule could interact poorly with other prompts. If you need deterministic behavior, ask the skill author to clarify language precedence, the source of meeting minutes, and what template variables are required.Like a lobster shell, security has layers — review code before you run it.
latestvk97axvjdv41k5brfp37ejm9c31817z4e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.