case-to-resolution-protocol SKILL.md skillA
case-to-resolution-protocol from vincentchuwaichow/vanguard-frontier-agentic is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vincentchuwaichow/vanguard-frontier-agentic/case-to-resolution-protocol@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vincentchuwaichow/vanguard-frontier-agentic
- Path
skills/cross-functional/case-to-resolution-protocol/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1.0, committed Jul 31, 2026
- First version recorded
- Jun 17, 2026
- Size
- 6,683 bytes
- Repository stars
- 24
- License
- Apache-2.0
Use this skill when a customer service case must be triaged, routed to the right team, driven to resolution, and captured as reusable knowledge in Dynamics 365 Customer Service. Covers intake-to-routing, SLA tracking, escalation gates, knowledge capture, and post-resolution CSAT. Orchestrates the d365-customer-service-contact-center-agent as primary and invokes human escalation when SLA risk or knowledge gaps are detected. Does not make final resolution decisions or override customer service…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Case to Resolution Protocol ## Purpose This skill defines how a customer service case moves from first contact through routing, active resolution, and closure — and how every resolved case feeds the knowledge base so future cases resolve faster. It exists to ensure SLA accountability, consistent routing logic, and structured knowledge reuse across Dynamics 365 Customer Service. It does not replace human judgment on complex resolutions; it structures the handoffs so nothing falls through. ## When to use - A new case must be triaged and routed to a queue, team, or specialist. - An active case risks breaching its SLA and needs escalation. - A case is resolved and a knowledge article should be created or updated. - Post-resolution CSAT is due and results must feed continuous-improvement loops. - Multiple channels (email, chat, voice, social) need a unified intake view. ## When NOT to use - The case is already resolved and closed — routing decisions are moot. - The matter is a product defect escalation requiring engineering triage — use your engineering escalation runbook. - Regulated health or financial-services data handling requires compliance …
Read the whole file at its exact version.
How to install
mdr add vincentchuwaichow/vanguard-frontier-agentic/case-to-resolution-protocol@sha256:e978ee6b7229430eThe line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_374ip3ockqxyjffc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 17, 2026 and Jul 31, 2026, about one every 44 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.0 latest | 2026-07-31 | e5f8521 | 6,683 B | A | view · diff |
| v0.1.0 | 2026-06-17 | 50d7ede | 6,673 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6683 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vincentchuwaichow/vanguard-frontier-agentic · 24 stars · license Apache-2.0 · pushed 2026-10-20 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_374ip3ockqxyjffc GET https://markdownregistry.com/api/v1/resolve?ref=vincentchuwaichow/vanguard-frontier-agentic/case-to-resolution-protocol GET https://markdownregistry.com/api/v1/blob/e978ee6b7229430e33adb3a8243d6fd72ea70260ebe361ecb18a4454f67f327d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.