gemini
Gemini CLI for one-shot Q&A, summaries, and generation.
64
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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...'), making it difficult for Claude to know when to select this skill. While 'Gemini CLI' provides some distinctiveness, the listed capabilities are vague and generic. The description needs concrete actions and clear selection criteria.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to run a one-shot query through Gemini CLI, or asks to summarize or generate text using Gemini from the command line.'
Make the capabilities more specific—instead of 'generation', specify what kind (e.g., 'generate code snippets, draft text, translate content via Gemini CLI').
Include natural trigger terms users might say, such as 'ask Gemini', 'gemini prompt', 'run gemini', or 'gemini command line'.
| 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 there's no detail about what kind of content or how. | 2 / 3 |
Completeness | It partially describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause 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 user phrases like 'ask Gemini', 'gemini query', 'one-shot prompt', or 'LLM CLI'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gemini CLI' is a fairly specific tool reference that helps distinguish it, but 'Q&A, summaries, and generation' are extremely broad capabilities that could overlap with many other skills involving text generation or summarization. | 2 / 3 |
Total | 7 / 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.
A concise, well-structured skill that efficiently communicates how to use Gemini CLI in one-shot mode. Its main weakness is slightly incomplete actionability—it could benefit from specifying available model names or showing a concrete example with expected output. Overall it's a solid simple skill that respects token budget.
Suggestions
Add one concrete example showing a full command with expected output (e.g., `gemini "What is 2+2?"` → expected response format)
List common model names or show how to discover them (e.g., `gemini --list-models`)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Gemini is or how CLIs work. Every line provides actionable information. | 3 / 3 |
Actionability | Provides concrete commands that are copy-paste ready, but lacks specifics like available model names, what JSON output looks like, or what extension commands are available. The guidance is real but incomplete. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (one-shot CLI usage). The single action is unambiguous, and the auth note provides a clear fallback path. No multi-step destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (quick start, extensions, notes). No unnecessary nesting or monolithic blocks. | 3 / 3 |
Total | 11 / 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.