How do I install the Opentrends skill?

Run npx skillmds@latest add tomevault-io/opentrends in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Opentrends safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Opentrends?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Opentrends free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Opentrends?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Opentrends by tomevault-io — Agent Skill

Name: Opentrends
Author: tomevault-io

Opentrends

Read structured trend data from the public OpenTrends API. Use when users ask about OpenTrends, current trends, AI trends, programming trends, hardware trends, biotech trends, embodied AI trends, or China tech trends. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

OpenTrends API Reader

Use OpenTrends as a structured API data source. Do not scrape the human-facing website.

Update Check

Before each OpenTrends task, fetch the current skill/API manifest:

GET https://api.opentrends.io/api/skills/opentrends

Use the returned baseUrl, topics, endpoints, and query parameter contract as the source of truth. If the manifest conflicts with this local Markdown file, follow the manifest.

If the manifest request fails, continue with the defaults in this file and tell the user that the latest OpenTrends skill manifest could not be checked.

Defaults

Base URL: https://api.opentrends.io
Topic endpoint: GET /api/trends/:topic
Source endpoint: GET /api/trends/:topic/sources/:sourceId
Summary endpoint: GET /api/trends/:topic/summary
Sources endpoint: GET /api/sources

Supported topics:

ai
programming
hardware
biotech
embodied
cn

Useful query parameters:

lang=zh | en | zh-Hant | ru
items=preview | number
translations=background | sync

Workflow

Map the user's request to a topic. If unclear, ask which topic they want or default to ai for general AI trend requests.
Fetch the manifest.

Request structured JSON from the API host, for example:

GET https://api.opentrends.io/api/trends/ai?lang=zh&items=preview

For one source, use /api/trends/:topic/sources/:sourceId.
For an overall generated summary, use /api/trends/:topic/summary, then use the topic JSON as citation/link context.
If the API returns topic_not_found, 404, or parameter errors, fetch the manifest again and retry once with the latest contract.

Response Rules

Summarize only from API JSON or API summary output.
Preserve source links from item url fields.
Include source names, item titles, and dates when available.
If a source or topic is empty, unavailable, or stale, say so directly.
Do not invent trends, source names, dates, or links.
Do not call https://opentrends.io/api/....
Do not scrape https://opentrends.io/... trend pages.

Source: nexmoe/opentrends — distributed by TomeVault.

---name: opentrendsdescription: Read structured trend data from the public OpenTrends API. Use when users ask about OpenTrends, current trends, AI trends, programming trends, hardware trends, biotech trends, embodied AI trends, or China tech trends. Use when this capability is needed.---# OpenTrends API ReaderUse OpenTrends as a structured API data source. Do not scrape the human-facingwebsite.## Update CheckBefore each OpenTrends task, fetch the current skill/API manifest:```txtGET https://api.opentrends.io/api/skills/opentrends```Use the returned `baseUrl`, `topics`, `endpoints`, and query parameter contractas the source of truth. If the manifest conflicts with this local Markdown file,follow the manifest.If the manifest request fails, continue with the defaults in this file and tellthe user that the latest OpenTrends skill manifest could not be checked.## Defaults```txtBase URL: https://api.opentrends.ioTopic endpoint: GET /api/trends/:topicSource endpoint: GET /api/trends/:topic/sources/:sourceIdSummary endpoint: GET /api/trends/:topic/summarySources endpoint: GET /api/sources```Supported topics:```txtaiprogramminghardwarebiotechembodiedcn```Useful query parameters:```txtlang=zh | en | zh-Hant | ruitems=preview | numbertranslations=background | sync```## Workflow1. Map the user's request to a topic. If unclear, ask which topic they want or default to `ai` for general AI trend requests.2. Fetch the manifest.3. Request structured JSON from the API host, for example: ```txt GET https://api.opentrends.io/api/trends/ai?lang=zh&items=preview ```4. For one source, use `/api/trends/:topic/sources/:sourceId`.5. For an overall generated summary, use `/api/trends/:topic/summary`, then use the topic JSON as citation/link context.6. If the API returns `topic_not_found`, `404`, or parameter errors, fetch the manifest again and retry once with the latest contract.## Response Rules- Summarize only from API JSON or API summary output.- Preserve source links from item `url` fields.- Include source names, item titles, and dates when available.- If a source or topic is empty, unavailable, or stale, say so directly.- Do not invent trends, source names, dates, or links.- Do not call `https://opentrends.io/api/...`.- Do not scrape `https://opentrends.io/...` trend pages.---> Source: [nexmoe/opentrends](https://github.com/nexmoe/opentrends) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions