@todoforai/todoregistry-cli

TODO Registry CLI — browse and create templates in the TODO registry (registry.todofor.ai). Read commands are public and need no auth; create requires a token. It never touches user projects — surfacing a template into a project is todoforai-cli recommend's job.

Install

bun add -g @todoforai/todoregistry-cli

Usage

todoregistry-cli search "reddit leads"          # ranked full-text search
todoregistry-cli search seo -c seo -n 5         # restrict to category, limit
todoregistry-cli list [category]                # browse (sorted by starts)
todoregistry-cli get <template-id>              # full template incl. prompt body
todoregistry-cli categories                     # categories with counts

todoregistry-cli create \                       # add a template, prints its id
  --name "Cold email outreach" \
  --description "Draft + send a personalized cold email sequence" \
  --body @prompt.md -c email

• -j/--json for machine-readable output on every command.
• --api-url <url> to point at a different registry backend.
• create auth: --api-key, else the URL-keyed credentials store, else TODOFORAI_API_TOKEN/TODOFORAI_API_KEY. A dst_… session token routes to /dst/v1; a persisted API key routes to /api/v1.

Recommending a template into a project

The registry stays project-agnostic. To surface a template as a reviewable recommendation card, reference it by id with todoforai-cli:

id=$(todoregistry-cli create --name "…" --description "…" --body @prompt.md)
todoforai-cli recommend --template "$id" --project "$PROJECT_ID" --note "why"

The user reviews the card and accepts it to start a real todo (which is when the todofor.ai API's /todos/from-template is used).

Endpoints used

• GET /public/todo-templates[/{id}] — public registry read (no auth)
• POST /{api|dst}/v1/registry/templates — create (auth required)