gemini
Gemini CLI for one-shot Q&A, summaries, and generation.
75
66%
Does it follow best practices?
Impact
99%
1.32xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gemini/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is too terse and lacks explicit trigger guidance ('Use when...'). While 'Gemini CLI' provides some distinctiveness, the listed capabilities (Q&A, summaries, generation) are overly broad and don't clearly differentiate this skill from other text-processing or LLM-related skills. The description needs both more specific actions and explicit usage triggers.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when the user wants to run Gemini CLI commands', 'when asking to query Gemini from the terminal', or 'when one-shot LLM prompts via command line are needed'.
Make capabilities more concrete—e.g., 'Runs Gemini CLI to send one-shot prompts, summarize files or text, generate content from command-line queries' instead of the vague 'Q&A, summaries, and generation'.
Add natural trigger terms users might say, such as 'gemini command', 'ask gemini', 'gemini prompt', or 'CLI LLM query'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the tool (Gemini CLI) and some actions (Q&A, summaries, generation), but these actions are broad and not very concrete—'generation' is vague, and the specific capabilities within each category are not elaborated. | 2 / 3 |
Completeness | It partially answers 'what' (Gemini CLI for Q&A, summaries, generation) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Gemini CLI' which is a useful trigger term, and 'Q&A', 'summaries', 'generation' are somewhat relevant keywords. However, it misses natural variations users might say like 'ask Gemini', 'gemini query', 'one-shot prompt', or 'LLM CLI'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gemini CLI' is a fairly distinct trigger that narrows the domain, but 'Q&A, summaries, and generation' are extremely broad capabilities that could overlap with many other skills involving text generation, summarization, or question answering. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, minimal skill that efficiently communicates how to use Gemini CLI in one-shot mode. It's concise, actionable, and appropriately scoped for its simple purpose. The safety note about --yolo and the auth guidance add practical value without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Gemini is or how CLIs work. Every line provides actionable information Claude wouldn't inherently know. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for the primary use case (one-shot mode), model selection, output format, and extension management. The auth note is specific and actionable. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (one-shot CLI usage) with no multi-step destructive operations. The single action is unambiguous, and the notes section provides clear guidance on edge cases like auth and safety. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with no need for external references, the content is well-organized into logical sections (quick start, extensions, notes) that are easy to scan. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.