google-workspace
Google Workspace integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Google Workspace. Routes through Apideck with serviceId "google-workspace".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 description that clearly identifies the specific integration (Google Workspace via Apideck HRIS unified API), lists concrete data entities it handles (employees, departments, payrolls, time-off records), and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId and the unified API pattern adds helpful technical context for disambiguation from other Apideck connectors.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read or sync employees, departments, payrolls, and time-off records' and mentions the integration mechanism (Apideck's HRIS unified API, serviceId). These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Google Workspace integration via Apideck HRIS API for employees, departments, payrolls, time-off) and 'when' (explicit 'Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Google Workspace'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Google Workspace', 'employees', 'departments', 'payrolls', 'time-off records', 'HRIS', 'Apideck', 'sync'. Good coverage of domain-specific terms a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the combination of 'Google Workspace' + 'Apideck' + 'HRIS' + specific serviceId 'google-workspace'. This clearly carves out a niche that wouldn't conflict with generic HR skills or other Apideck connector skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid connector-specific skill with good actionability and excellent progressive disclosure to related skills and references. Its main weaknesses are some marketing-style verbosity (repeating the portability pitch multiple times) and a lack of a clear sequential workflow with validation checkpoints for the integration process. The code examples are strong and executable.
Suggestions
Remove or condense the 'Portable across 58 HRIS connectors' section — the portability point is already made in the intro and the code example speaks for itself.
Add a brief numbered workflow (e.g., 1. Verify connection is callable, 2. Check coverage for needed operations, 3. Make API call, 4. Handle errors/fallback to proxy) to give Claude a clear decision sequence.
Trim the 'When to use this skill' section — Claude doesn't need to be told what the skill teaches it; the content itself demonstrates that.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 58 HRIS connectors' section repeats the marketing pitch from the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating Google Workspace directly' are sales copy that Claude doesn't need. The 'When to use this skill' section also over-explains. However, the code examples and quick facts are lean. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing employees, concrete curl commands for verifying coverage and using the proxy API, specific serviceId strings, and environment variable patterns. The examples are copy-paste ready with real SDK imports and method calls. | 3 / 3 |
Workflow Clarity | The skill covers a multi-step integration workflow (auth → verify coverage → call API → fallback to proxy) but doesn't present it as a clear sequential workflow with validation checkpoints. The coverage verification step is mentioned but not integrated into a 'before you call, do this' checklist. There's no explicit error handling flow for when operations fail. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in the main file and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and sibling connectors. The 'See also' section provides clear navigation to related resources. | 3 / 3 |
Total | 10 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.