Two skills in one plugin: one gets Claude authenticated access to an API stuck behind OAuth, the other turns a browser workflow with no API into a script you can re-run. These are meta-skills: Teach your AI how to create the workarounds for your specific skills and automations.
Built by the team that ran 20+ brands with three people.
It is a Claude Code plugin with two independent skills. Platform-connector sends Claude's request through a Make.com scenario you own, which authenticates to the real API and hands the answer back; so you don't have to maintain the API connections, Make's platform does it for you. Browser-automation drives the page with the Claude-in-Chrome tools and writes the steps out as a script you can re-run; for cases when connecting a platform via API is not an option.
Two skills in one plugin: one gets Claude authenticated access to an API stuck behind OAuth, the other turns a browser workflow with no API into a script you can re-run. These are meta-skills: Teach your AI how to create the workarounds for your specific skills and automations.
A real sample of the output sits here, so you see the result before you take it.
Platform-connector creates a Make.com connector you control, but don't have to maintain.
Browser-automation hands you the artifact, not a one-off result, so the job runs again next week.
The tool with no API, or one behind an OAuth wall, stops being a dead end.
You get both skills. platform-connector needs a Make.com account you own (free version is enough); browser-automation needs the Claude-in-Chrome tools. Set up only the one the job needs.
Tell it which tool you are stuck on and what you need from it.
If the platform has an API behind OAuth (Meta, Microsoft, etc.), platform-connector proxies it. If it has no usable API, browser-automation hands you a re-runnable script. Either way you get repeatable access. These then can become part of your everyday AI-driven workflows that your agents use seamlessly.
Claude Code, and then it depends which of the two skills you use. Platform-connector needs a Make.com account you own (but the free version is enough for normal use). Browser-automation needs the Claude-in-Chrome tools. Set up only the one the job needs.
Microsoft Graph and Meta are built out end to end, and there is a documented pattern for adding your own provider. If Make.com can authenticate to it, platform-connector can reach it. If the platform has no usable API at all, browser-automation is the path instead.
Yes. The free tools are yours to use in your own work. Software products are MIT-licensed.
No. There is no form on this page. You can subscribe if you want the new tools as they land, but the download never asks.
It does not break anything that is deliberately locked: it works through access you already have, not around it. And a browser script depends on the page it was built against, so a redesign at the other end will break it and it will need rebuilding.
Two skills in one plugin: one gets Claude authenticated access to an API stuck behind OAuth, the other turns a browser workflow with no API into a script you can re-run. These are meta-skills: Teach your AI how to create the workarounds for your specific skills and automations.
Download it freeNo email required.
×
Newsletter
You don't have to. But if you want the new tools and playbooks as we ship them, join the newsletter.
