AD event-staffing-procurement
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).
Answer event staffing procurement and vendor-onboarding questions, then bridge a real event into a staffing plan.
As a process D 47/100 · Unfinished process — 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: 0. 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 47/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-procurement) differs from the folder (tempguru-event-staffing-procurement)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 1587 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 823: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 10 headings
- +3Step-by-step instructions: 7 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.