Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications.
Install Monitoring Cpu Usage
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-cpu-usage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/monitoring-cpu-usage .claude/skills/monitoring-cpu-usage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "monitoring-cpu-usage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usage into .claude/skills/monitoring-cpu-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-cpu-usage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-cpu-usage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/monitoring-cpu-usage .agents/skills/monitoring-cpu-usage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "monitoring-cpu-usage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usage into .agents/skills/monitoring-cpu-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-cpu-usage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-cpu-usage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/monitoring-cpu-usage .cursor/skills/monitoring-cpu-usage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "monitoring-cpu-usage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usage into .cursor/skills/monitoring-cpu-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-cpu-usage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/monitoring-cpu-usage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-cpu-usage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/monitoring-cpu-usage .gemini/skills/monitoring-cpu-usage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "monitoring-cpu-usage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usage into .gemini/skills/monitoring-cpu-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-cpu-usage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-cpu-usageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/monitoring-cpu-usage .github/skills/monitoring-cpu-usage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "monitoring-cpu-usage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usage into .github/skills/monitoring-cpu-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-cpu-usage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-cpu-usage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/monitoring-cpu-usage .opencode/skills/monitoring-cpu-usage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "monitoring-cpu-usage" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/monitoring-cpu-usage into .opencode/skills/monitoring-cpu-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-cpu-usage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
monitoring-cpu-usage- GitHub stars
- 2.8k
- Token cost
- ~957 tokens
- SKILL.md length
- 401 words
- Files
- 6 (incl. scripts, references, assets)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications.
- Works in 3 steps: Initiate CPU Monitoring: Claude… → Code Analysis: The plugin analyzes the… → Optimization Recommendations: Claude…
- The user asks to monitor cpu usage
- SKILL.md covers Overview, How It Works, When to Use This Skill and Examples, plus 7 more sections
- Runs Python scripts from its folder
What it does
Monitoring Cpu Usage is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications. it helps identify cpu hotspots, analyze algorithmic complexity, and detect blocking operations. use this skill when the user asks to "monitor cpu usage", "opt... Use when setting up monitoring or observability. Trigger with phrases like 'monitor', 'metrics', or 'alerts'.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Observability. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- The user asks to monitor cpu usage
- Setting up monitoring
- With phrases like monitor
Example prompts
- “monitor cpu usage”
- “monitor”
- “metrics”
- “/monitoring-cpu-usage”
Requirements
- Python 3
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(cmd:*)
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Initiate CPU Monitoring: Claude activates the cpu-usage-monitor plugin.
- Code Analysis: The plugin analyzes the codebase for computationally expensive operations, synchronous blocking calls, inefficient loops…
- Optimization Recommendations: Claude provides a detailed report outlining areas for optimization, including suggestions for algorithmic…
What it can do on your machine
Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepGlobBash(cmd:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Monitoring Cpu Usage loads about 957 tokens when it runs, and up to ~972 if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 401 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 401 words, ~957 tokens.
Download SKILL.mdSave it as
.claude/skills/monitoring-cpu-usage/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- monitoring-cpu-usage
- description
- Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications. it helps identify cpu hotspots, analyze algorithmic complexity, and detect blocking operations. use this skill when the user asks to "monitor cpu usage", "opt... Use when setting up monitoring or observability. Trigger with phrases like 'monitor', 'metrics', or 'alerts'.
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash(cmd:*)
- compatibility
- Designed for Claude Code
- version
- 1.23.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- performance, monitoring, observability
Cpu Usage Monitor
Identify CPU hotspots, analyze algorithmic complexity, and detect blocking operations in application code with targeted optimization recommendations.
Overview
This skill empowers Claude to analyze code for CPU-intensive operations, offering detailed optimization recommendations to improve processor utilization. By pinpointing areas of high CPU usage, it facilitates targeted improvements for enhanced application performance.
How It Works
- Initiate CPU Monitoring: Claude activates the
cpu-usage-monitorplugin. - Code Analysis: The plugin analyzes the codebase for computationally expensive operations, synchronous blocking calls, inefficient loops, and regex patterns.
- Optimization Recommendations: Claude provides a detailed report outlining areas for optimization, including suggestions for algorithmic improvements, asynchronous processing, and regex optimization.
When to Use This Skill
This skill activates when you need to:
- Identify CPU bottlenecks in your application.
- Optimize application performance by reducing CPU load.
- Analyze code for computationally intensive operations.
Examples
Example 1: Identifying CPU Hotspots
User request: "Monitor CPU usage in my Python script and suggest optimizations."
The skill will:
- Analyze the provided Python script for CPU-intensive functions.
- Identify potential bottlenecks such as inefficient loops or complex regex patterns.
- Provide recommendations for optimizing the code, such as using more efficient algorithms or asynchronous operations.
Example 2: Analyzing Algorithmic Complexity
User request: "Analyze the CPU load of this Java code and identify areas with high algorithmic complexity."
The skill will:
- Analyze the provided Java code, focusing on algorithmic complexity (e.g., O(n^2) or worse).
- Pinpoint specific methods or sections of code with high complexity.
- Suggest alternative algorithms or data structures to improve performance.
Show full SKILL.md (144 more words)Show less
Best Practices
- Targeted Analysis: Focus the analysis on specific sections of code known to be CPU-intensive.
- Asynchronous Operations: Consider using asynchronous operations to prevent blocking the main thread.
- Regex Optimization: Carefully review and optimize regular expressions for performance.
Integration
This skill can be used in conjunction with other code analysis and refactoring tools to implement the suggested optimizations. It can also be integrated into CI/CD pipelines to automatically monitor CPU usage and identify performance regressions.
Prerequisites
- Appropriate file access permissions
- Required dependencies installed
Instructions
- Invoke this skill when the trigger conditions are met
- Provide necessary context and parameters
- Review the generated output
- Apply modifications as needed
Output
The skill produces structured output relevant to the task.
Error Handling
- Invalid input: Prompts for correction
- Missing dependencies: Lists required components
- Permission errors: Suggests remediation steps
Resources
- Project documentation
- Related skills and commands
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references, assets) in skills/.curated/monitoring-cpu-usage of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- assets/README.md
- references/README.md
- scripts/README.md
- scripts/cpu_analyzer.py
- scripts/example_usage.py
Open the folder on GitHubat commit 80f86df
Compare with similar skills
Monitoring Cpu Usage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Monitoring Cpu Usage this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~957 | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Monitoring Cpu Usage
What does Monitoring Cpu Usage do?
Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications. Monitoring Cpu Usage is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor this skill enables AI assistant to monitor and analyze cpu usage patterns within applications.
When should I use Monitoring Cpu Usage?
Monitoring Cpu Usage fits situations like: the user asks to monitor cpu usage; setting up monitoring; with phrases like monitor.
How do I install Monitoring Cpu Usage in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a claude-code`. Or copy the skill folder (skills/.curated/monitoring-cpu-usage in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/monitoring-cpu-usage in your project. Claude Code loads it when a task matches its description.
How do I install Monitoring Cpu Usage in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a codex`. Or copy the skill folder (skills/.curated/monitoring-cpu-usage in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/monitoring-cpu-usage in your project. Codex loads it when a task matches its description.
Can I use Monitoring Cpu Usage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-cpu-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitoring-cpu-usage, .gemini/skills/monitoring-cpu-usage, .github/skills/monitoring-cpu-usage and .opencode/skills/monitoring-cpu-usage in your project.
What does Monitoring Cpu Usage need to run?
Going by SKILL.md and its folder, Monitoring Cpu Usage needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Monitoring Cpu Usage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Monitoring Cpu Usage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Monitoring Cpu Usage use?
Monitoring Cpu Usage is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Monitoring Cpu Usage use?
About 957 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15 tokens, read only when the agent opens those files.
What are the alternatives to Monitoring Cpu Usage?
Skills that share tags, products or a category with Monitoring Cpu Usage: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Monitoring Cpu Usage?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.