valid_tool

Fetch JSON data from HTTP endpoints using curl-based requests.

40|6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/0xmariowu/Autosearch --skill valid-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: valid_tool
Source: https://github.com/0xmariowu/Autosearch/tree/main/tests/fixtures/skills/valid_tool
Command: npx skills add https://github.com/0xmariowu/Autosearch --skill valid-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reusable HTTP fetch primitive to share common HTTP GET logic across different channels, reducing duplication and increasing consistency.

Core Features & Use Cases

  • Reusable fetch_json primitive
  • Cross-channel data retrieval from HTTP APIs
  • Lightweight and easily integrable into existing workflows

Quick Start

Invoke fetch_json with a target URL to perform a JSON fetch using curl.

Frequently Asked Questions about valid_tool

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

FAQPage Schema
How do I fetch JSON data from an HTTP endpoint using curl?

To fetch JSON data from an HTTP endpoint using curl, you invoke a reusable fetch_json primitive with a target URL. This executes a curl binary request to retrieve lightweight JSON payloads across multiple automation channels.

What is a reusable HTTP fetch primitive for API data retrieval?

A reusable HTTP fetch primitive is a shared tool that centralizes common HTTP GET logic to retrieve JSON data from HTTP APIs. It reduces code duplication and increases consistency across different automation channels.

Do I need curl installed to retrieve JSON from HTTP APIs?

Yes, you need the curl binary installed to retrieve JSON from HTTP APIs. The fetch_json primitive is implemented in Python and requires curl to perform the actual HTTP requests.

What's the best way to share HTTP GET logic across different automation channels?

The best way to share HTTP GET logic across different automation channels is using a reusable fetch_json primitive. It provides a single, lightweight implementation that integrates easily into existing workflows to ensure consistency.

Are there limitations to using a reusable fetch_json primitive for HTTP requests?

A limitation of this reusable fetch_json primitive is that it only performs HTTP GET requests for JSON retrieval and depends on the curl binary. It is designed for lightweight data fetching rather than complex API interactions.