golem-http-params-ts

Map HTTP request elements to strongly typed TypeScript agent parameters and responses.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-http-params-ts-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-http-params-ts
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-http-params-ts
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-http-params-ts-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes guesswork when wiring HTTP endpoints to agent method signatures by clearly defining how URL parts, headers, and JSON bodies become strongly-typed TypeScript parameters and responses.

Core Features & Use Cases

  • Path variable mapping: Maps {varName} segments in mount and endpoint paths into constructor and method parameters, including last-segment catch-all behavior.
  • Query and header mapping: Supports ?key={var} syntax for query parameters and headers: { ... } for header-to-parameter binding, including optional (T | undefined) and repeated (Array<T>) forms for query/header only.
  • Body and return type mapping: Defines how unmapped parameters become a JSON request-object body and how void, undefined, Result, UnstructuredBinary, and UnstructuredText map to HTTP status codes and response content types.
  • Type safety rules: Restricts which TypeScript types are allowed for path/query/header parameters versus body parameters, preventing invalid runtime parsing.

Quick Start

Ask for the correct parameter and return type mapping rules for a specific HTTP endpoint in your TypeScript agent, including how to bind path variables, query params, headers, and request bodies.

Frequently Asked Questions about golem-http-params-ts

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

FAQPage Schema
How do I map HTTP request elements to TypeScript agent method parameters?

HTTP request elements are mapped to strongly-typed TypeScript agent parameters by binding URL path segments to constructor and method arguments, using query syntax for URL parameters, and assigning unmapped parameters to the JSON request body.

How does HTTP path variable mapping work for TypeScript agent endpoints?

Path variable mapping extracts `{varName}` segments from mount and endpoint paths and binds them to TypeScript agent parameters, supporting last-segment catch-all behavior to capture remaining URL path components dynamically.

How do I handle optional and repeated query parameters in TypeScript HTTP endpoints?

Optional and repeated query parameters are handled using `?key={var}` syntax for binding, where optional forms accept `T | undefined` types and repeated forms accept `Array<T>` types specifically for query and header parameter wrappers.

How are HTTP response status codes and content types determined from TypeScript return types?

HTTP response status codes and content types are determined by mapping TypeScript return types, where `void` and `undefined` yield specific status codes, while `UnstructuredBinary` and `UnstructuredText` enforce strict content-type rules for response serialization.

What TypeScript types are allowed for path and query parameters versus JSON body parameters?

Type safety rules restrict path, query, and header parameters to primitive TypeScript types suitable for URL parsing, while complex object types are reserved exclusively for JSON body parameters to prevent invalid runtime parsing.

Can I use binary and text payloads with strict content-type rules in TypeScript HTTP agents?

Binary and text payloads are supported through `UnstructuredBinary` and `UnstructuredText` types, which enforce strict content-type rules for HTTP request parsing and response serialization within TypeScript agent endpoint definitions.