Skip to content
TrustedSkillsbeta
Back to all skills

Draft Release

Checked
grafana·vlatest·devops·Apache-2.0

Draft Release helps you quickly create initial release notes drafts by summarizing changes from your tracked commits – saving time and ensuring consistency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add grafana/mcp-grafana --skill draft-release -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

grafana

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned grafana/mcp-grafana at 9dbfe137a5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9dbfe137a5
Manifest
.claude/skills/draft-release/SKILL.md
Scanned
1 file, 162 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The draft-release skill automates the process of creating and releasing Grafana dashboards. It can generate a new dashboard from a template, apply configuration changes, and deploy the updated dashboard to a Grafana instance. This streamlines the development and deployment workflow for Grafana users.

When to use it

  • You need to quickly create a new Grafana dashboard based on an existing template.
  • You want to automate applying configuration updates (e.g., data source connections, panel settings) to your dashboards.
  • You're managing multiple Grafana dashboards and require a consistent deployment process.
  • You are developing or maintaining Grafana dashboards as part of a larger DevOps pipeline.

Key capabilities

  • Dashboard creation from templates
  • Configuration updates via automation
  • Deployment to Grafana instances

Example prompts

  • "Create a new dashboard named 'System Metrics' based on the 'Standard Monitoring' template."
  • "Update the data source connection in all dashboards located in the '/dashboards/production/' directory."
  • "Deploy the changes from my local development environment to the staging Grafana instance."

Tips & gotchas

  • Requires familiarity with Grafana dashboard templates and configuration structure.