Skip to content
TrustedSkillsbeta
Back to all skills

Ct Monitor

Listed
tizerluo·vlatest·devops

Continuously monitors cloud infrastructure costs, identifies anomalies, and suggests optimization opportunities via detailed reports.

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 tizerluo/ct-monitor-skill --skill ct-monitor -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

tizerluo

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 4 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.binance.com, api.ctmon.xyz, api.dexscreener.com, web3.binance.com.

    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

    api.ctmon.xyzundeclaredweb3.binance.comundeclaredapi.binance.comundeclaredapi.dexscreener.comundeclared

    What it found (3 of 46)

    • SKILL.md:107contacts api.ctmon.xyz
      curl -s "https://api.ctmon.xyz/api/brief/generate?hours=24" \
    • SKILL.md:114contacts api.ctmon.xyz
      curl -s "https://api.ctmon.xyz/api/price/trending?hours=24" \
    • SKILL.md:120contacts api.ctmon.xyz
      curl -s "https://api.ctmon.xyz/api/signals/recent?hours=6&min_score=60" \

  • 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 tizerluo/ct-monitor-skill at 014bfb6513.

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

Commit
014bfb6513
Manifest
SKILL.md
Scanned
2 files, 1,355 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 ct-monitor skill provides monitoring capabilities, likely focused on system or application health. It can track metrics and report on their status, allowing users to assess performance and identify potential issues. This includes the ability to receive alerts based on predefined thresholds for monitored parameters.

When to use it

  • Troubleshooting Application Errors: Use ct-monitor to pinpoint the root cause of application slowdowns or errors by tracking relevant metrics.
  • Proactive System Health Checks: Regularly monitor key system resources (CPU, memory, disk I/O) to identify potential bottlenecks before they impact users.
  • Performance Optimization: Track performance indicators over time and use the data to optimize resource allocation and improve overall efficiency.
  • Incident Response: Quickly assess the scope of an incident by leveraging real-time monitoring data to understand affected systems and services.

Key capabilities

  • Metric tracking
  • Status reporting
  • Alerting based on thresholds

Example prompts

  • "Monitor CPU usage for the last 5 minutes."
  • "Show me a graph of memory utilization over the past hour."
  • "Alert me if disk space falls below 10%."

Tips & gotchas

The skill's effectiveness depends on properly configuring which metrics to monitor and setting appropriate threshold values. Ensure you understand the specific system or application being monitored to avoid generating false positives or missing critical issues.