Google Gemini File Search for managed RAG with 100+ file formats. Use for document Q&A, knowledge bases, or encountering immutability errors, quota issues, polling failures. Supports Gemini 3 Pro/Flash (Gemini 2.5 legacy).
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill google-gemini-file-searchOverall
score
88%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly identifies its niche (Google Gemini File Search) with good trigger terms and explicit 'Use for' guidance. The main weakness is that the capabilities could be more concrete - it describes the domain well but doesn't enumerate specific actions the skill enables beyond general 'document Q&A' and 'knowledge bases'.
Suggestions
Add more specific concrete actions like 'upload documents to corpora', 'query indexed files', 'manage file metadata' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Gemini File Search, managed RAG) and mentions some actions (document Q&A, knowledge bases), but doesn't list multiple concrete actions like 'upload files', 'query documents', or 'create knowledge bases'. | 2 / 3 |
Completeness | Clearly answers both what (Google Gemini File Search for managed RAG with 100+ file formats) and when (Use for document Q&A, knowledge bases, or encountering specific error types), with explicit 'Use for' trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'document Q&A', 'knowledge bases', 'Gemini', 'RAG', plus specific error scenarios ('immutability errors', 'quota issues', 'polling failures') and model names that users might reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific platform (Google Gemini), specific feature (File Search), and unique error scenarios that clearly differentiate it from generic document or RAG skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, production-ready skill with excellent actionability and workflow clarity. The code examples are complete and executable, error patterns are well-documented with solutions, and progressive disclosure is handled well with clear reference file guidance. Minor verbosity in the rules sections and some redundancy between 'Always Do/Never Do' lists prevent a perfect conciseness score.
Suggestions
Consolidate the 'Always Do' and 'Never Do' lists into a single 'Critical Rules' checklist to reduce redundancy
Trim the 'What Is File Search?' section - Claude doesn't need the comparison to other RAG solutions explained at length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the 'Critical Rules' section duplicates information found in the error examples, and the 'Always Do/Never Do' lists are somewhat repetitive mirror images of each other. The 'What Is File Search?' section could be tighter. | 2 / 3 |
Actionability | Excellent executable code examples throughout - the Quick Start, error prevention patterns, and common patterns sections all provide copy-paste ready TypeScript code with proper imports, error handling, and polling logic. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The document update flow shows numbered steps with polling verification, and the batch upload pattern includes proper operation polling. The 'Poll until done' pattern is consistently emphasized. | 3 / 3 |
Progressive Disclosure | Well-structured with clear navigation - main content provides actionable quick start, then references external files (setup-guide.md, error-catalog.md) with explicit 'When to Load References' section explaining when each is needed. One level deep, clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 14 / 16 Passed | |
Table of Contents
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.