cui-http

Standardize Java HTTP clients with HttpHandler and HttpResult patterns.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill cui-http
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cui-http
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-dev-java-cui/skills/cui-http
Command: npx skills add https://github.com/cuioss/plan-marshall --skill cui-http

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize HTTP client usage across Java projects by providing a reference implementation of HttpHandler, HttpResult pattern, and async-first adapters to ensure consistency, reliability, and safer error handling.

Core Features & Use Cases

  • Async-first adapters with composable retry and caching, including ETag support.
  • HttpResult pattern for type-safe results and exhaustive pattern matching.
  • TLS context management, status classification, and content conversion utilities for robust HTTP interactions.

Quick Start

Review the CUI HTTP standards and start integrating HttpHandler and HttpResult into your Java HTTP client code.

Frequently Asked Questions about cui-http

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

FAQPage Schema
How do I implement async HTTP retries and caching with ETag support in Java?

Standardize HTTP client usage across Java projects by adopting the HttpHandler interface, applying consistent TLS context management and content conversion for robust REST interactions.

Can I use async HTTP adapters for managing secure TLS contexts in Java?

Yes, async-first HTTP adapters support secure TLS context management alongside status classification and content conversion utilities for robust HTTP interactions.

What is the best way to standardize Java HTTP client behavior across multiple projects?

Adopt a reference HttpHandler implementation with HttpResult patterns and async adapters to ensure consistency, reliability, and type-safe error handling across Java projects.

Why does my Java HTTP client lack consistent retry and caching semantics?

Without composable HTTP adapters like ResilientHttpAdapter and ETagAwareHttpAdapter, Java clients lack standardized retry, caching, and type-safe error handling across REST calls.