CtrlK
BlogDocsLog inGet started
Tessl Logo

admin

Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning. Creates stacks via the Cloud API, mints service-account tokens, applies role assignments, configures SSO providers, and provisions teams/folders/dashboards via Terraform. Use when managing Grafana Cloud access, configuring SSO/SAML/OAuth, setting up service accounts for Terraform/CI/CD, assigning RBAC roles, inviting users, managing multiple stacks or organizations, provisioning cloud resources via API or Terraform, or auditing admin actions — even when the user says "set up SSO", "create a stack", "make a service account", or "onboard a team" without explicitly saying "admin".

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

The body is a lean, fully executable overview: complete curl/YAML examples, explicit validation and recovery steps in every workflow (including the destructive delete), and clean delegation to three annotated one-level-deep reference files. It matches the strongest anchors on all four dimensions with no trimming or reorganization needed.

DimensionReasoningScore

Conciseness

The body is nearly all executable code, tables, and short bullets with zero explanation of general concepts; the one framing line about service accounts is minimal, actionable guidance. Not 4: no section is trimmable — the org/stack structure and Cloud role scopes are product-specific, not knowledge Claude already has.

5 / 5

Actionability

Copy-paste-ready curl commands with headers, payloads, and realistic values (poll loop for stack readiness, full provisioning YAML for RBAC roles/assignments and service accounts). Not 4: the common cases are fully covered inline and the remainder is precisely delegated to reference files.

5 / 5

Workflow Clarity

Every workflow carries explicit validation with feedback loops: poll until 200, token tested on /api/org with a recovery hint, RBAC role verified via jq query, team membership listed back, and the destructive stack delete verified for 404 with troubleshooting guidance. The destructive-operation cap does not apply because validation is present throughout.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with three well-signaled, one-level-deep references, each annotated with its contents; all anchor links (e.g. references/sso.md#verifying-sso, api-reference.md#stack-api--user--team--org-management) resolve to real headers in the bundle. Not 4: navigation and content split leave nothing misplaced.

5 / 5

Total

20

/

20

Passed

Description

100%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.

An exemplary description: it states comprehensive concrete capabilities in third person, provides an explicit 'Use when…' clause with concrete triggers, and even anticipates paraphrased user requests. Voice is correctly third person, so no penalty applies.

DimensionReasoningScore

Specificity

Lists five named concrete actions ("Creates stacks via the Cloud API, mints service-account tokens, applies role assignments, configures SSO providers, and provisions teams/folders/dashboards via Terraform") with comprehensive coverage of the domain. Not 4: there are no gaps in the action coverage; the examples are as comprehensive as the anchor's PDF skill.

5 / 5

Completeness

Explicitly answers both what ("Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments…") and when ("Use when managing Grafana Cloud access… even when the user says 'set up SSO'…") with concrete trigger phrases. Not 4: the 'when' clause is fully explicit and includes quoted user phrasings rather than being merely implied.

5 / 5

Trigger Term Quality

Covers natural terms and synonyms comprehensively: "SSO/SAML/OAuth/GitHub", "service accounts for Terraform/CI/CD", "assigning RBAC roles", "inviting users", plus literal user phrasings ("set up SSO", "create a stack", "onboard a team"). Not 4: no common variation a user would naturally say is missing.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Grafana Cloud account administration) with product-specific triggers (stacks, RBAC, SAML, Cloud API), making conflict with other skills minimal. Not 4: the domain framing is unambiguous and no closely-related skill would claim these triggers.

5 / 5

Total

20

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
grafana/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.