skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
robot-inventor/agent-skills73 installs

prove-it-diagnostics

Prove it for debugging, performance investigation, bottleneck analysis, profiling, and optimization work.

How do I install this agent skill?

npx skills add https://github.com/robot-inventor/agent-skills --skill prove-it-diagnostics
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides a framework for debugging and performance optimization by instructing the AI to read, write, and execute code to verify root causes. While these capabilities involve processing untrusted project data and generating scripts, they are the core intended functions of a diagnostic tool and do not involve malicious patterns.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Prove It Diagnostics

Use this skill to pinpoint the causes of bugs and performance bottlenecks and fix them. Reading code alone may not reveal the source of a bug or bottleneck. Do not claim that a speculative code change fixed a bug or improved performance. Run the code, gather evidence, identify the cause, and verify the fix.

Steps

1. Establish a performance baseline for optimization tasks

For performance optimization tasks, create and run a benchmark before making changes. Run the benchmark as many times as practical. Use averages, percentiles, and other relevant statistics to establish a stable baseline.

2. Read the code

Read the code related to the bug or performance issue. For debugging tasks, you may fix the issue and skip the remaining steps when you find a clear cause, such as an incorrect operator or an obvious contradiction in the logic.

Continue with the remaining steps when you cannot identify the cause with confidence or when you find suspicious code but lack enough evidence to blame it.

3. Verify the cause

Run experiments to identify the source of the bug or bottleneck. For debugging tasks:

  1. Create a reproduction in a temporary file or REPL and run it to confirm the bug. If the reproduction does not fail, add relevant behavior from the target code until it reproduces the bug.
  2. Remove each part of the reproduction to find the smallest program that still triggers the bug.
  3. Investigate the minimal reproduction, identify the cause, and fix it. Address the root cause instead of applying a superficial workaround, as described in the Rules section.
  4. Confirm that the fix prevents the bug in the minimal reproduction.
  5. Apply the fix to the production code and confirm that it resolves the original bug. If the bug remains, return to the reproduction step and repeat the process.

For performance optimization tasks:

  1. Use benchmarks, profilers, timing logs, or similar tools to identify the slow operation.
  2. Fix the bottleneck, then use the same measurements to confirm that performance improved.
  3. If performance does not improve, return to bottleneck analysis and repeat the process.

4. Clean up

Remove temporary logs, reproduction code, generated files, and log data created during verification.

Rules

If a user reports that your fix did not resolve the bug or improve performance, treat your previous diagnosis as unverified and restart the investigation.

Surface-level and stop-gap fixes are shameful; identify and fix the root cause. For example, when an error triggers a bug, find and fix the source of the error instead of adding a fallback for the failure. Keep asking yourself, “Is this the root cause?”

When evidence points to a bug in a dependency, do not patch the dependency. Tell the user that the dependency appears to contain a bug, describe the evidence, and propose changes they can make in their project without modifying the dependency.

When you get stuck, try these approaches:

  • Add temporary logs across the affected path. Use them to find the boundary between correct and incorrect behavior, or between fast and slow execution.
  • When behavior contradicts the code or you cannot make progress, search the relevant library’s GitHub issues and pull requests, and community articles for reports of the same problem.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/robot-inventor/agent-skills/prove-it-diagnostics">View prove-it-diagnostics on skillZs</a>