How do I install the Newrelic CLI Deployments skill?

Run npx skillmds@latest add kilo-org/newrelic-cli-deployments in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Newrelic CLI Deployments safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Newrelic CLI Deployments?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Newrelic CLI Deployments free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Newrelic CLI Deployments?

Kilo-Org (@kilo-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Newrelic CLI Deployments by kilo-org

Name: Newrelic CLI Deployments
Author: Kilo-Org

Newrelic CLI Deployments

This subskill should be used when recording, listing, or automating New Relic APM deployment markers and correlating releases with performance changes. Use the parent newrelic-cli-skills skill for setup and routing.

Kilo-Org 9a270f6 2.4 KB Updated Sep 17, 2026

File contents

Deployment Markers

Record deployment events in New Relic so you can correlate releases with performance changes.

Record a Deployment

newrelic apm deployment create \
  --applicationId <APP_ID> \
  --revision "v1.2.3" \
  --description "Brief description of what changed" \
  --user "deploy-bot"

Required

--applicationId — numeric APM application ID
--revision — version string (e.g. git SHA, semver, MR number)

Optional

--description — what changed (show in NR UI on charts)
--user — who/what deployed
--changelog — detailed change notes

Get Application ID

newrelic entity search --name "my-app" --type APPLICATION --domain APM | \
  jq '.[] | {name, applicationId}'

List Recent Deployments

newrelic apm deployment list --applicationId <APP_ID>

GitLab/GitHub CI Integration

Add to your CI pipeline after a successful deploy:

#!/bin/bash
# deploy-marker.sh
APP_ID="${NEW_RELIC_APP_ID}"
REVISION="${CI_COMMIT_SHORT_SHA:-$(git rev-parse --short HEAD)}"
DESCRIPTION="${CI_COMMIT_TITLE:-Deployment}"
USER="${GITLAB_USER_LOGIN:-ci-bot}"

newrelic apm deployment create \
  --applicationId "$APP_ID" \
  --revision "$REVISION" \
  --description "$DESCRIPTION" \
  --user "$USER"

Why Deployment Markers Matter

After recording a deployment, the New Relic UI places a vertical line on all APM charts at that timestamp. This makes it immediately obvious if:

Response times increased after a deploy
Error rates spiked post-release
Throughput dropped unexpectedly

You can also query them via NRQL:

SELECT *
FROM Deployment
WHERE appId = <APP_ID>
SINCE 1 week ago

Automation: Mark on Every Merge

Script to call from a post-merge webhook or CI step:

#!/bin/bash
# Usage: ./deployment-marker.sh <app_id> <revision> <description>
set -euo pipefail

APP_ID="${1:?app_id required}"
REVISION="${2:?revision required}"
DESCRIPTION="${3:-Automated deployment}"

newrelic apm deployment create \
  --applicationId "$APP_ID" \
  --revision "$REVISION" \
  --description "$DESCRIPTION" \
  --user "ci-bot"

echo "Deployment marker recorded: $REVISION → app $APP_ID"

---name: newrelic-cli-deploymentsdescription: This subskill should be used when recording, listing, or automating New Relic APM deployment markers and correlating releases with performance changes. Use the parent newrelic-cli-skills skill for setup and routing.---# Deployment MarkersRecord deployment events in New Relic so you can correlate releases with performance changes.---## Record a Deployment```bashnewrelic apm deployment create \ --applicationId <APP_ID> \ --revision "v1.2.3" \ --description "Brief description of what changed" \ --user "deploy-bot"```### Required- `--applicationId` — numeric APM application ID- `--revision` — version string (e.g. git SHA, semver, MR number)### Optional- `--description` — what changed (show in NR UI on charts)- `--user` — who/what deployed- `--changelog` — detailed change notes---## Get Application ID```bashnewrelic entity search --name "my-app" --type APPLICATION --domain APM | \ jq '.[] | {name, applicationId}'```---## List Recent Deployments```bashnewrelic apm deployment list --applicationId <APP_ID>```---## GitLab/GitHub CI IntegrationAdd to your CI pipeline after a successful deploy:```bash#!/bin/bash# deploy-marker.shAPP_ID="${NEW_RELIC_APP_ID}"REVISION="${CI_COMMIT_SHORT_SHA:-$(git rev-parse --short HEAD)}"DESCRIPTION="${CI_COMMIT_TITLE:-Deployment}"USER="${GITLAB_USER_LOGIN:-ci-bot}"newrelic apm deployment create \ --applicationId "$APP_ID" \ --revision "$REVISION" \ --description "$DESCRIPTION" \ --user "$USER"```---## Why Deployment Markers MatterAfter recording a deployment, the New Relic UI places a vertical line on all APM charts at that timestamp. This makes it immediately obvious if:- Response times increased after a deploy- Error rates spiked post-release- Throughput dropped unexpectedlyYou can also query them via NRQL:```nrqlSELECT *FROM DeploymentWHERE appId = <APP_ID>SINCE 1 week ago```---## Automation: Mark on Every MergeScript to call from a post-merge webhook or CI step:```bash#!/bin/bash# Usage: ./deployment-marker.sh <app_id> <revision> <description>set -euo pipefailAPP_ID="${1:?app_id required}"REVISION="${2:?revision required}"DESCRIPTION="${3:-Automated deployment}"newrelic apm deployment create \ --applicationId "$APP_ID" \ --revision "$REVISION" \ --description "$DESCRIPTION" \ --user "ci-bot"echo "Deployment marker recorded: $REVISION → app $APP_ID"```

Frequently asked questions