Profiling Application PerformanceSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: profiling-application-performance
description: 'Execute this skill enables AI assistant to profile application performance,
  analyzing cpu usage, memory consumption, and execution time. it is triggered when
  the user requests performance analysis, bottleneck identification, or optimization
  recommendations. the... Use when optimizing performance. Trigger with phrases like
  ''optimize'', ''performance'', or ''speed up''.

  '
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*)
version: 1.21.0
author: Jeremy Longshore <[email protected]>
license: MIT
tags:
- performance
- profiling-application
compatibility: Designed for Claude Code
---
# Application Profiler

Profile application performance across Node.js, Python, and Java stacks by analyzing CPU usage, memory allocation, and execution hotspots to pinpoint optimization targets.

## Overview

This skill empowers Claude to analyze application performance, pinpoint bottlenecks, and recommend optimizations. By leveraging the application-profiler plugin, it provides insights into CPU usage, memory allocation, and execution time, enabling targeted improvements.

## How It Works

1. **Identify Application Stack**: Determines the application's technology (e.g., Node.js, Python, Java).
2. **Locate Entry Points**: Identifies main application entry points and critical execution paths.
3. **Analyze Performance Metrics**: Examines CPU usage, memory allocation, and execution time to detect bottlenecks.
4. **Generate Profile**: Compiles the analysis into a comprehensive performance profile, highlighting areas for optimization.

## When to Use This Skill

This skill activates when you need to:

- Analyze application performance for bottlenecks.
- Identify CPU-intensive operations and memory leaks.
- Optimize application execution time.

## Examples

### Example 1: Identifying Memory Leaks

User request: "Analyze my Node.js application for memory leaks."

The skill will:

1. Activate the application-profiler plugin.
2. Analyze the application's memory allocation patterns.
3. Generate a profile highlighting potential memory leaks.

### Example 2: Optimizing CPU Usage

User request: "Profile my Python script and find the most CPU-intensive functions."

The skill will:

1. Activate the application-profiler plugin.
2. Analyze the script's CPU usage.
3. Generate a profile identifying the functions consuming the most CPU time.

## Best Practices

- **Code Instrumentation**: Ensure the application code is instrumented for accurate profiling.
- **Realistic Workloads**: Use realistic workloads during profiling to simulate real-world scenarios.
- **Iterative Optimization**: Apply optimizations iteratively and re-profile to measure improvements.

## Integration

This skill can be used in conjunction with code editing plugins to implement the recommended optimizations directly within the application's source code. It can also integrate with monitoring tools to track performance improvements over time.

## Prerequisites

- Appropriate file access permissions
- Required dependencies installed

## Instructions

1. Invoke this skill when the trigger conditions are met
2. Provide necessary context and parameters
3. Review the generated output
4. 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

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.