Agent skill · software engineering · jeremylongshore
remofirst-debug-bundle
Assemble a privacy-safe RemoFirst support escalation bundle with a redacted timeline, record keys, screenshots index, and reproduction boundary. Use when support needs evidence for a platform or connector incident. Trigger with "RemoFirst debug bundle", "escalate RemoFirst", or "RemoFirst support ticket".
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 npm installed locally. 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 Privacy-Safe Support Bundle Overview Produce the smallest support packet that lets RemoFirst investigate without copying credentials, worker documents, bank details, full payrolls, or unrelated personal data. The bundle describes observed behavior and approved record keys; it does not reverse-engineer a private API or scrape a browser session. Prerequisites Incident owner, affected workflow, first/last observed time, and severity. A redaction standard and approved support channel. Consent to include each screenshot or exported field. Current Contract RemoFirst accepts support by email, in-platform chat/live agent, and Help Center ticket. The Workday guide asks for company name, affected team member, relevant Workday record or event, and a clear issue description. Payment investigations may require provider-issued trace evidence; sensitive values should travel only through the approved support path. Instructions 1. Assign a bundle ID, owner, severity, workflow, environment, tenant/company, affected period, first seen, last seen, and business impact. 2. Write expected and observed behavior in neutral terms. Separate facts from hypotheses and label every timestamp with timezone. 3. Include only redacted provider-visible identifiers needed to locate the case. Use placeholders for worker, bank, payment, and authentication values. 4. List reproduction steps that stop before any irreversible approval, payment, connector reset, offboarding, or personal-data exposure. 5. Create an evidence manifest with filename, source, capture time, owner, redaction reviewer, sensitivity, and retention deadline. 6. Scan the bundle for passwords, codes, cookies, tokens, bank details, identity documents, health data, and unrelated workers. Remove or quarantine findings. 7. Draft the support message with bundle ID, urgency, requested decision, and next contact time. A human reviews and sends it through the approved channel. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/remofirst-debug-bundle