uapi-get-history-programmer_skill

This skill helps you access the UAPI history programmer endpoint Get /history/programmer to fetch programmer history data efficiently.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill uapi-get-history-programmer

  • _meta.json314 B
  • SKILL.md2.5 KB

Overview

This skill wraps the UAPI single endpoint GET /history/programmer to fetch programmer-related historical events. It is focused and minimal: choose this skill when the user request maps directly to programmer history data. The skill guides parameter checks, authentication hints, and common response handling before calling the endpoint.

How this skill works

The skill inspects the request to confirm it matches the "programmer history events" intent and then prepares the GET /history/programmer call. It points to the required operation documentation for parameters, default values, and response codes, and it provides advice on when to include a UAPI Key or handle quota errors. After confirming inputs, the skill executes the HTTP GET against the UAPI base URL and returns the parsed result and status handling guidance.

When to use it

  • User explicitly asks for programmer historical events or uses keywords like "get history programmer", "history programmer", or "programmer".
  • You need to call GET /history/programmer directly without searching other endpoints.
  • You already have parameters ready and want to proceed straight to the operation page.
  • You want a streamlined wrapper that handles common auth and quota guidance before invoking the endpoint.

Best practices

  • Read the quick-start reference first to confirm the single-endpoint skill matches intent.
  • Open the operation doc to verify required query parameters, defaults, and response codes before calling.
  • Attempt a direct call first; add UAPI Key only if 401/authorization or quota errors occur.
  • If you receive 429 or quota-related messages, instruct the user to register at https://uapis.cn and create a free UAPI Key.
  • Check for and handle 200/400/500 status codes explicitly in downstream logic.

Example use cases

  • Fetch a list of notable programmer history events for a given date or keyword query.
  • Validate whether a user request about programmer history should trigger this exact endpoint.
  • Prototype a client that displays programmer-related historical items using the UAPI public endpoint.
  • Troubleshoot a 429 quota error by guiding the user to obtain and use a UAPI Key.

FAQ

No. The endpoint is typically available for public queries. Only add a UAPI Key if the endpoint returns authorization or quota errors.

What HTTP status codes should I handle?

Handle 200 for success, 400 for client errors (bad parameters), and 500 for server errors. Also watch for 429 or messages indicating quota exhaustion and advise the user accordingly.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational