36Kr 24-Hour Hot List

Problem to Solve

When writing technical posts, tracking industry signals, or doing competitive research, engineers often need a fast way to see which 36Kr stories made the day's hot list without manually browsing the site. 36kr-media-hotlist turns that lookup into a structured JSON request: fetch the 24-hour list by date and extract stable fields such as title, author, summary, publish time, and article URL. It fits workflows that need repeatable, scriptable, and agent-friendly output.

How It Works

The skill's core capability is calling the 36Kr hot-list endpoint and normalizing the response. The typical flow has four steps:
- Resolve the date: use today if the user does not provide one, in YYYY-MM-DD format.
- Request the list: build the 24h_hot_list.json URL and send a GET request without extra authentication.
- Parse the payload: read fields from the data array, including rank, title, author, authorUrl, publishTime, content, and url.
- Render the result: output an information stream sorted by rank, with clickable title and author links; omit the summary if content is empty or looks like a numeric ID.

Boundaries

This skill is best for querying one date at a time, with up to 15 entries per day. Historical dates are supported, but same-day data may not exist yet and can return 404 or NoSuchKey. In some early records, content may be an article ID rather than a real summary, so it should not be treated as full article text.