CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gemini-3-advanced

Advanced Gemini 3 Pro features including function calling, built-in tools (Google Search, Code Execution, File Search, URL Context), structured outputs, thought signatures, context caching, batch processing, and framework integration. Use when implementing tools, function calling, structured JSON output, context caching, batch API, LangChain, Vercel AI, or production features.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gemini-3-advanced/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured and highly actionable, with runnable examples for every task and a complete, verified bundle of reference files and scripts. Its weaknesses are redundant overview/summary sections that inflate token cost, and the absence of validation or error-recovery checkpoints in the batch-processing workflow, which the rubric caps at 3 for workflow clarity.

Suggestions

Remove the redundant 'Key Capabilities', 'When to Use This Skill', and closing 'Summary' checklist sections — they restate the description and add ~40 lines of tokens with no new information (conciseness).

Add validation/verification steps to the batch-processing and function-calling loops, e.g., checking each response for errors/finish_reason before proceeding and retrying or logging failed items (workflow_clarity).

Slim the inlined per-task code in SKILL.md to one minimal example each and defer full listings to the existing references/ and scripts/ files, which already cover the same ground (progressive_disclosure, conciseness).

DimensionReasoningScore

Conciseness

The body contains noticeable redundancy: 'Key Capabilities' and 'When to Use This Skill' restate the frontmatter description, the Quick Start function-calling example overlaps Task 1's example, and the closing 'Summary' checklist plus 'Ready for advanced features?' add no new information — more than the minor trimming of the level-4 anchor, though most code content is dense and useful.

3 / 5

Actionability

Most guidance is executable copy-paste code covering each task (Pydantic/Zod structured output, CachedContent.create, LangChain/Vercel integration), but there are minor gaps: 'execute_function(fc)' in Task 6 is undefined and the error-handling snippet references undefined 'model' and 'logger' variables.

4 / 5

Workflow Clarity

Tasks are sequenced with a consistent Goal → example → reference pattern, but the skill covers batch processing and includes no validation or verification checkpoints (no batch result verification, no error-recovery loop for failed items). The rubric's guideline caps batch-operation workflows without validation at 3.

3 / 5

Progressive Disclosure

All referenced files exist (8 reference .md files and 5 scripts are present on disk), references are one level deep and clearly signaled ('See: references/...'), but SKILL.md itself inlines ~600 lines of full code examples that substantially duplicate the reference files and scripts — a minor organization gap that keeps it below the clean-overview anchor.

4 / 5

Total

14

/

20

Passed

Description

88%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 description: it is specific and comprehensive about capabilities, and includes an explicit, concrete 'Use when' trigger clause. The only weakness is that several trigger terms are generic across LLM providers, creating minor overlap risk, and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

The description enumerates multiple specific concrete capabilities — 'function calling, built-in tools (Google Search, Code Execution, File Search, URL Context), structured outputs, thought signatures, context caching, batch processing, and framework integration' — comprehensively covering the skill's feature areas with named tools, matching the top anchor rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is the full feature enumeration, and the 'when' is a concrete 'Use when implementing...' clause with specific trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

'Use when implementing tools, function calling, structured JSON output, context caching, batch API, LangChain, Vercel AI, or production features' gives good natural keyword coverage, but common variations like 'tool use', 'Google Search grounding', or 'structured output schema' are missing, so it falls just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Advanced Gemini 3 Pro features' framing carves a clear niche, but several trigger terms ('structured JSON output', 'context caching', 'production features') are provider-agnostic and could cause overlap with similar skills for other providers, so it sits at 'mostly distinct; minor overlap risk' rather than minimal conflict.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (629 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

skills/gemini-3-advanced/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.