Sync the public integrations page (`public/integrations.html`) with the MCP servers this platform actually exposes. The page is 100% dynamic — it renders whatever `/api/v1/catalogs` returns — so there is nothing per-MCP to edit in the HTML itself. The two committed sources that drive it are `seedDefaultCatalogs()` in `src/mcpCatalogStore.ts` (which MCPs appear) and the `SAMPLE_PROMPTS` map in `src/website/webServer.ts` (the "Sample Prompts" section on each card). This skill diffs the catalog against `SAMPLE_PROMPTS`, adds prompts for any MCP that's missing them (so its card stops showing "Sample prompts coming soon."), and flags catalog/icon gaps. Use whenever the user wants to update, sync, or audit the integrations page after adding or changing an MCP server, or invokes `/update-integrations [slug]`. Chained as a soft follow-up from `add-mcp-server`.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Scanned
boarlabsxyz/awesome-mcp
85cee7a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.