$ loading_
Review and prioritize critical service requests in a read-only dispatch dashboard.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "field-service-dispatch-dispatch-dashboard" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/aibast-agents-library/main/solutions/field-service-dispatch/manual/skills/aibast_dispatch-dashboard/SKILL.md 2. Save it as ~/.claude/skills/aibast_dispatch-dashboard/SKILL.md 3. Reload skills and tell me it's ready
Use the dispatch_dashboard operation to find the current unassigned critical Central request and provide verifiable identifiers and evidence. Note any uncertainty and make clear this is a read-only result.
Returns the most critical unassigned service request with its identifier, severity, supporting evidence, and a note that authorized review is required.
Following dispatch_dashboard behavior, check whether the service-request queue contains an emergency record for a 'SCADA communication failure' and state its priority, whether a job is assigned, and the evidence source.
Outputs a source-backed determination of whether the request is emergency/CRITICAL, whether it has no job assigned, and a reminder of the no-write boundary.
Summarize the read-only service-request information visible through dispatch_dashboard, prioritizing the most urgent unassigned items, and end by stating that no system records were modified.
Provides a priority-ordered summary highlighting critical unassigned requests, supporting evidence, uncertainty, and a no-write statement.
A field operations manager can use this skill to review the service-request queue in read-only mode and identify the most critical unassigned request before allocating resources. This supports prioritization without changing any records.
When a team needs to confirm whether an emergency event is still unhandled, this skill can provide the request identifier, severity, and evidence that no job is assigned. The result also notes uncertainty and the need for authorized review.
The document describes a field service dispatch agent centered on the `dispatch_dashboard` operation. It instructs the agent to read synthetic knowledge records and controls, reproduce only the operation’s read-only behavior, and lead with source-backed identifiers and evidence. It also requires stating uncertainty, calling for authorized review, and ending with a clear no-write boundary that avoids implying any system or record changes.
Use the dispatch_dashboard operation. The canonical persona prompt is:
What critical Central request is unassigned right now?
dispatch_dashboard operation behavior.Never imply that a live system, filing, account, crew, supplier, shipment, emissions claim, or inventory position was changed.
It is used to review a service-request dispatch dashboard in read-only mode and identify the critical unassigned request that should be prioritized. It emphasizes evidence-backed conclusions and does not perform write actions.
No. The documentation explicitly requires a no-write boundary and says it must not imply that any system, job, account, or other record was changed.
The required evidence listed in the docs includes the emergency event 'SCADA communication failure,' the severity 'CRITICAL,' and the status 'No job.' For more detail, see the source repository.
Analyze loyalty tier thresholds, perks, progress, and tradeoffs without changing status.
Identifies tax-loss-harvesting candidates and required review controls.
Review SIU indicators in claims and return explainable evidence with human review guidance.
Find each line’s bottleneck and recommend which station to address first.
Generates controlled implementation checklists for human review.
Creates a deterministic reconsideration evidence packet from synthetic source files.
Dispatch field service jobs with instant quotes and tracked work orders.
Triage support tickets by priority, ownership, and duplicate or known issue checks.
Let agents perform permission-scoped product operations in Priorify workspaces.
Orchestrate multi-agent workflows, track spend, and govern AI operations centrally.
List, score, and rank automation requests from a Notion backlog.
Triages fictional insurance claims and summarizes key intake details and priority.