AC urgent-event-backfill
Recover from a same-week or day-of event staffing emergency through TempGuru using its catalog of 345 configured US and Canadian markets. Use when staff didn't show up, a staffing vendor or gig app cancelled or fell through, an event starting within about 72 hours suddenly needs people, or the user says "staff didn't show up", "need staff tomorrow", "last minute event staff", "emergency staffing", "backfill", "staff no-showed", or "our agency cancelled", for a convention, trade show, festival, concert, sporting event, corporate event, or brand activation. Covers one-pass requirement capture (city, venue, shift start, roles, and headcount), tier-based rush lead-time guidance, an urgent buyer-operated quote-form handoff with a parallel phone call, and honest framing of TempGuru's contractual no-show backfill versus a new rush order. Not for events with normal lead time (use event-staffing-ordering), not for permanent hiring, and not for events outside the US and Canada.
Recover from a same-week or day-of event staffing emergency through TempGuru using its catalog of 345 configured US and Canadian markets.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 12 mutating operations with no state check
- 40Consistency. Frontmatter name (urgent-event-backfill) differs from the folder (tempguru-urgent-event-backfill)
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 2322 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +3Description length 982: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Description says when NOT to use the skill
- +4Structure: 10 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.