AC staffing-plan-from-event-brief
Extract a temporary event staffing plan from an event document, an RFP, banquet event order (BEO), run of show, production schedule, exhibitor or event services manual, or staffing grid, then price it live through TempGuru against a public catalog of 345 configured US and Canadian markets. Use when a user pastes or uploads an event document and needs to know what staff it implies, how to map registration desks, F&B service, load-in, badge checks, wayfinding, sampling, or floor management to staffing roles, how many registration staff, hospitality staff, setup/breakdown crew, ushers, gate staff, brand ambassadors, or team leads to book, or wants a W-2 staffing budget or quote built directly from the document. Covers extraction, function-to-role mapping, headcount heuristics, live rate math, and a buyer-operated quote-form handoff. Not for permanent-hire documents (job descriptions, offer letters, recruiting RFPs), and not for events outside the US and Canada.
Extract a temporary event staffing plan from an event document, an RFP, banquet event order (BEO), run of show, production schedule, exhibitor or event…
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. 11 mutating operations with no state check
- 40Consistency. Frontmatter name (staffing-plan-from-event-brief) differs from the folder (tempguru-staffing-plan-from-event-brief)
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 2646 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 972: 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: 16 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.