Agent skill · software engineering · jeremylongshore
remofirst-local-dev-loop
Rehearse RemoFirst imports, report reconciliation, and operator controls offline with synthetic fixtures before touching a client account. Use when testing CSV mappings, payroll controls, or connector cutovers. Trigger with "RemoFirst local rehearsal", "test RemoFirst import", or "RemoFirst dry run".
Why this skill is useful
Provides specific API integration patterns and error handling for the RemoFirst platform 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 Offline Workflow Rehearsal Overview Validate mappings and controls with synthetic data against RemoFirst's documented dashboard reports, two-column contractor-timesheet CSV upload, and named Workday/ADP connectors, which do not include a general public sandbox API. A local loop must therefore model documented inputs and decisions without claiming provider execution parity. Prerequisites The workflow and current first-party source that defines its fields. A fixture directory containing synthetic—not anonymized production—records. Expected counts, invariants, failure cases, and approval owner. Current Contract Contractor monthly timesheet CSV requires exactly Email and Total Monthly Hours; emails must match active accounts and hours allow up to two decimals. Downloadable reports include employee and contractor data and are sensitive. Workday mapping and sync semantics are documented separately; local fixtures are a model and cannot prove live connector behavior. Instructions 1. Name the workflow, source article, fixture schema, assumptions, and the provider behavior that the rehearsal explicitly cannot prove. 2. Generate synthetic identities, countries, amounts, dates, and record keys. Reject copied or merely masked production rows. 3. Encode field names, types, required/optional rules, uniqueness, rounding, and allowed state transitions from the reviewed source. 4. Add positive fixtures plus missing header, duplicate, invalid decimal, unknown identity, wrong period, stale mapping, and unsafe-field cases. 5. Run deterministic parsing and reconciliation: input, accepted, rejected, duplicate, and output totals must balance. 6. Produce a preview and rollback/checkpoint design. Do not create a live import file until a human approves both mapping and data source. 7. Mark PASS only for local controls. Record live validation as PENDING and assign an approved operator for the later dashboard step. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-local-dev-loop