Agent skill · software engineering · jeremylongshore
remofirst-upgrade-migration
Control a RemoFirst workflow cutover to supported Workday, ADP, report, or CSV exchange with reconciliation and rollback. Use when replacing a manual data handoff or changing a connector. Trigger with "migrate to RemoFirst", "RemoFirst cutover", or "change RemoFirst integration".
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 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 Controlled Workflow Cutover Overview Plan a reversible change from a manual/export process to a documented RemoFirst connector or from one supported boundary to another. This is a business-data cutover, not an API-version migration; no public general API version contract was found in the reviewed first-party documentation. Prerequisites Current and target process owners, systems, populations, countries, and dates. Baseline counts/totals and an approved minimum field map. Change approver, privacy/security review, rollback owner, and support path. Current Contract Workday provides one-way inbound data to RemoFirst through mapped fields and a manually initiated sync. Approved time-off/time-entry state affects eligible Workday data; edits may not automatically resync, and time is subject to documented conversion/rounding. Workday offboarding data is prefilled but still needs human confirmation. ADP authorization uses its named connector, SSO flow, and temporary account ID. Reports and CSV workflows remain controlled alternatives for supported tasks. Instructions 1. Document the current process, target boundary, business objective, exclusions, accountable owners, freeze window, and success/abort criteria. 2. Inventory and classify fields. Map only documented target fields, record direction and transformations, and exclude unsupported or unnecessary data. 3. Establish least-privileged connector identities and approvals without copying credentials into the plan, repository, ticket, or support bundle. 4. Test with synthetic records, then a small approved cohort. Reconcile source and destination counts, values, status, time conversion, and ownership. 5. Run a time-boxed parallel period against the current controlled process. Keep one authoritative writer per field and prevent duplicate payroll actions. 6. At the change gate, obtain explicit business, system, security/privacy, and payroll approval. Start the production sync or authorization only then. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-upgrade-migration