service-account-manager
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill service-account-managerService Account Manager - Auto-activating skill for GCP Skills. Triggers on: service account manager, service account manager Part of the GCP Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just naming the skill without explaining its capabilities or providing meaningful trigger guidance. It lacks any concrete actions, has redundant and narrow trigger terms, and provides no 'Use when...' scenarios that would help Claude select this skill appropriately from a larger skill set.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, lists, deletes, and manages GCP service accounts. Handles key rotation, IAM bindings, and permission assignments.'
Include a 'Use when...' clause with natural trigger scenarios: 'Use when the user needs to create service accounts, manage GCP credentials, set up IAM permissions, or work with Google Cloud authentication.'
Expand trigger terms to include variations users would naturally say: 'service account', 'GCP IAM', 'Google Cloud credentials', 'API keys', 'workload identity', '.json key file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Service Account Manager') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'create', 'manage', 'delete', 'list', or other specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('service account manager' listed twice) and overly narrow. Missing natural variations users might say like 'GCP service account', 'IAM', 'create service account', 'manage permissions', or 'Google Cloud credentials'. | 1 / 3 |
Distinctiveness Conflict Risk | The GCP/service account focus provides some specificity that distinguishes it from generic document or code skills, but 'Service Account Manager' could overlap with other cloud provider skills or general IAM tools without clearer boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains no GCP service account-specific information, no gcloud commands, no IAM concepts, no code examples, and no actionable guidance whatsoever. The content would be identical if you replaced 'service account manager' with any other topic.
Suggestions
Add concrete gcloud commands for common service account operations (create, list, add-iam-policy-binding, keys create/delete)
Include executable code examples showing how to authenticate with service accounts and use them in applications
Define a clear workflow for service account lifecycle management with validation steps (e.g., verify permissions, test authentication)
Add specific guidance on service account best practices like key rotation, least-privilege principles, and workload identity federation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about service account management. | 1 / 3 |
Actionability | There is zero concrete guidance - no commands, no code, no specific steps for managing GCP service accounts. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating, managing, or configuring service accounts, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed documentation, no links to GCP-specific guides, and no structured navigation to actual implementation details. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.