CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-workspace-admin

Google Workspace administration agent using the gws CLI. Orchestrates workspace setup, Gmail/Drive/Sheets/Calendar automation, security audits, and recipe execution. Spawn when users need Google Workspace automation, gws CLI help, or workspace administration.

65

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-workspace-admin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A well-organized, actionable skill body with clear workflows and external references. Its main weakness is token efficiency: the full nested path is repeated verbatim throughout instead of being defined once and reused.

Suggestions

Define the long base path once (e.g. "GWS=../../engineering-team/google-workspace-cli/skills/google-workspace-cli") and reference scripts as "$GWS/scripts/gws_doctor.py" to avoid repeating the full path in every example.

Add an explicit post-execution verification checkpoint to the Daily Operations and Automation Scripting workflows (e.g. confirm recipe output or re-check dry-run results) to match the security audit's feedback loop.

Consolidate the Python Tools list and the Core Workflows so each tool's usage appears once rather than being restated in every workflow example.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but the very long path "../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/..." is repeated in full across the tools list and every workflow example, which is a notable token waste that could be tightened.

3 / 5

Actionability

Provides concrete, executable commands with real flags (e.g. "gws_recipe_runner.py --run <name> --dry-run", "workspace_audit.py --json | ... --filter status=FAIL"), with only minor gaps from placeholder values like <name> and <role>.

4 / 5

Workflow Clarity

Four workflows are clearly sequenced with goals and numbered steps, and destructive/batch validation is addressed ("use --dry-run first", "Re-run audit to verify fixes"); however not every workflow has an explicit post-execution checkpoint.

4 / 5

Progressive Disclosure

SKILL.md acts as an overview with well-signaled one-level-deep references to knowledge bases, templates, and scripts; minor gaps come from references pointing into an external sibling skill's deeply nested paths rather than a local bundle.

4 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong, third-person description that clearly states capabilities and provides an explicit spawn trigger. It is comprehensive and distinctive, with only minor room to broaden trigger-term synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the domain — "workspace setup, Gmail/Drive/Sheets/Calendar automation, security audits, and recipe execution" — naming four services and four action types for comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ("Orchestrates workspace setup...security audits, and recipe execution") and when ("Spawn when users need Google Workspace automation, gws CLI help, or workspace administration") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("Google Workspace automation", "gws CLI help", "workspace administration") that users would plausibly say, but a few synonyms or service-level variations are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to "Google Workspace administration agent using the gws CLI," a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing, 2 suspicious

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.