Grafana Cloud account management — organizations, stacks, RBAC, SSO/SAML/OAuth, service accounts, API keys, team management, billing, and cloud-level provisioning. Use when managing Grafana Cloud access, configuring SSO, setting up service accounts for CI/CD, assigning roles, managing multiple stacks or organizations, or provisioning cloud resources via API.
66
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/grafana-cloud/admin/SKILL.mdQuality
Discovery
100%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 is an excellent skill description that clearly defines its scope (Grafana Cloud account management), lists comprehensive specific capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. It uses proper third-person voice and is concise yet thorough, making it easy for Claude to distinguish from other Grafana-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: organizations, stacks, RBAC, SSO/SAML/OAuth, service accounts, API keys, team management, billing, and cloud-level provisioning. These are all distinct, concrete actions/domains. | 3 / 3 |
Completeness | Clearly answers both 'what' (Grafana Cloud account management with a detailed list of capabilities) and 'when' (explicit 'Use when...' clause covering managing access, configuring SSO, setting up service accounts for CI/CD, assigning roles, managing stacks/orgs, and provisioning via API). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Grafana Cloud', 'SSO', 'SAML', 'OAuth', 'service accounts', 'API keys', 'RBAC', 'CI/CD', 'roles', 'stacks', 'organizations', 'billing'. These are terms users would naturally use when seeking help with Grafana Cloud account management. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Grafana Cloud account-level management, clearly separated from Grafana dashboard creation, alerting, or data source configuration. The focus on cloud account management, RBAC, SSO, and organizational structure creates a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, concrete examples covering a broad range of Grafana Cloud admin tasks — its greatest strength. However, it suffers from being a monolithic reference document with no progressive disclosure or external file references, and it lacks workflow sequencing and validation steps for multi-step or destructive operations. The content would benefit significantly from being restructured into an overview with pointers to detailed sub-files.
Suggestions
Split SSO configurations (OAuth, SAML, GitHub) into a separate SSO.md file and the Terraform examples into a TERRAFORM.md file, keeping only a brief summary and links in the main SKILL.md.
Add explicit workflow sequences with validation checkpoints for multi-step operations like stack creation, service account setup, and SSO configuration (e.g., 'verify SSO login works before disabling password auth').
Add a navigation section at the top or bottom that clearly signals where to find detailed content for each topic area.
For destructive operations like stack deletion, add confirmation/validation steps (e.g., 'verify stack name matches before deleting, check no active dashboards remain').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete examples, but it's quite long and includes multiple SSO configurations (OAuth, SAML, GitHub) that could be split into a reference file. The Terraform block is extensive and could be trimmed or referenced externally. Some sections like the full provider block with team/user/folder/dashboard resources go beyond what's needed in an overview. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides fully executable code: curl commands with proper headers, complete YAML provisioning files, full Terraform HCL, and INI configuration blocks. All examples are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | The skill presents individual operations clearly but lacks sequenced workflows with validation checkpoints. For example, creating a service account and then creating a token are shown as separate commands without explicit sequencing guidance. Stack creation/deletion (destructive operations) have no validation or confirmation steps. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no layered structure. All SSO configurations, Terraform examples, API endpoints, and RBAC provisioning are inlined in a single file that runs well over 150 lines. There's a single docs link at the top but no structured navigation or content splitting. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
a031314
Table of Contents
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.