performance

Profile code and record baseline metrics to identify performance bottlenecks.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/micaelmalta/agentic --skill performance-micaelmalta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance
Source: https://github.com/micaelmalta/agentic/tree/main/skills/performance
Command: npx skills add https://github.com/micaelmalta/agentic --skill performance-micaelmalta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams identify and fix performance issues by guiding you through profiling, bottleneck analysis, and targeted optimization, while emphasizing measurable improvements through observability.

Core Features & Use Cases

  • Profile and benchmark across languages to locate hot paths, high-latency calls, and memory-heavy operations.
  • Identify bottlenecks and guide optimizations focused on the most impactful areas.
  • Add observability through structured logging, metrics, and tracing to monitor production performance and diagnose regressions.
  • Use Case: Profile a slow API endpoint, optimize the critical path, and validate improvements with repeatable measurements.

Quick Start

Use the performance skill to profile a running service, identify a bottleneck, and implement a measurable optimization, then verify improvements with updated metrics.

Frequently Asked Questions about performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify performance bottlenecks and reduce latency in a slow API endpoint?

You can identify performance bottlenecks by profiling code to locate hot paths and slow queries, then applying targeted optimizations. Adding observability through structured logging, metrics, and tracing helps monitor production performance and diagnose regressions.

What is the best way to profile code and record baseline metrics across different languages?

Profiling code across languages requires accessing profiling tools to locate memory-heavy operations and blocking I/O. You record baseline metrics before optimizing to ensure measurable improvements without changing program semantics.

How do I add observability and tracing to a service without changing program semantics?

You add observability by instrumenting code with structured logging, metrics, and tracing to monitor production performance. This instrumentation must be added carefully to gather diagnostic data without altering program semantics.

Can I use this profiling approach for batch jobs and web apps, or is it limited to specific services?

This profiling approach applies to web apps, batch jobs, and services across multiple languages. It is used whenever you need to identify hot paths, slow queries, or blocking I/O within those diverse application contexts.

Do I need specific profiling tools to find slow queries and blocking I/O in my application?

Yes, identifying slow queries and blocking I/O requires access to dedicated profiling tools. These tools are necessary to benchmark operations, locate memory-heavy calls, and establish the baseline metrics needed for optimization.