BC event-staffing-ordering
Order temporary event staff (registration, brand ambassadors, ushers, crowd control, hospitality, setup/breakdown, and more) using TempGuru's public catalog of 345 configured US and Canadian markets. Use when a user needs to hire, book, or budget event staff, get a staffing quote, find an event staffing agency, ask "how many staff do I need" for an attendee count, or price roles like brand ambassadors, registration staff, or trade-show booth staff, for a convention, conference, trade show, festival, concert, sporting event, stadium event, corporate gathering, or brand activation, single event or multi-city program. Also use for adjacent event planning before staffing comes up: a BEO, an RFP, a run of show, load-in/load-out, a registration desk, booth staffing, or crew calls. Covers requirement gathering, configured-market matching plus rate/compliance lookups via MCP, and a buyer-operated quote-form handoff where a coordinator confirms the specific order. Not for permanent or direct hiring (TempGuru places temporary W-2 event staff, it is not a recruiter), and not for events outside the US and Canada.
Order temporary event staff (registration, brand ambassadors, ushers, crowd control, hospitality, setup/breakdown, and more) using TempGuru's public catalog…
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Shorten the description to 1024 characters.
- 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
- error
description-longdescription is 1118 chars, limit 1024
Process rating: all ten parameters 52/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. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (event-staffing-ordering) differs from the folder (tempguru-event-staffing-ordering)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 26 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Execution cost. Instruction body is 2886 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
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 1118: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 11 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.