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 for when Claude should select this skill. While it names the tool (Gemini CLI) and lists broad capability categories, the actions are generic and there is no 'Use when...' clause to help Claude distinguish when to apply this skill versus others.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to run Gemini CLI commands, query Gemini from the terminal, or needs one-shot text generation without a conversation.'
Make the capabilities more specific—instead of 'Q&A, summaries, and generation', describe concrete actions like 'sends single prompts to Gemini via CLI, summarizes documents or text, generates content from command-line inputs'.
Include natural trigger terms users might say, such as 'gemini command line', 'ask gemini', 'gemini prompt', or 'run gemini'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gemini CLI) and some actions (Q&A, summaries, generation), but these actions are fairly generic and not deeply specific about what concrete operations are performed. | 2 / 3 |
Completeness | Describes what it does at a high level 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 relevant trigger term, and 'Q&A', 'summaries', 'generation' are somewhat natural but missing common variations like 'gemini command line', 'ask gemini', 'generate with gemini', or 'one-shot prompt'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gemini CLI' provides some distinctiveness as a specific tool, but 'Q&A, summaries, and generation' are extremely broad capabilities that could overlap with many other skills. The 'one-shot' qualifier helps slightly. | 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 incomplete actionability—it could benefit from listing available models or output formats. The safety note about --yolo and the auth recovery guidance are good touches.
Suggestions
Add a brief list of common model names (e.g., `gemini-2.5-pro`, `gemini-2.5-flash`) so Claude can select the right one without guessing.
Include the available `--output-format` options and common extension commands to make the reference more complete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line provides actionable information without explaining what Gemini is or how CLIs work. No unnecessary padding. | 3 / 3 |
Actionability | Provides concrete commands that are copy-paste ready, but lacks key details like available model names, what output formats are supported, and what extension commands exist. 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 recovery path. No multi-step destructive operations require validation checkpoints. | 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). No bundle files are needed for this scope. | 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.