gws-alertcenter
Google Workspace Alert Center: Manage Workspace security alerts.
62
47%
Does it follow best practices?
Impact
94%
3.24xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-alertcenter/SKILL.mdQuality
Discovery
22%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 is too brief and vague to effectively guide skill selection. It names the product but fails to specify concrete capabilities or provide trigger guidance. The lack of specific actions and missing 'Use when...' clause significantly limits Claude's ability to choose this skill appropriately.
Suggestions
Add specific actions like 'View, investigate, dismiss, and respond to security alerts including suspicious login attempts, malware detections, and policy violations'
Add a 'Use when...' clause with trigger terms like 'Google admin alerts', 'Workspace security', 'suspicious activity', 'security incidents', 'threat detection'
Include common user phrasings such as 'check security alerts', 'review admin notifications', or 'investigate suspicious login'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Manage') without listing concrete actions. It doesn't specify what 'manage' means - no mention of viewing, dismissing, investigating, or responding to alerts. | 1 / 3 |
Completeness | Only weakly addresses 'what' (manage alerts) and completely missing 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Google Workspace', 'Alert Center', 'security alerts') but misses common variations users might say like 'admin alerts', 'security notifications', 'threat alerts', or 'suspicious activity'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Workspace Alert Center' is a specific product name which helps distinguish it, but 'security alerts' is generic enough to potentially conflict with other security monitoring or alerting skills. | 2 / 3 |
Total | 6 / 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 skill is well-structured and concise, appropriately referencing shared documentation and organizing API resources clearly. However, it lacks concrete executable examples of actual alert operations and misses validation/verification guidance for destructive operations like batchDelete. The skill would benefit from at least one complete example showing a real API call with parameters.
Suggestions
Add 1-2 executable examples showing actual API calls (e.g., listing alerts, deleting an alert) with specific --params usage
Include validation/verification guidance for destructive operations like batchDelete and batchUndelete (e.g., list alerts first, confirm results after)
Show an example of the expected output format from common operations to help verify success
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information about the API resources and methods without explaining concepts Claude already knows. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands for discovery (--help, gws schema) but lacks executable examples of actual API calls. No copy-paste ready examples showing how to list alerts, delete an alert, or update settings with specific parameters. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic two-step workflow for exploration, but there are no validation checkpoints or feedback loops for operations like batch delete which are destructive and should have verification steps. | 2 / 3 |
Progressive Disclosure | Appropriately structured with a clear prerequisite reference to shared skills, well-organized resource sections, and guidance on using gws schema for deeper exploration. References are one level deep and clearly signaled. | 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 | |
- Repository
- googleworkspace/cli
- Commit
6ed836c
- 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.