Agent skill · software engineering · jeremylongshore
remofirst-rate-limits
Build RemoFirst operational deadlines and supported connector sync cadence without inventing API quotas. Use when payroll, timesheet, invoice, Workday, or ADP timing affects a workflow. Trigger with "RemoFirst cutoff", "RemoFirst sync timing", or "RemoFirst rate limits".
Why this skill is useful
Provides specific implementation patterns and error handling for RemoFirst API that the AI wouldn't reliably generate on its own.
What it needs
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 Deadlines and Sync Cadence Overview Build a timing plan from the documented business cutoffs and supported connector behavior. No reviewed public source publishes a general RemoFirst API quota, so this skill must not manufacture request-per-minute limits, retry headers, endpoints, or backoff rules. Prerequisites Workflow, population, period, country, owners, and timezone. The live RemoFirst calendar or connector status available to an authorized user. A support owner for ambiguities or missed deadlines. Current Contract Monthly payroll has documented revision, review, approval, and funding stages; live dates and worker-specific schedules remain authoritative. Contractor timesheet approval locks a submitted timesheet; rejection returns it for correction. Workday sync is manually initiated and imports only supported approved records. ADP setup uses a short-lived account ID during connector authorization. No public first-party general API quota or SDK retry contract was found. Instructions 1. Classify the timing domain: payroll, contractor timesheet, invoice funding, Workday sync, ADP activation, or a provider-issued private integration. 2. Record every time in one canonical timezone plus the operator's local time. Include source URL, retrieval date, owner, and whether it is a guide or live date. 3. For payroll, confirm revision, approval, funding, and pay-date milestones from the live period. Do not silently reuse dates from a prior month. 4. For timesheets, leave review time before approval because approval locks the record. Reject incorrect entries early enough for contractor correction. 5. For Workday, schedule a human-triggered sync, review imported records, and reconcile unsupported or edited data manually. 6. For ADP, generate the account ID only when the connector owner is ready to use it; if it expires, repeat the documented setup instead of reusing it. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-rate-limits