tessl install https://github.com/softaworks/agent-toolkit --skill geminigithub.com/softaworks/agent-toolkit
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
Average Score
80%
Content
77%
Description
75%
Generated
Validations
Total score
14/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 224 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'gemini' | |
description_field 'description' field is valid (243 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 3
Total score
10/12| Dimension | Score |
|---|---|
conciseness The skill contains useful information but is verbose in places, with repeated warnings about background mode (mentioned 5+ times) and some redundancy between the quick reference table and the common use cases section. The model selection guide is thorough but could be more condensed. | 2/3 |
actionability Provides fully executable bash commands throughout, with specific flags, model names, and copy-paste ready examples. The troubleshooting section includes concrete diagnostic commands and the quick reference table maps use cases to exact command patterns. | 3/3 |
workflow_clarity Clear numbered steps for running tasks (1-7), explicit validation checkpoints (ask user for model, check for hung processes), and feedback loops for error handling. The troubleshooting section provides detection → diagnosis → resolution workflow with explicit commands at each step. | 3/3 |
progressive_disclosure Content is well-organized with clear sections and headers, but everything is in a single file. The skill is ~200 lines and could benefit from splitting detailed troubleshooting and model comparison into separate reference files, keeping SKILL.md as a concise overview. | 2/3 |
Suggestions
Consolidate the background/non-interactive mode warnings into a single prominent section rather than repeating throughout the document
Consider moving the detailed troubleshooting section and model comparison table to separate reference files (e.g., TROUBLESHOOTING.md, MODELS.md) to reduce SKILL.md length
Remove redundancy between the 'Quick Reference' table and 'Common Use Cases' section—one or the other would suffice
Overall Assessment
This is a well-structured, highly actionable skill with excellent workflow clarity and concrete executable examples. The main weakness is verbosity—the critical warning about background mode is repeated excessively, and the content could be more token-efficient by consolidating redundant sections and potentially splitting detailed reference material into separate files.
Description
Suggestions 2
Total score
10/12| Dimension | Score |
|---|---|
specificity Names the domain (Gemini CLI) and some actions (code review, plan review, big context processing), but lacks comprehensive concrete actions. 'Comprehensive analysis' is somewhat vague. | 2/3 |
completeness Clearly answers both what (run Gemini CLI for code review, plan review, big context processing) and when (explicit 'Use when' clause with specific triggers for user requests). | 3/3 |
trigger_term_quality Includes some natural terms like 'code review', 'plan review', and '>200k' context, but missing common variations users might say like 'large file', 'long document', 'Gemini', or 'external model'. | 2/3 |
distinctiveness_conflict_risk Clear niche targeting Gemini CLI specifically with distinct triggers around large context windows (>200k) and specific review types. Unlikely to conflict with general code review or document processing skills. | 3/3 |
Suggestions
Add more specific concrete actions beyond 'comprehensive analysis' - e.g., 'analyze large codebases', 'review lengthy documents', 'process files exceeding Claude's context limit'
Include additional natural trigger terms users might say: 'large file', 'too long', 'external model', 'Gemini', 'big document', 'context limit'
Overall Assessment
This description has good structure with an explicit 'Use when' clause and clear differentiation through the Gemini CLI and large context window focus. However, it could be more specific about concrete actions beyond 'comprehensive analysis' and include more natural trigger term variations that users might actually say.