service-account-manager
Service Account Manager - Auto-activating skill for GCP Skills. Triggers on: service account manager, service account manager Part of the GCP Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/service-account-manager/SKILL.mdQuality
Discovery
7%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 extremely weak — it is essentially just a title and category label with no concrete actions, no trigger guidance, and no explanation of when to use it. It would be nearly impossible for Claude to reliably select this skill from a pool of similar GCP skills. The repeated trigger term adds no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, lists, deletes, and manages GCP service accounts and their keys. Assigns IAM roles and permissions to service accounts.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating or managing GCP service accounts, generating service account keys, or assigning IAM roles.'
Include common user-facing keywords and variations such as 'service account', 'IAM', 'GCP permissions', 'service account key', 'workload identity', '.json key file' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions at all. 'Service Account Manager' is just a title repeated, with no indication of what it actually does (create, delete, list, assign roles to service accounts, etc.). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explicit 'Use when...' clause and no description of capabilities beyond the title. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'service account manager' repeated twice. It misses natural user phrases like 'create service account', 'IAM', 'GCP permissions', 'service account key', 'grant role', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'GCP' and 'service account' provides some domain specificity that narrows the scope, but without concrete actions it could overlap with other GCP-related skills or IAM skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no substantive content. It contains only meta-descriptions and trigger phrases but provides absolutely no actionable guidance on GCP service account management—no gcloud commands, no IAM best practices, no code examples, no workflows for common tasks like creating, listing, or rotating service account keys.
Suggestions
Add concrete gcloud CLI commands for common service account operations (e.g., `gcloud iam service-accounts create`, `gcloud iam service-accounts keys create`, `gcloud projects add-iam-policy-binding`) with executable examples.
Include a clear multi-step workflow for service account lifecycle management (create → assign roles → generate keys → rotate keys → disable/delete) with explicit validation steps like verifying permissions with `gcloud iam service-accounts get-iam-policy`.
Add specific best practices as actionable rules (e.g., 'Use workload identity federation instead of key files when possible', 'Apply least-privilege principle: prefer predefined roles over primitive roles', 'Set key expiration policies').
Remove all boilerplate meta-sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actual technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding that convey no useful information to Claude. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No commands, no code, no specific GCP CLI invocations, no API calls, no IAM role references—nothing that would help Claude actually manage a service account. The entire content describes rather than instructs. | 1 / 3 |
Workflow Clarity | There are no steps, no sequences, no validation checkpoints. Service account management involves potentially destructive operations (key rotation, permission changes, deletion) that demand clear workflows with verification, yet none are provided. | 1 / 3 |
Progressive Disclosure | There is no meaningful structure beyond boilerplate headings. No references to external files, no layered content organization. The sections (Purpose, When to Use, Capabilities, Example Triggers, Related Skills) are all meta-information with no substantive content to organize. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.