skills.rest
jlwaugh
jlwaughCOMMUNITY
Explore all skills by this author →
𝕏@jwaupGitHub

api-debug

Test NearBlocks API endpoints for functionality, performance, and rate limiting.

Updated Jan 28, 2026
Search Tags:#testing#performance#api#debug#curl#nearblocks
One-click install
npx skills add https://github.com/jlwaugh/legion-social --skill api-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-debug
Source: https://github.com/jlwaugh/legion-social/tree/main/.claude/skills/api-debug
Command: npx skills add https://github.com/jlwaugh/legion-social --skill api-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and testers quickly diagnose issues with the NearBlocks API by providing automated testing for key endpoints and response characteristics.

Core Features & Use Cases

  • Endpoint Testing: Verifies the functionality of API endpoints like holders and health.
  • Performance Monitoring: Measures response times and checks for rate limiting.
  • Error Scenario Handling: Identifies and reports common API errors (e.g., 404, 429, 500).
  • Use Case: When the NearBlocks NFT marketplace is slow or unresponsive, use this Skill to pinpoint whether the issue lies with the API's performance, rate limits, or specific endpoint failures.

Quick Start

Run the api-debug skill to test the holders endpoint.

Frequently Asked Questions about api-debug

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

FAQPage Schema
How do I test NearBlocks API endpoints for functionality and errors?▼

Test NearBlocks API endpoints by executing curl commands to verify endpoint functionality and identify common API errors like 404, 429, and 500. This automated testing checks API health and NFT holders data retrieval.

How do I check NearBlocks API rate limits and performance?▼

Check NearBlocks API rate limits and performance by measuring response times and performing parallel requests for multiple contracts. This identifies rate limit issues and benchmarks API response characteristics.

Why is my NearBlocks NFT marketplace slow or unresponsive?▼

A slow NearBlocks NFT marketplace can be diagnosed by testing the API's performance, rate limits, and specific endpoint failures. Pinpoint whether the issue lies with API health or NFT holders data retrieval delays.

Can I perform parallel API requests for multiple NearBlocks contracts?▼

Yes, you can perform parallel API requests for multiple NearBlocks contracts using curl commands. This tests API functionality under concurrent load and helps identify rate limiting issues across different contracts.

What common API errors should I look for when debugging NearBlocks?▼

When debugging NearBlocks API, look for common HTTP errors including 404 for not found endpoints, 429 for rate limiting issues, and 500 for server errors. Error scenario handling identifies and reports these failures.

Does api-debug require any external dependencies to test NearBlocks?▼

No, api-debug has no external dependencies. It uses standard curl commands to test NearBlocks API endpoints, making it easy to run without installing additional packages or configuring complex testing environments.

Related Skills

Explore More Software Engineering Skills→
mkusakamkusaka
7

verify-serverapi-changes-example-for-verify-skill

Executes predefined request sequences to validate server/API changes after deployment.

Community
Intermediate
abzhawabzhaw

system-monitoring

Aggregate process, disk, memory, and observability metrics for Julia's macOS server health.

Community
Intermediate
Camilo8902Camilo8902

backend-latency-profiler-helper

Analyze API logs to detect slow endpoints and outline performance fixes.

Community
Intermediate
jc180105jc180105

API Tester

Automate API testing across functional, performance, and security domains.

Community
Advanced