Agent skill · software engineering · jeremylongshore
remofirst-core-workflow-b
Manage RemoFirst contractor onboarding from engagement choice through agreement, identity, tax, bank, timesheet, invoice, and first-payout readiness. Use when engaging or paying an international contractor. Trigger with "onboard RemoFirst contractor", "contractor payout readiness", or "RemoFirst contractor payment".
Why this skill is useful
Adds executable scripts for payroll processing, employee payslip management, and invoice generation specific to the RemoFirst platform.
What it needs
Requires curl, npm installed locally. Requires remofirst account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
RemoFirst Contractor Onboarding and First Payout Overview Prepare a contractor engagement and first-payment control record while treating contractor and EOR engagements as different classification, benefit, control, and compliance decisions. RemoFirst's documented contractor path is dashboard-operated and requires agreement, tax, identity, bank, invoice, and payment checkpoints. Prerequisites Approved engagement model, country, work scope, term, rate, and currency. Authorized signatory, line manager, and payment owner. A classification review and approved personal-data handling path. Current Contract Rate types include monthly, daily, hourly, and milestone; available currencies and payment frequency belong to the live engagement context. The client may generate an agreement in RemoFirst or upload a pre-signed one. Contract signing enables timesheet submission; first payout also depends on tax forms, identity verification, bank details, and compliant invoicing. Approved hours link to an invoice, and payments are processed only after the client funds the required payment. A status is not a bank-settlement guarantee. Instructions 1. Record why contractor—not EOR—is approved, plus country, scope, term, rate type, amount, currency, frequency, manager, signatory, and payment owner. 2. Choose generated or pre-signed agreement handling. Record that RemoFirst does not accept legal responsibility for a client-uploaded pre-signed agreement. 3. Reconcile contractor, job, compensation, IP, confidentiality, and signatory fields before sending an invitation. Require two-person review for money. 4. Track agreement signature, tax form, identity verification, bank details, and invoice readiness as separate gates. Do not mark payout-ready from one gate. 5. For hourly work, review or reject the submitted timesheet. Approval locks the entry for payment; rejection must carry a clear correction reason. 6. Match the approved period and hours to the invoice and correct Payment Request ID. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-core-workflow-b