Content
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionability with concrete, copy-paste-ready CLI commands and comprehensive option/model tables. Its main weaknesses are moderate verbosity (generic agent instructions, redundant sections) and missing error recovery steps for authentication and runtime resolution workflows. The structure is reasonable but could benefit from clearer separation of reference material from core workflow.
Suggestions
Add explicit error handling/recovery steps for authentication failures (e.g., 'If browser doesn't open, check GEMINI_WEB_CHROME_PATH; if cookies fail, run --login') to improve workflow clarity.
Remove or significantly trim the 'User Input Tools' section — this is generic agent behavior that doesn't need 10+ lines of instruction in a Gemini API skill.
Remove the redundant 'Extension Support' section at the bottom since it just points back to the Preferences section already documented above.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables, but includes some unnecessary sections like the 'User Input Tools' block which is generic agent behavior, and the 'Extension Support' section at the end is redundant with the Preferences section. The authentication section has some verbose explanation about CDP session reuse that could be tightened. | 2 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples covering all major use cases (text generation, image generation, vision input, multi-turn conversations, JSON output). Options table is complete with clear descriptions, and environment variables are well-documented. | 3 / 3 |
Workflow Clarity | The consent check flow is well-sequenced with clear steps. However, the authentication workflow lacks explicit validation/error recovery steps (what if browser auth fails? what if cookies expire mid-session?). The script directory resolution is a multi-step process but lacks validation checkpoints for whether bun/npx is actually available. | 2 / 3 |
Progressive Disclosure | References EXTEND.md for configuration and mentions scripts/gemini-webapi/* for implementation details, which is good. However, without bundle files to verify, the inline content is somewhat heavy (full options table, models table, env vars table, sessions info could potentially be in a reference file). The EXTEND.md reference is mentioned but its actual supported options are only vaguely described. | 2 / 3 |
Total | 9 / 12 Passed |