gws-vault
Google Vault: Manage eDiscovery holds and exports.
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 93%
↑ 2.58xAgent success when using this skill
Validation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear, specific product domain (Google Vault) which provides good distinctiveness, but it is too terse. It lacks explicit trigger guidance for when to use the skill and could benefit from more specific action verbs and common user terminology around legal holds and compliance workflows.
Suggestions
Add a 'Use when...' clause with trigger terms like 'legal hold', 'litigation hold', 'eDiscovery export', 'compliance', or 'data preservation'
Expand the capability list with more specific actions such as 'create matters', 'search mailboxes', 'set retention policies', or 'generate audit reports'
Include common variations users might say like 'Vault hold', 'export emails for legal', or 'preserve data for litigation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Vault, eDiscovery) and mentions two actions (holds and exports), but lacks comprehensive detail about what specific operations can be performed with these features. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Google Vault', 'eDiscovery', 'holds', and 'exports' which users familiar with the domain would use, but misses common variations like 'legal hold', 'litigation hold', 'data retention', or 'compliance'. | 2 / 3 |
Distinctiveness Conflict Risk | Google Vault is a specific product with a clear niche in eDiscovery; unlikely to conflict with other skills due to the distinct product name and specialized legal/compliance domain. | 3 / 3 |
Total | 8 / 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 well-organized, concise API reference skill that efficiently documents available Vault resources and methods. However, it lacks concrete usage examples and workflow guidance for common eDiscovery tasks, which are typically multi-step processes with legal implications requiring careful sequencing.
Suggestions
Add 1-2 concrete executable examples showing common workflows (e.g., creating a matter and adding a hold with actual --params syntax)
Include a brief workflow section showing the typical sequence: create matter → add hold → create export → check operation status
Add a note about verification steps for legal hold operations given their compliance implications
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information: command syntax, resource/method listings, and discovery commands. No unnecessary explanations of what Vault is or how eDiscovery works. | 3 / 3 |
Actionability | Provides command structure and method listings, but lacks concrete executable examples showing actual usage with parameters. The discovery commands are helpful but no complete working examples for common tasks like creating a hold or export. | 2 / 3 |
Workflow Clarity | For a simple reference skill, the structure is adequate, but eDiscovery workflows (create matter → add hold → export → download) are multi-step processes that would benefit from explicit sequencing. No validation checkpoints for operations that could affect legal holds. | 2 / 3 |
Progressive Disclosure | Appropriately structured with clear prerequisite reference to shared skill, organized sections for resources and discovery. The content is appropriately sized for a reference skill without needing additional files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
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 | 8 / 11 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.