Agent skill · software engineering · jeremylongshore
remofirst-install-auth
Prepare secure RemoFirst client access with account activation, 2FA, billing contacts, and least-privilege manager groups. Use when onboarding an operator or repairing access without inventing API credentials. Trigger with "RemoFirst access", "RemoFirst 2FA", "RemoFirst roles", or "activate RemoFirst account".
Why this skill is useful
Provides specific API integration patterns and error handling for RemoFirst that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires remofirst account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
RemoFirst Secure Access Readiness Overview Prepare a human-operated RemoFirst account without fabricating an API key, base URL, SDK, or machine credential; the reviewed public contract covers client account activation, password login, optional 2FA, manager groups, and named Workday or ADP connector setup. Treat any custom API access as unavailable until RemoFirst supplies a customer-specific written contract. Prerequisites A RemoFirst welcome invitation for the intended person. The company, team, billing contact, and required operator duties. An approved password manager and 2FA recovery-code storage location. Current Contract Client activation starts from the welcome email and requires a password, acceptance of terms, company review, and at least one billing contact. Client 2FA uses an authenticator application and a one-time recovery code. Manager groups separate PTO, expense, payroll, finance, people, and team-admin duties. Selecting no group defaults the user to Superuser. Public first-party sources do not publish a general RemoFirst API or SDK contract. Do not reuse a generic API-key example. Instructions 1. Record the person, company, team, business duty, approver, and requested duration. Reject a shared login or generic mailbox as the account owner. 2. Activate only from the expected welcome email. Confirm the company record, terms, privacy notice, and billing contact before completing setup. 3. Map duties to the narrowest documented groups. Never leave a user with the implicit Superuser default merely because the group selection was skipped. 4. Enable 2FA from Account preferences > Security. Store the recovery code in the approved vault; do not place it in a repository, ticket, chat, or output. 5. Have a second operator verify visible teams and permitted areas without opening worker documents or exporting personal data. 6. Record owner, groups, 2FA state, review date, and removal trigger. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-install-auth--34451e