google-workspace
Build integrations with Google Workspace APIs (Gmail, Calendar, Drive, Sheets, Docs, Chat, Meet, Forms, Tasks, Admin SDK). Covers OAuth 2.0, service accounts, rate limits, batch operations, and Cloudflare Workers patterns. Use when building MCP servers, automation tools, or integrations with any Google Workspace API, or troubleshooting OAuth errors, rate limit 429 errors, scope issues, or API-specific gotchas.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill google-workspace92
Does it follow best practices?
Validation for skill structure
Discovery
100%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 is a strong skill description that excels across all dimensions. It provides comprehensive coverage of specific Google Workspace APIs, includes natural trigger terms users would actually search for (including error codes), and has an explicit 'Use when' clause covering both building and troubleshooting scenarios. The description is well-structured and clearly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'Build integrations with Google Workspace APIs' followed by specific APIs (Gmail, Calendar, Drive, Sheets, Docs, Chat, Meet, Forms, Tasks, Admin SDK) and technical concepts (OAuth 2.0, service accounts, rate limits, batch operations, Cloudflare Workers patterns). | 3 / 3 |
Completeness | Clearly answers both what ('Build integrations with Google Workspace APIs... Covers OAuth 2.0, service accounts...') AND when with explicit 'Use when' clause covering building scenarios and troubleshooting specific error types. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: specific API names (Gmail, Calendar, Drive, Sheets), common error scenarios (OAuth errors, rate limit 429 errors, scope issues), and use case terms (MCP servers, automation tools, integrations). | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Google Workspace APIs with distinct triggers like specific API names, OAuth errors, and 429 rate limits. Unlikely to conflict with generic coding or other cloud platform skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, production-ready skill that efficiently covers Google Workspace API integration patterns. The code examples are executable and comprehensive, covering OAuth, service accounts, rate limiting, and batch operations. The main weakness is the lack of explicit validation checkpoints in multi-step workflows like service account setup.
Suggestions
Add explicit validation steps to the service account setup workflow (e.g., 'Test token: curl -H "Authorization: Bearer $TOKEN" https://www.googleapis.com/oauth2/v1/tokeninfo')
Include a verification step after token exchange to confirm the token works before storing it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing code examples without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what APIs are or how OAuth works conceptually. | 3 / 3 |
Actionability | Provides fully executable TypeScript code for OAuth flows, service account authentication, batch requests, and retry logic. Code is copy-paste ready with proper imports and complete function signatures. | 3 / 3 |
Workflow Clarity | While individual code blocks are clear, the service account setup steps are listed without validation checkpoints. The retry logic is good, but there's no explicit workflow for 'authenticate -> test -> proceed' or validation that tokens work before using them. | 2 / 3 |
Progressive Disclosure | Excellent structure with a quick reference table at top, shared patterns in the main file, and clear one-level-deep references to API-specific guides in the references/ directory. Navigation is well-signaled with consistent formatting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.