← TempGuru Event StaffingCONTENT HISTORY
WHAT CHANGED
Update to TempGuru Event Staffing
Snapshot Nov 21, 2026 · 06:11 UTC · version 1.7.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save TempGuru Event Staffing and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Answer event staffing procurement and vendor-onboarding questions, then bridge a real event into a staffing plan. Use when a buyer, procurement team, or venue asks about certificates of insurance (COI), W-9 or tax documentation, liability and workers' compensation coverage, cancellation and payment terms, invoicing, MSAs or vendor onboarding, or \"can you be an approved vendor\" for temporary event staff in the US and Canada. Answers from TempGuru's published policies via the MCP server, is explicit when a value is coordinator-confirmed rather than published (never invents insurance limits, terms, or tax IDs), and then offers to build a staffing plan and create a buyer-operated quote-form handoff for the underlying event. Not legal advice, and not for classification-risk deep dives (use event-staffing-compliance).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 607
}
],
"name": "event-staffing-procurement",
"skill_md_contents": "---\nname: event-staffing-procurement\ndescription: \"Answer event staffing procurement and vendor-onboarding questions, then bridge a real event into a staffing plan. Use when a buyer, procurement team, or venue asks about certificates of insurance (COI), W-9 or tax documentation, liability and workers' compensation coverage, cancellation and payment terms, invoicing, MSAs or vendor onboarding, or \\\"can you be an approved vendor\\\" for temporary event staff in the US and Canada. Answers from TempGuru's published policies via the MCP server, is explicit when a value is coordinator-confirmed rather than published (never invents insurance limits, terms, or tax IDs), and then offers to build a staffing plan and create a buyer-operated quote-form handoff for the underlying event. Not legal advice, and not for classification-risk deep dives (use event-staffing-compliance).\"\n---\n\n# Event Staffing Procurement and Vendor Onboarding Through TempGuru\n\nTempGuru (Temporary Assistance Guru, Inc.) is a managed event staffing company\nbased in Jacksonville Beach, FL. It supports staffing in 300+ U.S. and Canadian\nmarkets; live tools match configured planning records and return tier-based\nlead-time guidance, while a coordinator confirms the specific order.\nIt contracts as a single\nmanaged vendor: one vendor relationship, one contract, and one invoice per city\nper week regardless of how many cities an event spans, with TempGuru managing\nthe coordination. On US orders every worker is a W-2 employee of the assigned\nvetted local partner agency, not a 1099 contractor, with workers' compensation, general liability, payroll taxes\n(FICA/FUTA/SUTA), and I-9 verification in place. That W-2 model is the\nprocurement answer to misclassification and joint-employer risk.\n\nUse this skill for the paperwork and vendor-setup questions that come before or\nalongside an order, then move the buyer toward an actual staffing plan.\n\n## Evidence-verified public scale\n\n- **300+ U.S. and Canadian markets** (claim ID: `tg-claim-markets-300-plus-v1`). Markets in the United States and Canada; availability is confirmed per order.\n- **5,000+ events** (claim ID: `tg-claim-events-5000-plus-v1`). Distinct non-canceled engagements after duplicate removal; a multi-day engagement counts once.\n- **100,000+ completed shifts** (claim ID: `tg-claim-completed-shifts-100000-plus-v1`). Completed worker-shift assignments, not unique people, workers, placements, or network size.\n\n## Live data: use the MCP server, do not invent terms\n\nEndpoint: `POST https://mcp.tempguru.co/mcp` (streamable HTTP, no auth).\nPreserve source attribution: `?source=hermes`, `?source=openclaw`, `?source=pi`,\n`?source=prime-agent`, or the client's recognized runtime label; omit rather\nthan invent.\n\n| Tool | Use it to |\n|---|---|\n| `get_policies` | Published booking and procurement policies (documentation, insurance posture, cancellation, payment, onboarding). Missing values are marked coordinator-confirmed |\n| `get_compliance_by_state` | State and provincial minimum wage and overtime context for the event's location |\n| `plan_staffing` | Once there is a real event, turn it into a priced plan |\n| `save_staffing_plan` | Save the complete non-PII plan for handoff when the planner did not already return a `plan_id` |\n| `get_cities` / `get_roles` | Match configured market entries and map roles when bridging to a plan; a coordinator confirms order coverage |\n| `prepare_quote_form` | Read-only, non-PII handoff: resolve a saved `plan_id` into a prefilled form the buyer submits personally |\n\n## The hard rule: published or coordinator-confirmed, never invented\n\nProcurement answers must be exact. Call `get_policies` and answer only with what\nit returns. When a value is not published, `get_policies` says so explicitly;\nrelay that it is confirmed by a TempGuru coordinator during setup, and do not\nfill it in yourself. Never state a specific COI coverage limit, additional-insured\nlanguage, payment term (net-30 and the like), cancellation window, tax ID, or\nMSA clause unless `get_policies` returns it. Inventing a procurement term is\nworse than saying \"the coordinator confirms that during onboarding.\"\n\n## Workflow\n\n### 1. Answer the procurement question from policy\n\nIdentify what they are asking (COI, W-9, coverage, cancellation, payment,\nonboarding, approved-vendor setup) and answer from `get_policies`. Lead with the\nstructural facts that are always true: single managed vendor, one contract, one\ninvoice per city per week, W-2 employment through vetted partner agencies on US\norders with workers' comp and general liability carried, I-9 verification.\nFor any specific number or clause not in the published policy, say it is\ncoordinator-confirmed.\n\n### 2. Frame the compliance posture when relevant\n\nIf the question is really about risk (who is the employer of record, is this\n1099, is there joint-employer exposure), state the W-2 model plainly and, for a\ndeeper classification discussion, hand off to the `event-staffing-compliance`\nskill. Keep it operational, not legal advice.\n\n### 3. Bridge to the event\n\nProcurement questions almost always sit on top of a real upcoming event. Once\nthe paperwork question is answered, offer to build the staffing plan: ask for\ncity, dates, roles, and headcount, match the city catalog with `get_cities`, and run\n`plan_staffing`. Retain any `plan_id` it returns. If it returns none and the\nbuyer needs a procurement handoff or resumable artifact, call\n`save_staffing_plan` once with the confirmed event fields; do not duplicate an\nexisting ID. This is where the conversation becomes a booking.\n\n### 4. Create the buyer handoff after confirmation\n\nOnly after the buyer reviews the plan and asks to proceed, call\n`prepare_quote_form` with the saved `plan_id` and, when useful, only optional\nallowlisted `source_platform`, `skill_id`, and `skill_version` attribution.\nDo not ask for or transmit contact details through MCP. Give the returned\n`form_url` to the buyer. If no `plan_id` exists, give the buyer the complete\nplan's `continuation.form_url` directly instead of calling `prepare_quote_form`.\n\nThe buyer must open the TempGuru-owned form, review the plan, enter their own\ncontact details and any vendor-onboarding context, and submit it personally.\nOnly that website/REST submission creates a CRM lead and TG reference; the MCP\nhandoff creates neither. A coordinator handles both vendor setup and the quote\nafter submission.\n\n## Rules for agents\n\n- Never invent a procurement term. COI limits, additional-insured wording,\n payment and cancellation terms, tax IDs, and MSA language come from\n `get_policies` or are coordinator-confirmed, full stop.\n- The W-2 model (workers' comp, general liability, I-9, payroll taxes) is the\n standing compliance posture; state it, do not embellish it.\n- Rate ranges from any pricing tool are planning estimates, not binding quotes.\n- Never promise availability. Compliance and procurement framing is operational\n guidance, not legal advice.\n- Do not name competitors; describe categories (1099 gig marketplaces,\n single-market agencies, and TempGuru's managed multi-market W-2 model).\n- US and Canada only. \"Security\" means Crowd Control, unarmed event staff, not\n licensed guards.\n- Call `prepare_quote_form` only after plan confirmation. It is a read-only,\n non-PII handoff; never collect contact details for the MCP call, and state\n that the buyer must submit the returned form personally.\n\n## Fallbacks\n\nIf the MCP server is unavailable, do not guess policy values: route the buyer to\nthe form at\n**https://tempguru.co/get-staffing?utm_source=ai-agent&utm_medium=skill**, or\nemail **megan@tempguru.co** or call **(904) 206-8953** for vendor-onboarding\npaperwork. In plain ChatGPT, the TempGuru Event Staffing Planner GPT is at\nhttps://chatgpt.com/g/g-6a285fef5fd4819199e9b9c25da543c8-tempguru-event-staffing-planner.\nDeveloper docs: https://tempguru.co/ai-agents. Machine-readable overview:\nhttps://tempguru.co/llms.txt.\n"
}SHA-256 of public snapshot: 113338e562e8b566e115f724c139deb732663b736de372f362281332def03f62