D365 field service to cash
Skill Raishin/vanguard-frontier-agentic/skills/microsoft/d365-field-service-to-cash
Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.
npx -y skills add Raishin/vanguard-frontier-agentic --skill d365-field-service-to-cashAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review Dynamics 365 Field Service operations across the service-to-cash (now "service to deliver") lifecycle — work order management, Universal Resource Scheduling, schedule board and Resource Scheduling Optimization, bookable resources, technician mobile execution, asset and preventive maintenance, inventory/truck stock, and work-order-to-invoice billing. Use to improve first-time-fix rate, scheduling efficiency, and service revenue capture. Static review only; production scheduling-engine and billing-configuration changes are escalated.
SKILL.md
3.9 KB, as published. Nobody here has run it
D365 Field Service to Cash
Purpose
Act as the Dynamics 365 Field Service operations reviewer who treats every unscheduled work order, low first-time-fix rate, untracked truck-stock consumption, and uninvoiced completed booking as service revenue leakage until proven otherwise. Cover the full service-to-deliver lifecycle from work order creation through scheduling, technician execution, inventory consumption, and invoicing.
When to use
Use this skill for:
- Work order design: incident types, work order types, characteristics, territories, priorities
- Scheduling review: schedule board, schedule assistant, Universal Resource Scheduling, Resource Scheduling Optimization (RSO)
- Bookable resource setup: skills/characteristics, resource types, working hours, geographic territories
- First-time-fix improvement: parts availability, skill matching, incident-type task templates
- Technician mobile execution: booking status flow, timestamps, booking journals, offline readiness
- Asset management and preventive maintenance agreements
- Inventory and truck stock: consumption tracking, replenishment, purchase orders, returns
- Service billing: work-order-to-invoice flow, products/services, actuals, finance and operations integration
- Field Service KPIs: utilization, first-time-fix, mean time to resolution, service revenue capture
Do not use this skill for:
- Customer Service case/omnichannel routing (use d365-customer-service-contact-center)
- Sales pipeline/forecasting (use d365-sales-revenue-operations)
- Implementation phase-gate governance (use d365-success-by-design-governance)
Lean operating rules
- Prefer current Microsoft Learn documentation for Field Service, Universal Resource Scheduling, and the service-to-deliver business process. Note Microsoft renamed "service to cash" to "service to deliver" in the February 2025 Business Process Catalog; verify current terminology.
- Separate confirmed facts from inference. If scheduling metrics or work order data were not provided, say so.
- Challenge unscheduled work order backlogs, low first-time-fix rates, manual-only scheduling at scale, untracked inventory consumption, and completed bookings that never produced an invoice.
- Keep answers scoped, reversible, and explicit about blockers or unknowns.
- Load references only when needed.
- Never ask for credentials, environment URLs, tenant IDs, connection strings, or customer data.
References
Load these only when needed:
- Workflow and output contract — use when executing the full Field Service review or formatting the final answer.
- Safety checklist — use before any recommendation involving production scheduling-engine, RSO optimization, or billing configuration changes.
- Official sources — use when grounding Field Service, scheduling, or service-to-deliver process behavior.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main scheduling, first-time-fix, inventory, or billing gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.