filelu-registerlisted

Automate FileLu.com account registration from just an email address. Use this skill whenever the user wants to sign up for / create / register a FileLu (filelu.com) account, open a FileLu account for an email address, or automate FileLu onboarding — even if they don't say "register" explicitly (e.g. "set me up on FileLu with this email", "open a filelu account for ..."). It drives the browser signup (reCAPTCHA forces a real browser), generates FileLu-legal credentials, saves them to YAML, and hands off to the human for the email activation click. When the user also wants to go pure-API afterwards, it optionally logs in once more to capture the API key from the account page.
gdm257/cc-plugins · ★ 0 · Data & Documents · score 60

Install: claude install-skill gdm257/cc-plugins

# filelu-register Register a FileLu.com account from just an email address and save the credentials to YAML — that's the whole job by default. The browser is only needed for the signup form (reCAPTCHA), so the agent fills it, asks the human to solve the captcha and click the activation email, and stops there. Optionally, if the user wants to drive FileLu over its HTTP API afterwards, a second short browser visit logs back in and captures the API key from the account page. ## Why this skill is shaped the way it is FileLu's signup page is protected by **Google reCAPTCHA v2**, so a plain HTTP `POST` to `/register` is rejected — there is no signup API. A real browser (the user's own Chrome via `browser-harness`) is the only path that can render the challenge. The human is already at the machine to click the activation email, so having them solve the captcha in the same window costs nothing and avoids depending on a paid captcha-solving service. The signup is the only step that *must* be a browser visit. If the user later wants the API key (optional), one more login-and-scrape visit captures it; after that every file operation runs over the documented `https://filelu.com/api/*` endpoints with no browser at all. ## Prerequisites - The `browser-harness` skill / CLI must be available. If it isn't installed, stop and tell the user to install it first — this skill cannot work without it. - The user's local Chrome must allow remote debugging. If `browser-harness --doctor` repo