Agent skill · data analytics · jeremylongshore
remofirst-common-errors
Debug RemoFirst contractor payment, invoice, timesheet, and access failures with evidence-safe decision paths. Use when a payment is late, mismatched, returned, unreconciled, or blocked. Trigger with "RemoFirst payment issue", "RemoFirst PRID", "contractor not paid", or "RemoFirst invoice error".
Why this skill is useful
Provides specific error handling patterns and API integration examples for RemoFirst that the AI wouldn't 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 Payment and Workflow Error Triage Overview Classify a RemoFirst operational failure before suggesting a correction while keeping payment state, bank settlement, invoice reconciliation, timesheet approval, and account visibility separate. A dashboard status such as Paid is evidence of platform state, not proof that funds reached the receiving account. Prerequisites A redacted issue summary, expected outcome, event time, and affected period. The authorized payment or workflow owner and escalation contact. Access to approved evidence without copying bank or identity data. Current Contract Delayed funds may require Proof of Payment, ISO/MX evidence, or an MT103 trace coordinated through RemoFirst; do not invent a transfer status. A wrong or missing Payment Request ID can prevent automatic reconciliation. Issued invoice changes require RemoFirst; approved credits apply later, while overpayments are refunded rather than credited to a future invoice. Unsigned agreements, incomplete onboarding gates, unapproved timesheets, or non-compliant invoices can block contractor payment. Instructions 1. Classify the issue as access, onboarding gate, timesheet, invoice, PRID, client funding, in-transit delay, returned payment, amount mismatch, or other. 2. Build a redacted timeline: expected amount/currency, invoice period, submitted and approved dates, payment status changes, and first observed failure. 3. For access or missing objects, verify tenant and group scope before requesting broader permissions. Never treat missing visibility as a deleted record. 4. For timesheet/invoice blocks, reconcile agreement, onboarding gates, approved hours, invoice, PRID, and client payment in sequence. 5. For delayed funds, request provider-approved trace evidence. Do not tell the contractor to retry, change bank details, or accept direct payment by default. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-common-errors--fc707f