TimeZest Resources — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited TimeZest Resources (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 resources domain is TimeZest's combined view of everything bookable — agents and teams together in one list. It is the right starting point when a dispatcher has not named a specific technician or team and you need to survey the pool first.
Enter the domain with timezest_navigate to resources.
| Tool | Purpose |
|---|---|
timezest_resources_list | List all resources (agents and teams) available for scheduling |
timezest_resources_list accepts:
pageSize — results per page (1–100, default 50)type — agent or team to filter by resource typefilter — a TQL filter string (e.g. active:true)Each resource entry indicates whether it is an agent or a team, so a single call surveys the whole bookable surface.
Use the resources domain when | Use agents / teams when |
|---|---|
| You want a combined survey of everything bookable | You already know it is an agent or a team |
| The dispatcher said "whoever's available" | The dispatcher named a person or team |
| Producing a roster or capacity report | Fetching detail for one named resource |
timezest_resources_list is list-only — there is no timezest_resources_get. To fetch full detail for one resource, drop into the agents or teams domain and use its _get tool.
timezest_navigate to resources.timezest_resources_list with filter: "active:true".type (agents vs teams) to give the dispatcherthe full menu.
active:true.type: "agent" or type: "team" if the dispatcherleaned one way.
agents or teamsdomain for full detail before booking.
pageSize: 100 to capture the full pool.agents orteams for detail.
teams; always check the type of each entry before treating it as one or the other.
pageSize orpage through for a complete roster.
resources for surveys and rosters; use agents / teams fornamed lookups and detail.
active:true for booking work — inactive resourcescannot be scheduled.
actual scheduling request still books a specific agentId or teamId.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.