Agent skill · software engineering · jeremylongshore
remofirst-sdk-patterns
Build a supported RemoFirst integration boundary across Workday, ADP, reports, CSV, and provider-approved private contracts. Use when designing data exchange with RemoFirst. Trigger with "RemoFirst integration", "RemoFirst SDK", or "connect HRIS to RemoFirst".
Why this skill is useful
Provides specific implementation patterns and error handling for the 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 Supported Integration Boundary Overview Choose the narrowest documented exchange mechanism. The public first-party contract covers named Workday and ADP connectors plus controlled platform reports and CSV workflows; it does not establish a general RemoFirst SDK or API. Prerequisites Source system, business object, direction, cadence, owner, and lawful purpose. Data classification and approved minimum field set. Authorized RemoFirst and source-system administrators for connector changes. Current Contract Workday is a one-way inbound connector using a Workday integration system user and OAuth credentials; the RemoFirst operator starts sync manually. Supported Workday data is mapped before sync. Approved time-off and time-entry states matter; edits after sync may require reconciliation. Workday offboarding can be prefilled but requires human confirmation. ADP Workforce Now uses the RemoFirst connector and ADP SSO authorization. Reports and documented CSV templates are operator-controlled exports/imports. No public general SDK, endpoint, authentication, or versioning contract was found. Instructions 1. Classify the request as Workday inbound, ADP connection, report export, documented CSV workflow, manual platform operation, or private integration. 2. Reject a generic SDK design unless RemoFirst has issued a written contract to this customer. Record its owner and version without copying secrets. 3. Build a field-level map with source, destination, direction, required status, transformation, sensitivity, and accountable data owner. 4. For Workday, establish the least-privileged integration system user and OAuth client through Workday's approved administration path. Never store secrets here. 5. Test a minimal synthetic population, trigger the documented manual sync, and reconcile counts, fields, time rounding, approvals, and unsupported records. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-sdk-patterns