Skip to content
TrustedSkillsbeta
Back to all skills

Monitoring Setup

Listed
shipshitdev·vlatest·devops

Helps with monitoring, setup and configuration as part of automating DevOps pipelines and CI/CD workflows workflows.

Repository

Install on your platform

This skill no longer installs under the name monitoring-setup. shipshitdev/skills has no skill named "monitoring-setup" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-27. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

shipshitdev

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: shipshit.dev.

    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.

    Hosts contacted

    shipshit.devundeclared

    What it found

    • bundles/infrastructure/skills/monitoring-setup/plugin.json:8contacts shipshit.dev
      "url": "https://shipshit.dev"
    • skills/monitoring-setup/plugin.json:8contacts shipshit.dev
      "url": "https://shipshit.dev"

  • 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 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 shipshitdev/skills at cccb912bdd.

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

Commit
cccb912bdd
Manifest
skills/monitoring-setup/SKILL.md
Scanned
4 files, 246 lines
Copies in repo
2 — all of them scanned
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

This skill empowers AI agents to configure monitoring for NestJS and Next.js applications. It specifically enables setup of Sentry for error tracking and Google Analytics for user analytics, supporting automated DevOps pipelines and CI/CD workflows. The agent can guide users through the necessary installation steps and configuration processes for both backend (NestJS) and frontend (Next.js) components.

When to use it

  • You need to implement error tracking using Sentry.
  • You want to configure Google Analytics to track user behavior on your application.
  • You are deploying a production application and require comprehensive monitoring.
  • You want to track specific events like user signups, purchases, or feature usage.

Key capabilities

  • Sentry Setup (NestJS): Provides instructions for installation (npm install @sentry/node @sentry/profiling-node), initialization in main.ts, and configuration using the SENTRY_DSN environment variable. Includes guidance on setting appropriate sample rates.
  • Sentry Setup (Next.js): Guides users through installation (npm install @sentry/nextjs), wizard execution (npx @sentry/wizard@latest -i nextjs), and configuration of client, server, and edge environments using NEXT_PUBLIC_SENTRY_DSN.
  • Google Analytics Setup (Next.js): Provides instructions for adding the Google Analytics script to the root layout file, utilizing NEXT_PUBLIC_GA_MEASUREMENT_ID, creating event tracking utility functions, and setting up page view tracking.
  • Event Tracking: Supports tracking common events like user signups/logins, purchases, feature usage, and custom business events.

Example prompts

  • "Set up Sentry error tracking for my NestJS application."
  • "Configure Google Analytics on my Next.js frontend."
  • "How do I install the Sentry package in my Next.js project?"
  • “Show me how to track user signups as a custom event.”

Tips & gotchas

  • Use separate DSNs for development and production environments to avoid impacting live data during testing.
  • Be mindful of user privacy regulations (GDPR/CCPA) and avoid tracking sensitive data.
  • The skill integrates with the /monitoring-setup command for automated workflows.