Submit an agent-friendly tool

Tool name
Website URL
Submitter
Agent-readiness notes
Opens a prefilled PR composer for branch catalog/add-new-tool.
Copies a ready prompt for an agent to research, edit the catalog, run checks, and open the PR.
Agent prompt preview
Please add a new agent-friendly tool to https://github.com/phuctm97/canagentsuse and open a pull request.

Tool request:
- Name: Not provided
- Website: Not provided
- Submitter: Not provided
- Notes: Not provided

If the tool name or website URL is missing, ask me for it before editing files. If optional fields are missing, research them from official public sources.

Repository workflow:
1. Create a branch named `catalog/add-new-tool`.
2. Read `data/README.md`, `data/catalog.schema.json`, and nearby records in `data/catalog.json` before editing.
3. Edit `data/catalog.json` only, unless the repo clearly requires a small docs update for the submission flow.
4. Add or update exactly one tool record with a stable unique `slug`, `name`, `tagline`, `websiteUrl`, `docsUrl`, `githubUrl`, `shortDescription`, `agentSummary`, `bestFor`, `cautionNotes`, `pricingSummary`, `authModel`, `accountCreation`, `browserSupport`, `cliPackage`, `apiBaseUrl`, `mcpServer`, `agentScore`, `launchScore`, `categorySlugs`, `useCaseSlugs`, and `capabilities`.
5. Use existing category, use-case, and capability slugs where possible. Do not invent new slugs unless the catalog schema/data already supports them or the new slug is truly required.
6. For each capability, use support level `native`, `strong`, `partial`, `manual`, or `unknown`; include a concrete detail and an official/public evidence URL when available.
7. Prefer official docs, product docs, GitHub repos, package registries, pricing pages, and auth/setup docs as evidence. Avoid marketing-only or unsourced claims.
8. Score conservatively from evidence: machine operability, agent safety, agent readability, auth/setup, and production reliability. Add caution notes for money, production data, accounts, compliance, infrastructure, browser-only flows, or brittle automation.
9. Do not add secrets, database credentials, Docker/Neon setup, generated build output, or unrelated refactors.
10. Run `bun run catalog:audit`, `bun run build`, and `git diff --check`.
11. Commit the change and push the branch before opening the PR. GitHub's prefilled PR composer requires the head branch to exist.
12. Open a PR to `main` in `phuctm97/canagentsuse` using `.github/PULL_REQUEST_TEMPLATE/add-tool.md`.

Use this PR body exactly, filling any remaining blank fields with researched evidence or `Not applicable`:

## Tool

- Name:
- Website:
- Stable slug:
- Submitted by:

## Catalog Fields

- `slug`:
- `name`:
- `tagline`:
- `websiteUrl`:
- `docsUrl`:
- `githubUrl`:
- `shortDescription`:
- `agentSummary`:
- `bestFor`:
- `cautionNotes`:
- `pricingSummary`:
- `authModel`:
- `accountCreation`:
- `browserSupport`:
- `cliPackage`:
- `apiBaseUrl`:
- `mcpServer`:
- `agentScore` (0-100):
- `launchScore` (0+):
- `categorySlugs`:
- `useCaseSlugs`:

## Agent Capability Evidence

For each capability, include support level (`native`, `strong`, `partial`, `manual`, or `unknown`), a short detail, and a public evidence URL when available.

- CLI:
- API:
- MCP:
- Browser:
- Account creation:
- Pricing clarity:
- Docs quality:
- Sandbox:

## Official Evidence

- Product or homepage:
- Docs home:
- API docs:
- CLI docs:
- MCP server docs:
- Pricing page:
- Sandbox, test-mode, or local-mode docs:
- Account setup or auth docs:
- GitHub or package registry:

## Submitter Notes

Not provided

## PR Checklist

- [ ] Added or updated exactly one tool record in `data/catalog.json`
- [ ] Used a stable unique slug and existing category/use-case/capability slugs where possible
- [ ] Filled required fields from `data/catalog.schema.json`
- [ ] Added evidence URLs for important API, CLI, MCP, docs, pricing, sandbox, browser, and account setup claims
- [ ] Included limitation/caution notes for money, production data, infrastructure, compliance, user accounts, browser-only flows, or brittle automation
- [ ] Did not add secrets, database credentials, Docker/Neon setup, generated build output, or unrelated files

## Validation

- [ ] `bun run catalog:audit`
- [ ] `bun run build`
- [ ] `git diff --check`