TimeZest Scheduling — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited TimeZest Scheduling (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The "book a tech against this PSA ticket" workflow is what TimeZest exists for. This skill walks the canonical flow: resolve the agent, resolve the appointment type, create the scheduling request with the PSA association, then poll for the customer's response.
| Tool | Purpose |
|---|---|
timezest_agents_list | List available technicians |
timezest_agents_get | Detail for a specific agent |
timezest_teams_list | List teams (round-robin / shared availability) |
timezest_teams_get | Detail for a specific team |
timezest_appointment_types_list | List bookable appointment types |
timezest_appointment_types_get | Detail for one appointment type |
timezest_resources_list | List resources (rooms / shared assets) |
| Tool | Purpose |
|---|---|
timezest_scheduling_list | List recent scheduling requests |
timezest_scheduling_get | Pull current state of one request |
timezest_scheduling_create_request | Create a new request (sends customer link) |
timezest_scheduling_cancel | Cancel a pending request |
timezest_agents_list and match.timezest_teams_list.timezest_appointment_types_list and pick the one thatmatches the ticket type (e.g. "Onsite Visit", "Remote Session").
timezest_scheduling_create_request with:agent_id or team_idappointment_type_idassociated_entities linking to the PSA tickettimezest_scheduling_get with the request ID./ expired.
window, surface that to the dispatcher — the link may need to be resent.
timezest_scheduling_get to confirm current state.timezest_scheduling_cancel to revoke the customer link.timezest_scheduling_list.how many waiting on the customer, how many booked today.
window, TimeZest still creates a request but the customer will see "no times available". Surface the agent's calendar gap to the dispatcher.
parallel. Always set the correct associated_entities.type.
second a dispatcher cancels. Always re-fetch state after a cancel call.
the same session; do not cache IDs across days.
ticket - the PSA only sees the booking after it is confirmed.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.