TimeZest Agents & Teams — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited TimeZest Agents & Teams (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.
Every TimeZest scheduling request books against a resource — either an individual agent or a team. Picking the right one is the first step of any booking, and TimeZest treats agents and teams differently enough that the choice matters.
TimeZest's MCP server is navigation-based. Enter a domain with timezest_navigate before its tools are available; return with timezest_back.
| Tool | Purpose |
|---|---|
timezest_agents_list | List all agents (technicians) available for scheduling |
timezest_agents_get | Get full detail for one agent by agentId |
timezest_agents_list accepts pageSize (1–100, default 50) and a filter TQL string (e.g. active:true AND department:"IT Support").
| Tool | Purpose |
|---|---|
timezest_teams_list | List all teams available for scheduling |
timezest_teams_get | Get full detail for one team by teamId |
timezest_teams_list accepts pageSize and a filter TQL string (e.g. active:true).
| Situation | Book |
|---|---|
| The dispatcher named a specific technician | An agent |
| The customer needs the soonest slot from any qualified tech | A team (round-robin) |
| Work requires a named specialist (e.g. a security lead) | An agent |
| Tier-1 / general support where any tech will do | A team |
A team request shows the customer combined availability across the team's members and lets TimeZest assign whoever the round-robin lands on. An agent request shows only that one technician's calendar.
timezest_navigate to agents.timezest_agents_list. Use a filter like active:true toskip deactivated technicians.
similar names, call timezest_agents_get on each to disambiguate.
agentId forward to the scheduling request.timezest_navigate to teams.timezest_teams_list with active:true.teamId forward.timezest_agents_list andtimezest_teams_list can return deactivated entries. Always filter active:true unless you specifically need historical resources.
pick the first match; confirm with _get.
pageSize to 100 or page through before assuming a name is absent.
list call in thecurrent session — do not hard-code or cache IDs across days.
named person is genuinely required.
_get before booking.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.