uni-google

Google Suite via uni CLI. Use when user mentions: calendar, events, schedule, meetings, Gmail, email, Drive, files, Sheets, spreadsheet, Docs, documents, Slides, presentations, Forms, surveys, Meet, video call, Tasks, todos, Contacts. Trigger words: calendar, gcal, gmail, email, drive, sheets, docs, slides, forms, meet, tasks, contacts, google. Services: gcal, gmail, gdrive, gsheets, gdocs, gslides, gforms, gmeet, gtasks, gcontacts.

Quality

76%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skill/skills/uni-google/SKILL.md

Quality

Discovery

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description excels at trigger term coverage and distinctiveness, providing comprehensive keywords users would naturally use when needing Google Suite functionality. However, it lacks specificity about what concrete actions can be performed with each service - it reads more like a keyword list than a capability description. Adding specific actions (e.g., 'create calendar events', 'send emails', 'upload files to Drive') would significantly improve it.

Suggestions

Add concrete action verbs for each service (e.g., 'Create and manage calendar events, send and read emails, upload and organize Drive files, edit spreadsheets and documents')

Restructure to lead with capabilities before listing trigger words - the current format prioritizes triggers over explaining what the skill actually does

Dimension	Reasoning	Score
Specificity	Names the domain (Google Suite via uni CLI) and lists services, but doesn't describe concrete actions like 'create events', 'send emails', or 'upload files'. It tells what tools are available but not what specific operations can be performed.	2 / 3
Completeness	Has a 'Use when user mentions' clause which addresses 'when', but the 'what' is weak - it only says 'Google Suite via uni CLI' without explaining what actions/capabilities are available. The description is trigger-heavy but capability-light.	2 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'calendar', 'events', 'schedule', 'meetings', 'Gmail', 'email', 'Drive', 'files', 'spreadsheet', 'documents', etc. Includes both formal names and casual variations users naturally use.	3 / 3
Distinctiveness Conflict Risk	Very distinct niche focused specifically on Google Suite services via the uni CLI tool. The explicit service names (gcal, gmail, gdrive, etc.) and Google-specific terminology make it unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable and concise CLI reference that provides excellent copy-paste ready commands for all Google services. The main weaknesses are the lack of validation/verification steps for destructive operations and the lengthy Sheets section that could benefit from being split into a separate reference file.

Suggestions

Add validation guidance for destructive operations (e.g., 'Before uni gsheets clear, verify range with uni gsheets get <id> <range>')

Consider moving the extensive Sheets section to a separate GSHEETS.md file with a brief summary and link in the main skill

Add error handling guidance or common failure modes for operations like auth failures or permission issues

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations of what Google services are or how OAuth works. Every line is a concrete command example that earns its place.	3 / 3
Actionability	Fully copy-paste ready commands with clear flags and arguments. Examples cover common use cases with inline comments explaining what each command does.	3 / 3
Workflow Clarity	Commands are well-organized by service, but lacks validation checkpoints for destructive operations (delete, clear). No guidance on verifying success or handling errors for batch operations like gsheets clear or gmail delete.	2 / 3
Progressive Disclosure	Well-organized sections by service, but the Sheets section is quite long (could be split to a separate reference). No links to external documentation or advanced guides for complex operations.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shockz09/uni-cli
Commit: f1dfc90

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.