Add a Gearlist entry
Gearlist is a short, source-checked directory. Reading public docs is required. Installing the product is not.
Steps
- Read
AGENTS.md and CONTRIBUTING.md.
- Confirm the official URL with a live fetch. Prefer the vendor site or the canonical GitHub repository.
- Write access notes: account, OAuth scopes, local files, spend, or "none beyond a public clone".
- Add one object to
resources.json with id, name, category, url, description, for_whom, access_notes, source_url, source_checked (today's date), added (today's date), verification, thl_project. Set updated at the top of the file to today's date. When you correct an entry, keep its added date.
- If the same repo is in
stars-queue.json, set that row's status to published or remove it.
- Run
python3 build.py from the repository root and fix any assertion failure.
- Do not paste credentials, chats or client names.
Categories
Use an existing category where it fits: Agent tools, MCP and integrations, Security and governance, Platforms, Protocols, Skills and learning, APIs and data, Hardware, Models.
Hardware and Models entries also carry specs, a list of [label, value] pairs taken from the maker's or provider's own pages. Use the same labels as the other entries in that group, so its page can show one comparison table. Put a date on every price. Leave a value out when the official page does not state it; the table shows "Not stated".
Refuse
Stop if the source is an affiliate dump, has no public documentation, or asks you to install in order to describe it.
1---2name: add-entry3description: Add or correct a Gearlist catalog entry. Use when asked to add a tool, MCP server, skill or platform to this repository, or to promote a row from stars-queue.json.4metadata:5 source: https://skillmd.com/skills/techhorizonlabs/add-entry6 internal: true7---89# Add a Gearlist entry1011Gearlist is a short, source-checked directory. Reading public docs is required. Installing the product is not.1213## Steps14151. Read `AGENTS.md` and `CONTRIBUTING.md`.162. Confirm the official URL with a live fetch. Prefer the vendor site or the canonical GitHub repository.173. Write access notes: account, OAuth scopes, local files, spend, or "none beyond a public clone".184. Add one object to `resources.json` with `id`, `name`, `category`, `url`, `description`, `for_whom`, `access_notes`, `source_url`, `source_checked` (today's date), `added` (today's date), `verification`, `thl_project`. Set `updated` at the top of the file to today's date. When you correct an entry, keep its `added` date.195. If the same repo is in `stars-queue.json`, set that row's `status` to `published` or remove it.206. Run `python3 build.py` from the repository root and fix any assertion failure.217. Do not paste credentials, chats or client names.2223## Categories2425Use an existing category where it fits: Agent tools, MCP and integrations, Security and governance, Platforms, Protocols, Skills and learning, APIs and data, Hardware, Models.2627Hardware and Models entries also carry `specs`, a list of `[label, value]` pairs taken from the maker's or provider's own pages. Use the same labels as the other entries in that group, so its page can show one comparison table. Put a date on every price. Leave a value out when the official page does not state it; the table shows "Not stated".2829## Refuse3031Stop if the source is an affiliate dump, has no public documentation, or asks you to install in order to describe it.