api-auditor

Audit API endpoints with HEAD requests and explain failures in plain English.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill api-auditor-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-auditor
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/api-auditor
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill api-auditor-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Auditing and testing API endpoints for reliability and correctness. It helps you quickly identify status codes, latency, and failures.

Core Features & Use Cases

  • Audit: Use the bundled audit.js to check the status of the provided URL.
  • Report: Analyze the output (status codes, latency) and explain any failures in plain English.
  • Secure: Remind the user if they are testing a sensitive endpoint without an https:// protocol.

Quick Start

Provide the URL you want to audit and the AI will run a HEAD request to verify its status and report results.

Frequently Asked Questions about api-auditor

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

FAQPage Schema
How do I test API endpoint health and latency?

Test API endpoint health and latency by providing a URL to run a HEAD request. The script verifies status codes and reports latency, explaining any failures in plain English.

What does a HEAD request check for during an API audit?

A HEAD request checks API status codes and latency without downloading the response body. The audit script uses this method to verify endpoint reliability and analyze failures.

Can I audit an HTTP endpoint or do I need HTTPS?

You can audit HTTP endpoints, but the script provides an HTTPS reminder. It warns you if you are testing a sensitive endpoint without the https:// protocol to ensure secure connections.

What is the best way to get a plain-English explanation for API failures?

Get plain-English API failure explanations by running the bundled audit script. It analyzes status codes and latency from the HEAD request output to explain endpoint issues clearly.

Do I need any dependencies to run an API status code check?

No dependencies are required to run the API status code check. The Skill uses a bundled scripts component to perform the audit directly without installing external packages.