add-portal

Invoke /add-portal with the portal's URL. The workflow interviews you for the market and a test query, investigates the site's search endpoints, scaffolds a search CLI, and verifies it with a live query before registering the skill.

The generated CLI uses plain Bun with fetch and regex parsing, zero runtime dependencies. It exposes search and detail commands with flags like --query, --jobage, --page, and --format, outputting a standard JSON shape with meta and results.

Yes, the generator is country-agnostic and works for any portal in any market or language. The skills it produces are market-specific and stay in your fork, since upstream policy does not merge country-specific portal skills.

The workflow stops for login-walled portals and suggests checking for an official API. If robots.txt or terms restrict access, it tells you plainly; if you proceed for personal use, the generated skill carries a prominent personal-use-only warning.

Markup assumptions from reconnaissance routinely miss quirks that only appear in live responses. The mandatory test run verifies search returns real results and detail returns readable text, iterating on parsers until output is clean.

Yes, when robots.txt permits access but bot protection blocks ordinary fetches. The token is read only from a SERVICE_API_TOKEN environment variable, never hardcoded, and per-call billing is disclosed before scaffolding.