Skip to content
TrustedSkillsbeta
Back to all skills

Ai Monitoring

Checked
lebsral·vlatest·devops

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

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 lebsral/dspy-programming-not-prompting-lms-skills --skill ai-monitoring -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

lebsral

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 lebsral/dspy-programming-not-prompting-lms-skills at ededb2fbcb.

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

Commit
ededb2fbcb
Manifest
skills/ai-monitoring/SKILL.md
Scanned
6 files, 1,059 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 ai-monitoring skill allows an AI agent to track and report on the performance of other AI agents or systems. It can collect metrics like response time, error rates, and resource utilization. This enables proactive identification of issues and optimization opportunities within AI workflows.

When to use it

  • Debugging slow responses: Identify bottlenecks in a chain of AI tools by monitoring their individual execution times.
  • Detecting errors: Track error rates from specific AI agents to pinpoint failing components.
  • Resource Optimization: Monitor resource usage (e.g., API calls, memory) to identify areas for cost savings or efficiency improvements.
  • Performance Baseline: Establish a baseline of performance metrics to measure the impact of changes and updates.

Key capabilities

  • Metric collection
  • Error rate tracking
  • Response time measurement
  • Resource utilization monitoring

Example prompts

  • "Monitor the response time of the summarization agent."
  • "Track error rates for the translation tool over the last hour."
  • "Report on API call usage by the code generation agent."

Tips & gotchas

The skill requires access to logs or metrics from the AI agents being monitored. Ensure appropriate permissions and logging are configured before deployment.