reqwest-client

Implement a reusable reqwest HTTP client with configurable timeouts and headers.

Updated May 10, 2026
One-click install
npx skills add https://github.com/jymchng/injectable --skill reqwest-client
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reqwest-client
Source: https://github.com/jymchng/injectable/tree/main/skills/reqwest-client
Command: npx skills add https://github.com/jymchng/injectable --skill reqwest-client

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires reqwest, and includes scripts (resource) components.

What problem does it solve?

The reqwest-client skill addresses the challenge of managing multiple HTTP requests across services by encapsulating a reusable reqwest client, ensuring standardized configurations and timeouts.

Core Features & Use Cases

  • Reusable HTTP Client: Provides a shared reqwest client for all services, ensuring consistent timeout, user-agent, and headers.
  • Configurable Factories: Allows for dynamic configuration of the HTTP client, such as using environment variables for timeout settings.
  • Shared Client via DynProvider: Offers flexibility to use a single client instance across different services.

Quick Start

Instantiate a WeatherService and utilize its get_weather method to fetch weather data by providing latitude and longitude.

Frequently Asked Questions about reqwest-client

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

FAQPage Schema
How do I reuse an HTTP client across multiple services for consistent network requests?

You can reuse an HTTP client across services by encapsulating a shared reqwest instance, ensuring standardized configurations like consistent timeouts, user-agent strings, and headers for all network requests.

What is the best way to manage reqwest client configurations for service communication?

Managing reqwest client configurations is best handled through configurable factories that dynamically set up the HTTP client, such as using environment variables to define timeout settings for service communication.

Can I use a single reqwest client instance for both synchronous and asynchronous requests?

Yes, the reusable reqwest client supports both synchronous and asynchronous configurations, allowing a single shared client instance to handle diverse network request flows within a service ecosystem.

How do I fetch data using a shared HTTP client in a service ecosystem?

You fetch data by instantiating a service like WeatherService and calling its methods, such as get_weather with latitude and longitude, which utilizes the underlying shared HTTP client.

Why do my HTTP requests have inconsistent timeouts across different services?

Inconsistent timeouts occur when services instantiate separate clients; using a shared reqwest client via a provider like DynProvider standardizes timeout settings across the entire service ecosystem.

Does dependency injection work with a reqwest client for service communication?

Yes, dependency injection is supported by sharing a single reqwest client instance across different services through a DynProvider, offering flexible and consistent service communication.