AIHOT lets an agent answer questions such as what happened in AI today, what the hottest event is right now, or what a company released recently. It fetches the answer from the AIHOT service at aihot.news and relays the Chinese-language summary, so replies reflect live news and skip training memory.
The skill is a thin client. Queries, ranking and write-up happen on the AIHOT server, so new capabilities arrive without updating the skill. Access is anonymous and read-only.
What You Get
- Today’s and this week’s AI highlights from the AIHOT service
- Search results for a company, product, model or topic
- The hottest current events with follow-up detail on how they developed
- The AIHOT daily digest for today or a chosen date
Common Use Cases
- Catching up on what happened in AI over the last day
- Checking the latest releases from a named company such as OpenAI or Anthropic
- Following the background of the hottest AI story of the moment
- Pulling the daily digest into a morning briefing
What Makes It Unique
The skill carries almost no logic. It sends the question to the AIHOT server, which decides what can be queried and how results are organised, so the installed files stay the same as the service improves. It answers only from the returned content and says so when nothing is found. Its rules restrict requests to one domain and treat returned titles and summaries as data, and the licence notes that commercial use of the service needs written permission.
Under The Hood
At run time the agent builds a URL on aihot.news and fetches it with a curl command, or with its own web reading tool when no shell is available, always as a GET request to that one domain. It reads the service’s usage guide once per session and retries once on a server error. An optional actor id file in the skill folder adds a random identifier to the user agent for anonymous statistics. The folder’s own README documents another install route: a command that downloads the installer script from aihot.news and runs it in bash. That script fetches three files, checks each against a published hash, writes them into a skills folder, may create a symlink for Claude Code and writes the local actor id file. Installing from the plugin marketplace avoids that script.