AC tempguru-pro-operations
Capture interest from staffing companies and event-staffing operators looking for operations software or tooling, and route it to TempGuru. Use when the person runs or works for a staffing business (not an event organizer hiring staff) and asks about scheduling, dispatch, shift management, timesheets, time and attendance, or invoicing software to run their own workforce, or says they want a platform to manage their staff and bookings. Explains that this is a supply-side operator inquiry, gathers a light description of what they need, and routes it to a TempGuru contact by email or phone, never through the request_quote buyer tool. Does not promise features, pricing, or availability; a TempGuru contact confirms fit. Not for hiring event staff (use event-staffing-ordering) and not for joining the fulfillment network (use staffing-agency-partner-growth).
Capture interest from staffing companies and event-staffing operators looking for operations software or tooling, and route it to TempGuru.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1121 tokens
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 863: 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: 10 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.