Microsoft
- 2k skills
- 0 followers
- 195k repo stars
- 210 verified
- 2 days ago last updated
- ▌ Sap Power Platform Integration Architect · microsoft bundleUse this skill whenever the user asks how to connect, integrate or extend SAP (ECC, S/4HANA, RISE, S/4HANA Cloud, SuccessFactors, BTP) with Microsoft Power Platform or Copilot Studio: which SAP connector, gateway, API layer or single sign-on option to choose; why use Copilot Studio or Microsoft 365 Copilot when SAP Joule exists and how Joule and Copilot work together; or whether to extend inside SAP (Fiori, key-user, ABAP Cloud, SAP Build, BTP) or with Power Apps, Power Automate, Power Pages or Copilot Studio. Also when the user uploads an SAP landscape or requirements document and asks for an architecture. Run it BEFORE answering: it answers straight away with stated assumptions that follow Microsoft's and SAP's documented patterns, attaches an architecture report, and offers a pre-filled template the user can complete to refine the answer.
- ▌ Store Map · microsoft bundleRetrieves one store's profile for the promotion readiness test — format, cluster, fixtures, received assets, completed tasks, prior execution history and current shelf prices — from the store master, receiving, task-system and POS exports into store.json + shelf-prices.json. Use after pack-ingest, or when the user asks "what does this store actually have", "pull the store profile for <id>", "what's been received at the store", "which launch tasks are done", "get the current shelf prices for store <id>". Do NOT use for floor plans, department layouts or wayfinding maps — use a store layout / planogram tool instead; not for the readiness verdict — use readiness-check instead; not for ingesting the HQ pack — use pack-ingest instead.
- ▌ Appeal Draft · microsoft bundleDrafts the level-appropriate appeal letter from the cited policy clause and chart evidence already on the contract, with the deadline status in the header. Use when asked to "draft the appeal letter", "write the appeal for this denial", "put together our response to Contoso", "redraft this appeal on the original code". Use after evidence-assemble and deadline-track. Do NOT use to classify a new denial or "start an appeal" from a remittance - use denial-classify instead; do NOT use to gather evidence - use evidence-assemble instead; do NOT use to find policy - use policy-retrieve instead; do NOT use to compute the deadline - use deadline-track instead. Never sends, files or uploads the appeal: hand it to the human coordinator. Action level L0: draft text only.
- ▌ Exec Update · microsoftCompresses content you already have into an executive-ready update: strict TL;DR / Key numbers / Risks / Ask structure, ~150 words, answer first. Use when the user asks to "turn this into an exec update", "summarize this for my VP", "make this leadership-ready", "give me a TL;DR for the CFO", or "compress this into a status note". Do NOT use for assembling an update from your own recent activity, org-wide announcements, long-form reports (use docx), or analysis that does not exist yet.
- ▌ Edit Contract · microsoftMakes precise, minimal changes to an existing legal document, with every modification made as a tracked change. Use when the user asks to "change the notice period in clause 9 to 60 days", "add a limitation of liability clause", "soften this indemnity", "delete the exclusivity provision", "fix the wording of this definition", or "redline this agreement so that…". Do NOT use for reviewing a contract against a playbook — use review-contract instead; for explaining the changes in a marked-up draft use summarize-redlines, and for a new agreement from a precedent use draft-new-contract.
- ▌ Section Plan · microsoft bundleWork out which sections a CSR or 510(k) requires, from the templates in config, check each one against the cited fact map, and name what is missing before a word is drafted. Use when the user asks "what do we still need before we can draft the CSR?", "which sections are ready to start?", "what's blocking the performance data section?", "do we have everything for the synopsis?" or "map our tables to the E3 structure". Do NOT use for writing section language - use section-draft instead. Do NOT use for cross-checking a finished draft - use consistency-check instead. Do NOT use for outlining general Word documents or business reports - use the built-in docx skill instead. Only structures with a template in config are supported. Guardrail: plans only; never marks a section ready on a missing fact and never invents a structure.
- ▌ Eligibility Check · microsoft bundleDetermines return eligibility against the configured policy and surfaces fraud signals deterministically with the eligibility_check engine - the explicit Govern step of this plugin. Use after reason-classify, or on "is this returnable", "do they qualify for a refund", "check eligibility", "any fraud signals", "can we accept this return". Do NOT use to retrieve policy text - use policy-retrieve instead; not to start a case - use return-intake; not to draft the packet or customer response - use case-packet.
- ▌ Disruption Intake · microsoft bundleExtracts cited local supplier delay notices into draft contract inputs. Use for "a PO is late", "process this supplier notice", "intake this disruption", "extract the delay facts", or "our supplier is delayed". Do NOT use for impact mapping, retrieval, mitigation or terminal drafts — use shortage-impact-map, supply-knowledge-retrieve, mitigation-recommend or disruption-writeup instead. Offline only; no supplier or ERP actions.
- ▌ 3 Statements · microsoft bundleCompletes existing income statement, balance sheet and cash flow templates while preserving layout, grounding historical inputs and linking forecast formulas with reconciliation checks. Use for "fill in a 3-statement template", "complete an IS/BS/CF framework", "populate my integrated financial model", "link statements in this template", or "finish the forecasts in my three-statement workbook". Do NOT use for blank-slate models or general workbook edits (use xlsx), DCF valuation (use dcf-valuation), or buyout modeling (use lbo-model).
- ▌ Meeting Moments Library Builder Cowork · microsoft bundleDiscovers the user's authorized Microsoft 365 meetings and transcripts, then builds a reviewable library of verified moments in Microsoft 365 Copilot Cowork. Use whenever the user wants a how-to library, decision log, customer-voice library, demo highlights, lessons-learned archive, onboarding library, or another searchable collection of timestamped meeting moments. Search the date range and meeting series the user chooses using native Microsoft 365 meeting/transcript capabilities; fall back to attached transcripts only when discovery or transcript access is unavailable. Verify every proposed entry against transcript evidence, require approval before publication, then deliver portable HTML, CSV, and JSON library files. Never invent a timestamp, presenter, recording link, or quote. Never publish transcript content, upload files, or write to SharePoint without explicit confirmation.
- ▌ Section Draft · microsoft bundleWrite or revise the language for one planned CSR or 510(k) section - synopsis, efficacy, safety, discussion, device description - using only figures already in the cited fact map, each with its TLF or SAP citation. Use when the user asks "draft the Synopsis from our locked tables", "write up safety from Table 14.3.1", "give me a first pass at the discussion", "draft the device description for the 510(k)" or "tighten the wording of the Discussion section". Do NOT use for supplying a number not already in source_facts - use source-ingest instead. Do NOT use for verifying a draft's figures - use consistency-check instead. Do NOT use for appeal letters, clinical notes or discharge summaries - use the matching HLS plugin instead. Guardrail: drafts for human approval only (L1); never asserts an unsourced number or harmonises two figures.
- ▌ Source Ingest · microsoft bundlePull every number, date and population definition out of a study's protocol, SAP, TLF tables, investigator brochure and prior approved text into one cited fact map, keyed per config/field-dictionary.json, before any CSR or 510(k) section is written. Use when the user asks "here's the locked TLF set and SAP, set up the CSR", "load the protocol and tables before we start drafting", "what figures do we have from the database lock?", "pull the disposition counts out of Table 14.1.1" or "ingest the IB for the 510(k)". Do NOT use for drafting or assembling submission sections - use section-draft or submission-assemble instead. Do NOT use for reconciling a patient's medications - use the discharge-care-transition plugin instead. Guardrail: reads and cites sources only; never estimates, rounds or invents a fact.
- ▌ Policy Retrieve 2 · microsoft bundleResolves the applicable policy clause and checks promotion eligibility deterministically with the policy_resolve engine (window AND cluster AND SKU). Use after question-intake on "what does the policy say", "is this return within the window", "can we price match this competitor", "is the customer eligible for the promo", "does the raincheck clause apply". Do NOT use for a fresh floor question with no question.json - use question-intake instead; not for a pure two-SKU spec comparison - use product-compare; not to present an already-computed promo result - use promo-check; not to draft the answer - use answer-draft.
- ▌ Product Compare · microsoft bundleBuilds a side-by-side product comparison from the PIM extract with the deterministic product_compare engine - differences stated, missing shown as MISSING, never guessed. Use when the associate asks "what's the difference between these two", "which should I recommend", "compare SKU A and SKU B", "side-by-side on these two models", "which one has the longer warranty". Do NOT use for a fresh floor question with no resolved payload - use question-intake instead; not for single-SKU promo or price questions - use promo-check or policy-retrieve; not to draft the final answer - use answer-draft; not for specs outside the PIM extract.
- ▌ Question Intake · microsoft bundleTakes an associate's floor question with store, role and department context into the rtl.store-associate-assist.v1 contract (question.json, the entry hop). Use when an associate asks "can she return this", "do we price match", "is this still on promo", "what's the difference between these two", "customer is asking about the return policy", or any new floor question about policy, product or promotion. Do NOT use to resolve the policy - use policy-retrieve instead; not to present promo results - use promo-check; not to compare two SKUs from a resolved payload - use product-compare; not for the final answer - use answer-draft; not for staffing, scheduling, inventory or refund requests.
- ▌ Disruption Writeup · microsoft bundleRenders one fixed Markdown draft containing a cited supplier follow-up and internal escalation brief from a local packet. Use for "draft the supplier follow-up", "write the escalation brief", "draft the supplier email", "write it up", or "prepare the internal brief". No audience-switching or document conversion. Do NOT use for intake, retrieval, mapping or mitigation — use disruption-intake, supply-knowledge-retrieve, shortage-impact-map or mitigation-recommend. No sending, ERP writes or spending, even after approval.
- ▌ Lbo Model · microsoftBuilds a leveraged buyout model: sources and uses, a debt schedule with cash sweep, operating projections, and returns to the sponsor as IRR and money multiple, plus sensitivity on entry multiple, exit multiple, and leverage. Use when the user asks to "build an LBO model", "what returns does this deal generate", "run the sponsor returns", "how much leverage can this support", "model the buyout", or "IRR and MOIC for this transaction". Do NOT use for intrinsic cash-flow valuation, trading comparables, or corporate budgeting and forecasting.
- ▌ Criticality Rank · microsoft bundlePrioritizes the fault by asset criticality and downtime cost into a P1-P4 maintenance priority with a response target and cost estimate, deterministically. Use when the user says "how urgent is this", "what's the priority", "rank by criticality", "what will downtime cost", or after failure-mode-rank completes. Do NOT use for intake — use fault-intake; history retrieval — use history-retrieve; cause ranking — use failure-mode-rank; drafting — use work-order-update.
- ▌ History Retrieve · microsoft bundleRetrieves the asset's maintenance history — prior work orders, similar failures, PM records — and the relevant OEM manual and troubleshooting sections, and attaches them to the mfg.maintenance-triage.v1 contract. Use when the user says "pull the history for <asset>", "has this failed before?", "find the manual section", "any prior work orders?", or after fault-intake completes. Do NOT use for intake — use fault-intake; cause ranking — use failure-mode-rank; priority — use criticality-rank; drafting — use work-order-update.
- ▌ Policy Retrieve · microsoft bundleRetrieves the applicable return policy clauses and the configured windows/limits for a return case and attaches them verbatim as policy_context. Use after return-intake, or on "what does the return policy say for <category>", "what's the return window for", "pull the policy clauses", "what does policy say about no receipt", "attach the policy to the case". Do NOT use to decide eligibility or red flags - use eligibility-check instead; not to start a case - use return-intake; not for the packet - use case-packet.
- ▌ Reason Classify · microsoft bundleClassifies the stated return reason against the reason-code taxonomy with the deterministic reason_classify engine, recording confidence and candidate codes. Use after return-intake in every case, or on "what reason code is this", "classify the return reason", "which reason code", "code this return", "why are they returning it". Do NOT use for sentiment or complaint triage; not for eligibility or red flags - use eligibility-check instead; not for policy text - use policy-retrieve.
- ▌ Answer Draft · microsoft bundleDrafts the cited floor answer for the associate - or the shift-lead escalation when the payload is out of scope or below confidence - from the completed rtl.store-associate-assist.v1 payload, using the answer template. Use to close every assist run: "draft the floor answer", "write up the answer for the associate", "close out the assist run", "draft the escalation to the shift lead", "what can I tell the customer". Do NOT use for a new question with no resolved payload - use question-intake instead; not to compute eligibility - use policy-retrieve or promo-check; never send, post or execute anything - drafts only.
- ▌ Similar Work Rank · microsoft bundleComputes deterministic similarity and recurring-failure evidence from supplied history. Use for "rank similar past work", "have we repaired this before", "find the closest prior fix", or "explain similarity scores". Do NOT use for intake — use wo-intake instead; retrieval — use knowledge-retrieve instead; stock checks — use parts-readiness instead; terminal notes — use work-order-writeup instead. Local draft evidence only.
- ▌ Copilot Studio Adaptive Card Builder · microsoft bundleUse this skill whenever a user asks to create, generate, design, review, validate, lint, troubleshoot, or improve an Adaptive Card for Microsoft Copilot Studio standard-harness agents, including forms, confirmations, approvals, welcome prompts, status cards, handoff cards, input mappings, Action.Submit payloads, Power Fx card formulas, accessibility, host compatibility, or paste-ready card JSON. The skill may run in a skills-capable GitHub Copilot harness, but its generated package cannot render or be tested there because that harness does not support Adaptive Cards or topic nodes. Use it before claiming that Adaptive Card JSON is ready for a Copilot Studio node. Do not use it to claim that generative instructions dynamically render native cards.
- ▌ Failure Mode Rank · microsoft bundleRanks the likely failure modes for a fault against the failure-mode library, symptoms, alarm codes and repeat-failure history, deterministically. Use when the user says "what's the likely cause", "rank the failure modes", "diagnose this fault", "is this the real root cause?", or after history-retrieve completes. Do NOT use for intake — use fault-intake; history retrieval — use history-retrieve; priority — use criticality-rank; drafting — use work-order-update.
- ▌ Work Order Update · microsoft bundleDrafts the work-order update and recommended action from the triaged contract payload, with every determination cited to the manual, history and rules. Use when the user says "draft the work order", "write up the WO update", "what should we do", "recommend the fix", or after criticality-rank completes. Do NOT use for intake — use fault-intake; history retrieval — use history-retrieve; cause ranking — use failure-mode-rank; priority calculation — use criticality-rank.
- ▌ Knowledge Retrieve · microsoft bundleAttaches cited SOPs, manuals, prior fixes and usage evidence to draft inputs. Use for "retrieve the SOP", "find the manual section", "pull prior fixes", or "get parts history". Do NOT use for intake — use wo-intake instead; ranking — use similar-work-rank instead; stock checks — use parts-readiness instead; terminal notes — use work-order-writeup instead. No scheduling, orders or live write-back.
- ▌ Work Order Writeup · microsoft bundleRenders one fixed-layout cited Markdown work-order draft for technician/planner review. Use for "draft technician notes", "write up this work order", "give the planner summary", or "show the proposed next action". No audience-switching or document-conversion feature. Do NOT use for intake — use wo-intake; retrieval — use knowledge-retrieve; ranking — use similar-work-rank; stock checks — use parts-readiness. No CMMS write-back, closure, scheduling or purchasing, even when approved.
- ▌ Defect Grade · microsoft bundleRecommends manufacturing defect severity and disposition from validated engine deviations. Use for "grade the defects", "what disposition?", "how bad is it?", "can we ship it?", or "certificate says pass". Do NOT use for document intake — use spec-ingest; tolerance math — use tolerance-check; NCR writing — use ncr-draft. No release approval or operational actions.
- ▌ Case Packet · microsoft bundleDrafts the return case packet - determination, recommendation, evidence list, fraud signals, customer response draft, manager exception request - from the governed contract payload using the packet template. Use to close every return case: "build the case packet", "write up the return", "draft the customer response", "draft the manager exception request", "close the return case". Do NOT use to start a case - use return-intake instead; not for eligibility or red flags - use eligibility-check; not for incident or safety write-ups.
- ▌ Evidence Match · microsoft bundleFinds the specific chart notes, dates and verbatim quotes that back a prior-auth request and attaches them as citations. Use when the user says "where in the chart does it show the conservative therapy", "find the notes supporting this auth request", "cite the documentation for the MRI request", "pull the PT records for this order". Do NOT use to decide whether the payer's criteria are met - use criteria-extract instead; do NOT use to write the justification - use necessity-draft instead; do NOT use to list what is still missing - use gap-report instead; do NOT use to audit a completed encounter's documentation or coding - use the clinical-documentation-companion plugin instead.
- ▌ Create Copilot Adoption Dashboard · microsoft bundleTurns the four Microsoft admin center (MAC) Copilot activity exports into a populated, single-file HTML adoption dashboard using the Copilot Adoption Analysis framework (Pillars A–E and the KPI scorecard). Triggered by the `create-copilot-adoption-dashboard` command. Use when the user asks to "create a Copilot adoption dashboard", "populate the adoption dashboard template", "build my MAC report dashboard", "generate a Copilot usage dashboard", "turn my Copilot exports into a dashboard", or "make an adoption at-a-glance report". It first explains the process, then collects a company name (required) and logo (optional) plus the four CSV exports (Copilot usage, Agents per-user, Agents per-agent, Copilot Chat), computes the real metrics, and replaces every template placeholder with the customer's data. Do NOT use for a plain HTML page or a one-off chart with no MAC data — use the html or render-ui skill instead. Do NOT use to query a Power BI report — use the powerbi skill instead.
- ▌ Necessity Draft · microsoft bundleWrites the medical-necessity narrative that accompanies a pending prior-auth request, using only criteria the engine marked met and cited. Use when the user says "write the medical-necessity letter for this MRI request", "draft the clinical justification for the auth", "explain to the plan why this procedure is needed", "put together the necessity narrative". Do NOT use to list what is still missing or check packet readiness - use gap-report instead; do NOT use to decide whether the criteria are met - use criteria-extract instead; do NOT use to argue against a decision the payer has already made - use the denials-appeals-response plugin instead. Never writes approval, denial or clearance language.
- ▌ Return Intake · microsoft bundleStructures a customer return request - item, order/receipt, reason as stated, condition, serials, customer history - into the rtl.returns-refund-case.v1 contract as case.json. Use when the user says "customer wants to return", "process this return", "start a return case", "log this return", "new return at the desk", or a return case begins. Do NOT use for eligibility or refund decisions - use eligibility-check instead; not for policy text - use policy-retrieve; not for the write-up or customer response - use case-packet.
- ▌ Parts Readiness · microsoft bundleComputes cited stock sufficiency and replacement-part availability from supplied extracts. Use for "check parts readiness", "are the parts in stock", "is this part current", or "show stock shortages". Do NOT use for intake — use wo-intake instead; retrieval — use knowledge-retrieve instead; ranking — use similar-work-rank instead; terminal notes — use work-order-writeup instead. Never reserves, orders or schedules.
- ▌ Criteria Extract · microsoft bundleChecks a specific patient's pending prior-auth request against the payer's coverage-policy checklist, clause by clause, and reports which criteria the chart satisfies and which are still open. Use when the user says "does this patient meet Contoso's criteria for the procedure", "does this patient qualify for the MRI under the plan's policy", "run the auth criteria check on this order", "are we ready to request auth yet", "why would this request get pushed back". Do NOT use to look up which payer policy or clause governs a service - use policy-ingest instead; do NOT use to hunt through the chart for source notes - use evidence-match instead; do NOT use for coding or documentation gaps on a finished encounter - use the clinical-documentation-companion plugin instead. Never renders an approval or a denial.
- ▌ Tolerance Check · microsoft bundleComputes inspection deviation statistics using a local deterministic engine. Use for "check tolerances", "compare against spec", "any out-of-spec?", "bore exceedance", or "measurement band consumption". Do NOT use for document intake — use spec-ingest; grading — use defect-grade; NCR or review-report Markdown — use ncr-draft. This release does not produce DOCX/PDF or other report formats. No release decisions or operational actions.
- ▌ Promo Check · microsoft bundlePresents the promotion eligibility already computed by policy_resolve - the three-part test (window AND cluster AND SKU) with the failing leg and exact dates named. Use for "is this on promo", "does this customer get the deal", "is the discount still running", "why isn't the promo applying", "did the offer end". Do NOT use to resolve the clause or compute eligibility - use policy-retrieve instead (it populates promo_check); not for return or price-match questions - use policy-retrieve; not for product comparisons - use product-compare; not to draft the floor answer - use answer-draft.
- ▌ Template Based Document Generation · microsoft bundleFill a Word (.docx) template from structured data and return the finished document with its branding intact. Placeholders, blanks and content controls are replaced with values, optional sections are removed, and table rows repeat per input item. Use when the user supplies a .docx template plus data and asks to fill in, populate or complete it.
- ▌ Cowork Consumption Advisor · microsoft bundleTurns Microsoft 365 admin center Cost Management and Cowork usage exports (CSV) into an interactive Cowork & Work IQ consumption report: service breakdown (prepaid vs pay-as-you-go), spending-limit analysis per policy, group and user consumption, credits per task, forecasts, per-department and per-manager roll-ups (users enriched via Microsoft Graph), and evidence-backed recommendations. Use when the user runs "/analyze-cowork-consumption", says "build a consumption report from these files", "analyze our Cowork consumption", "how many Copilot Credits did we use", "Cowork spend by department or manager", or uploads Consumption > Users / Groups / Policies / Agents and services or Cowork usage exports. Do NOT use for Copilot licence adoption reporting (use the Copilot Adoption Dashboard skill), for Copilot Studio credits in Power Platform admin center, or to change spending policies.
- ▌ Agent Rai Impact Assessment · microsoft bundleUse this skill whenever the user asks for a Responsible AI (RAI) impact assessment, RAI review, harms or impact analysis, or pilot/release-readiness review of an AI agent, or to reassess an agent after material changes to its tools, data, memory, or users. Works from the agent's use case, design, tools, data flows, and evaluation evidence to identify affected people, benefits, harm scenarios, authority boundaries, mitigations, residual uncertainty, and the human decisions still required. Not a generic security audit, automatic compliance certification, or authority to approve deployment.
- ▌ Wo Intake · microsoft bundleExtracts cited work-order identity and asset context into draft inputs. Use for "intake this work order", "pull WO-4507", "extract the asset context", or "start the work-order packet". Do NOT use for evidence retrieval — use knowledge-retrieve instead; ranking — use similar-work-rank instead; stock checks — use parts-readiness instead; terminal notes — use work-order-writeup instead. Offline synthetic evidence only; no operational actions.
- ▌ Copilot Studio MCP Readiness · microsoft bundleUse this skill when someone wants to connect a Model Context Protocol (MCP) server to a Microsoft Copilot Studio agent, is reviewing an MCP server before a rollout, or is debugging why a tool never appears in the agent, why the input schema came back truncated, or why a connection fails. Trigger on requests like "can Copilot Studio use this MCP server", "why is this tool missing from my agent", "review my MCP server before I add it", or a pasted tools/list response, tool definition, or MCP connector OpenAPI file. Do NOT trigger for MCP servers targeted at coding agents such as VS Code or Visual Studio, which have a different constraint set.
- ▌ Gap Report · microsoft bundleAfter the criteria check has run, lists every piece of evidence still missing from a prior-auth packet and presents the packet as a draft for review. Use when the user says "what's still missing before we submit this auth", "what does the payer still need from us", "assemble the submission packet for review", "give me the outstanding items on this request". Do NOT use to check whether the patient meets the payer's criteria or why a request would be pushed back - use criteria-extract instead; do NOT use to locate documents in the chart - use evidence-match instead; do NOT use for general Word reports or documents - use docx instead; do NOT use on a claim the payer already denied - use the denials-appeals-response plugin instead. Never submits, files or uploads anything.
- ▌ Ncr Draft · microsoft bundleWrites a cited draft nonconformance report and inspection summary in Markdown (.md) from graded engine evidence. Use for "draft the NCR", "write up the nonconformance", "inspection summary please", "prepare the review report", or "draft supplier notification text". Do NOT use for intake — use spec-ingest; tolerance math — use tolerance-check; grading — use defect-grade; CAPA plans and DOCX/PDF conversion are outside this release. Never sends, files or executes actions.
- ▌ Semantic PDF Image Extractor · microsoft bundleExtract meaningful images, photos, diagrams, charts, maps, screenshots, illustrations, and visual evidence from uploaded PDFs with arbitrary layouts. Use when a user asks to extract, crop, classify, caption, deduplicate, inventory, or package images from PDF documents while preserving page context and source traceability.
- ▌ Stakeholder And Decision Map · microsoft bundleMines customer interactions to identify stakeholders, infer their likely roles and engagement, map the decision process, and highlight who or what may be missing. Use when asked to "map a deal's buying group", identify influential or missing stakeholders, "assess who has gone quiet", or "explain how the customer will decide". Do not use for phased engagement plans, contact sequences, choosing or drafting outreach to the single next contact, seller or team performance reviews, or contacting, scheduling, or changing records.
- ▌ Spec Ingest · microsoft bundleOrganizes cited inspection documents into engine-ready inputs without grading. Use for "load the inspection results", "read the part spec", "structure the lot documents", "intake inspection evidence", or "review lot documents". Do NOT use for deviation math — use tolerance-check; grading — use defect-grade; NCR writing — use ncr-draft. Never authorizes release or operational actions.
- ▌ Fault Intake · microsoft bundleReads maintenance fault notes, operator reports, alarm/event logs, asset IDs and location into the mfg.maintenance-triage.v1 contract inputs. Use when the user says "triage this fault", "work this breakdown", "read the fault note for <asset>", "what's wrong with pump <id>", or when a maintenance triage run begins. Do NOT use for history retrieval — use history-retrieve; cause ranking — use failure-mode-rank; priority — use criticality-rank; drafting — use work-order-update. Not employee-injury recordability.
- ▌ Power Platform Solution Compare · microsoft bundleUse this skill whenever the user asks to compare two Power Platform or Dataverse solution versions or exports, diff two solution .zip files or unpacked solution source folders, find what changed between releases, review a solution before import or promotion to another environment, produce release notes or a change log from solution packages, or check for breaking changes across tables, columns, relationships, choices, forms, views, apps, security roles, business rules, cloud and desktop flows, plug-ins, custom APIs, connection references, environment variables, web resources, and Copilot Studio agents. Also use when the user pastes a report produced by this skill's comparison script and wants it interpreted. Not for comparing live environments directly, reading solution checker results, inspecting managed layers in a live environment, running imports, or editing solutions.
- ▌ Policy Ingest · microsoft bundleFinds which payer coverage policy governs an ordered service and writes its exact clause key into the prior-auth packet. Use when the user says "which Contoso policy covers a lumbar MRI", "what are the payer's rules for this procedure", "look up the coverage policy before we request auth", "which clause applies to this order". Do NOT use to read the chart or gather notes - use evidence-match instead; do NOT use to judge whether this patient qualifies - use criteria-extract instead; do NOT use to write the necessity narrative - use necessity-draft instead; do NOT use to report outstanding items - use gap-report instead; do NOT use on a policy already applied to a denied claim - use the denials-appeals-response plugin instead. An unlisted service is handed on as out_of_scope, never matched to a near-miss clause.
- ▌ Phi Deidentifier · microsoft bundleUse this skill whenever the user asks to de-identify, redact, anonymise, scrub, or remove PHI/PII from clinical text, notes, transcripts, or documents before sharing, exporting, or using them for analytics, testing, or demos — e.g. "de-identify this note", "strip patient info", "make this HIPAA Safe Harbor compliant", "produce a limited data set". It removes the 18 HIPAA Safe Harbor identifiers and emits an audit manifest of what was removed. Run the bundled scripts/deidentify.py — do NOT hand-write redaction regexes yourself. This skill prepares de-identified text and an audit trail for human review; it does NOT certify legal compliance or make a formal expert determination.
- ▌ Study Flashcards · microsoft bundleUse this skill whenever the user provides source material (notes, slides, a document, a PDF, pasted text, or a web page) and asks to "create a guide based on this", make a study guide, make flashcards, turn it into a quiz, "quiz me on this", or otherwise study from that material. Produces source-grounded flashcards and a practice quiz, defaulting to an interactive HTML study app for "guide" requests unless the user asks for Word, PDF, printable, or plain text. Do NOT use for essay grading, open-ended tutoring, multi-week course design, or trivia quizzes with no source material.
- ▌ Knowledge Harvest · microsoft bundleHelps customer service representatives harvest reusable knowledge from a recently closed case or verified workaround, with a brief chat summary and one saved editable review artifact in CRM when supported, otherwise in Word or Markdown. Separates symptoms, cause, workaround, fix, and tested scope, removes identifying details, checks guidance overlap, and proposes knowledge updates and recurrence-prevention actions without publishing. Use when asked to "capture a verified fix", "draft a knowledge article", "update an article from resolution evidence", or assess whether there is enough evidence for reusable guidance. Do not use to answer a current customer's question, draft their reply, turn unresolved speculation into executable instructions, or publish automatically.
- ▌ Root Cause Analysis · microsoft bundleUse this skill whenever the user asks to diagnose why something failed, find the root cause of an incident, conduct a post-mortem, analyze a problem or defect, distinguish symptoms from causes, or apply 5 Whys or Fishbone analysis. Trigger on phrases like "why did this happen", "root cause", "post-mortem", "5 whys", "fishbone", "what caused this", "diagnose the failure", "why did it fail", "underlying cause". Do NOT trigger for general problem solving (use business-os), refining existing plans (use idea-refiner), or content quality audits (use content-quality-auditor).
- ▌ Competitive Strategy · microsoft bundleBuilds customer-specific competitive positioning with supported differentiators, honest tradeoffs, objection responses, and claims to avoid. Use when a customer use case needs supported competitive positioning, comparison, objection handling, or discovery hypotheses, such as "position against this competitor", "answer this competitive objection", "compare options for this customer", "which competitive claims are safe to use", "build a battlecard for this deal", or "how do we beat this competitor here". DO NOT use for business-case or ROI modeling, a full meeting brief, generic product pitches, or unsupported competitor claims.
- ▌ Draft Customer Reply · microsoft bundleDrafts a reviewable customer-facing support reply grounded in known facts, applicable policy, and the customer's actual needs. Use when a ticket, incident, issue, request, or complaint needs a reviewable customer-facing reply grounded in the known facts, applicable policy, customer need, and communication context. Triggers include "draft a reply," "respond to the customer," "write a status update," and requests to adjust tone, length, or language. Do not use to research an unresolved answer or to send automatically.
- ▌ Kql Grounded Queries · microsoft bundleUse whenever the user asks for a KQL query for Microsoft Sentinel, Log Analytics or Defender XDR Advanced Hunting — writing one, fixing one, modifying one, or explaining one — including requests that never say "KQL" (for example "query SigninLogs", "hunt for phishing URLs in Defender", "write a Sentinel detection"). Verify every table and column BEFORE composing any query — against Microsoft documentation, or against the tenant's own schema where the table is custom and Microsoft does not document it.
- ▌ Pipeline Prioritizer · microsoft bundleRanks a scoped set of open opportunities into an evidence-backed worklist of what to work next and why, with ties and unknowns where needed. Use when a scoped visible opportunity set needs a ranked or tied worklist explaining what deserves attention next and why, such as "which deals should I work today", "rank my open opportunities", or "prioritize this deal list". DO NOT use for change digests, meeting prep, or full team pipeline reviews.
- ▌ Sales Progress Update · microsoft bundleCreates or refreshes a sales progress update for a manager or team about work done, deal movement, pending outcomes, supported forecast position, and help needed. Use when asked to "create my weekly sales update", "refresh my sales progress deck", "report my forecast position", "where do I stand against my quarter forecast", or "catch my manager up on committed deals". Do NOT use for non-sales project updates, a since-date deal change digest, momentum or blocker analysis, meeting prep, or outreach drafting.
- ▌ Business Case Composer · microsoft bundleBuilds a customer-specific business-case draft connecting the problem, cost of inaction, proposed solution, investment, and supported value. Use when a customer-specific deal or initiative needs a decision-ready qualitative or quantitative business case, such as "draft a business case", "build the value case", or "justify this initiative". DO NOT use for generic product pitches or price and discount quotes.
- ▌ Case Preparation Brief · microsoft bundleBuilds a decision-ready brief on one support issue, covering status, material history, open commitments, and the recommended next step. Use before the next interaction or action on one case, incident, ticket, customer issue, request, or complaint — reconciling what's happened, what's still open, and what to do next, even from a single description or one substantive interaction with no full record yet. Examples include "brief me on this case", "prepare this case handoff", and "what is still open on this complaint". Do not use to rank several issues, compose the outbound customer reply, or close, reassign, or otherwise change the case.
- ▌ Cowork Plugin Engineer · microsoft bundleUse this skill whenever a user asks to create, import, repair, authenticate, package, validate, sideload, evaluate, upgrade, or troubleshoot a Microsoft Copilot Cowork plugin containing Agent Skills or remote Model Context Protocol (MCP) connectors.
- ▌ Post Meeting Follow Up · microsoft bundleTurns one completed sales meeting into an accurate summary of decisions and commitments, proposed next actions, and an optional customer follow-up draft. Use when one completed sales meeting or call needs accurate capture, proposed durable actions, and safe customer follow-up, such as "summarize this completed call", "capture meeting commitments", or "draft the meeting follow-up". DO NOT use for upcoming meeting prep, account-wide activity summaries, or lead re-engagement campaigns.
- ▌ Sharepoint File Creation · microsoft bundleSource/generate the requested file using whatever content rules apply to the use case, gate it against an evidence-based pre-upload size threshold using the filesystem API, and upload it to SharePoint via the Create file tool's confirmed /app/created/ path-reference mechanism — without ever streaming raw file bytes through the LLM. Use this skill whenever a request asks for a file to be produced and uploaded to SharePoint, whether or not the user specifies a path, filename, format, or content source.
- ▌ Case Triage · microsoft bundleRanks support issues into an explainable work order based on impact, deadlines, commitments, and evidenced urgency. Use when two or more tickets, incidents, issues, requests, or complaints need an explainable relative work order based on impact, deadlines, commitments, staleness, unanswered contact, documented urgency, and any available priority or response-time evidence. Also supports a bounded urgency assessment for one issue without inventing a queue rank. Examples include "rank these cases", "which complaint should be first", and "how urgent is this issue". Do not use for a deep brief on one selected issue or to claim work automatically.
- ▌ Deal Catchup · microsoft bundleSummarizes what changed and why across a scoped deal set, separating genuine customer movement from record housekeeping. Use to report what changed and why across a scoped set of deals since a stated baseline, such as "which deals slipped", "what moved on my top deals", or "what changed while I was out". Needs a defined scope and current deal evidence; a baseline improves the comparison, but a current-state result is available without one. DO NOT use for ranking what to work on next or a single deal's full standing review.
- ▌ Inbox Triage · microsoft bundleUse this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.
- ▌ Meeting Prep · microsoft bundlePrepares a seller for one upcoming customer conversation such as what to learn, say, prove, and ask, with an evidence-backed next move and a private editable brief. Use when asked to "prep my customer call", "brief me before my sales meeting", "prepare for this buyer demo", "plan my renewal conversation", or "build talking points for this opportunity meeting". Do NOT use for past-meeting recaps, broad account plans, pipeline audits, seller coaching, standalone pitch decks, or automatic outreach.
- ▌ Answer Research · microsoft bundleResearches a bounded, source-backed answer to a support, policy, eligibility, or troubleshooting question, with citations and explicit evidence gaps. Use when a support, policy, eligibility, informational, or troubleshooting question needs a bounded, source-backed investigation that reconciles authority, applicability, currency, contradictions, and source coverage. Triggers include "research this answer," "what does the guidance support," "reconcile these sources," and "does this customer appear eligible." Do not use merely to compose a reply after the answer is established.
- ▌ Qr Code Builder · microsoft bundleUse this skill whenever the user asks to "make a QR code", "create a QR code", "QR code for this link/website", "QR code with my logo", "branded QR code" or "Wi-Fi QR code". Guided walkthrough that builds a scannable QR code (PNG, SVG, PDF, JPG, WEBP) with a bundled Python script. Only the web address is required; body shapes, corner-eye styles, outer frames, brand colors, a logo and a caption are optional. Also makes Wi-Fi, contact card, email, SMS, phone, map, event and bulk codes on request. Do NOT use for reading, scanning or decoding an existing QR code, or for barcodes other than QR codes. A QR code with a logo is handled here, not by general image generation.
- ▌ Build And Test 2 · microsoftBuild the Wassette workspace and run its test suite with the just recipes — debug and release builds, example and test components, and the combined unit plus documentation tests. Use when compiling Wassette, building example components, or running and debugging tests.
- ▌ Rust Code Style · microsoftWrite idiomatic, well-structured Rust for Wassette — single-responsibility design, anyhow error handling, Arc/Mutex for shared state, and the required formatting and linting with cargo +nightly fmt, cargo clippy, and cargo machete. Use when adding or refactoring Rust code in this repository.
- ▌ Copyright Headers · microsoftEnsure every Rust (.rs) file in Wassette starts with the required Microsoft copyright header, using the idempotent scripts/copyright.sh helper. Use when adding new Rust files or when a copyright-header check fails.
- ▌ MCP Inspector Testing · microsoftValidate Wassette changes end-to-end by running the MCP server with just and driving it with the MCP Inspector CLI over Streamable HTTP — listing tools, resources, and prompts, and calling tools. Use before committing server changes or when debugging tool exposure and behavior.
- ▌ Pull Request 2 · microsoftWrite concise, focused pull request descriptions for Wassette — at most three sentences on the what and why, with an explicit note on any breaking public-API change and how users adapt. Use when opening or editing a Wassette pull request.
- ▌ Documentation 2 · microsoftBuild, serve, and write Wassette's mdBook documentation under docs/ — concise, code-first prose, the multi-version URL layout, and navigation in SUMMARY.md. Use when editing docs/ pages or previewing the documentation site.
- ▌ Build Research Paper · microsoft bundleCross-domain / Scientific writing and publication — Build beautifully-formatted, arxiv-ready research paper PDFs from a mix of hand-authored LaTeX and/or markdown + PNG figures, using `tectonic` (default) or `pandoc` (escape hatch). Captures the reusable pattern that research projects keep re-discovering: `report/main.tex` + `references.bib` + `generate_figures.py` + iterative feedback/response scaffolding, all buildable with a single command. WHEN: write a research paper, arxiv submission, prepub, generate PDF from markdown, LaTeX paper, build main.tex, journal manuscript, referee revision, response to referee, resubmission package, publication-quality figures, matplotlib publication style, tectonic build, pandoc build, generate arxiv-ready PDF, bibliography from BibTeX.
- ▌ Discovery Catalog · microsoft bundleInventory the contents of this Discovery catalog repo. Lists publishers, agents, starter-kits, and the tools shipped under each agent. Use this skill whenever the user asks what's in the catalog, who publishes what, what agents/tools/starter-kits exist, lists or counts of any of those, "show me the catalog", "do we have an agent for X", "what starter kits do we have", "list the publishers", "list tools per agent", or any inventory/discovery question about repo-resident assets — even if the user doesn't explicitly say the word "list".
- ▌
- ▌ Migrate Podman Containerfile · microsoftMigrate a Podman Containerfile to the canonical Dockerfile required by the Discovery catalog. Use when a PR fails POL-022, a tool contains Containerfile or Dockerfile.in, or a contributor asks to convert Podman build files for Docker. Creates the Dockerfile directly only when the migration is mechanically safe and refuses ambiguous preprocessing or multi-file builds.
- ▌ Discovery Services Agent Deployer · microsoft bundleDeploy Discovery catalog agents end-to-end with one command: discover the agent, build and bind its tool when present, skip tool stages for agents without tools, deploy the agent, and optionally run validation. Use this skill whenever the user asks to deploy a Discovery agent, publish or rebuild an agent tool image, register a Discovery tool from a repo Dockerfile/tool.yaml, resume a failed deployment, or produce a dry-run deployment plan for an agent in this catalog.
- ▌ Discovery Services Starter Kit Deployer · microsoft bundleDeploy Discovery catalog starter-kits end-to-end: validate kit.json agentRefs, build and deploy every referenced agent tool, deploy each referenced agent individually, and summarize deployed agents/tools plus customer-ready sample prompts. Use this skill whenever the user asks to deploy a Discovery starter-kit or deploy all agents listed in starter-kits/*/kit.json.
- ▌ Token Estimator Mvp · microsoft bundleEstimate AI planning ranges from a work description or explicitly authorized safe project context. Provides coarse class ranges or conditional planning bases without requiring token guesses.
- ▌ Migrate Webapi Selectall · microsoft bundleReviews and migrates deprecated wildcard (*) values in Power Pages Web API fields site settings to least-privilege explicit Dataverse columns. Use whenever a user mentions Web API wildcard or select-all remediation, fields settings containing *, data-exposure review, wildcard deprecation readiness, or Web API failures after wildcard retirement. Applies to both non-SPA sites using HTML, CSS, JavaScript, Liquid, and downloaded YAML, and SPA sites using React, Vue, Angular, Astro, or TypeScript. The agent must inspect every source Web API call and consumer, report exact fixes for every wildcard, report every already-explicit configuration, apply approved edits, and verify no wildcard remains.
- ▌ Analyze Drivers · microsoftUse when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.
- ▌ Analyze Objects · microsoftUse when analyzing interacting object types, object-centric processes, leading-object executions or cross-object delay.
- ▌ Compare Cohorts · microsoftUse when comparing process cohorts, departments, periods or before-and-after results under matched definitions.
- ▌ Telemetry 6 · microsoftEnable, disable, or check usage telemetry transmission for Power Apps Mobile Extension skills. Use for 'turn off telemetry', 'opt out', 'enable telemetry', or 'telemetry status'. Opt-out stops transmission only; local diagnostic logs continue when the plugin is enabled.
- ▌ Analyze Variants · microsoftUse when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.
- ▌ Analyze Performance 2 · microsoftUse when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.
- ▌ Investigate Process · microsoftUse when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.
- ▌ Edit Site · microsoft bundlePlans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in Design Studio. Use for requests involving pages, localized content, navigation, assets, snippets, site markers, Liquid/web templates, page layouts, or styling. Coordinated work produces an approved browser-viewable plan, executes changes in dependency order, verifies the local result, and optionally hands off to deployment. Not for React, Angular, Vue, or Astro SPA sites.
- ▌ Report Issue 7 · microsoft bundleUse this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the code-apps plugin to the GitHub repository.
- ▌ Telemetry 5 · microsoftUse this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-automate telemetry / usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".
- ▌ Setup 2 · microsoftUse when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.
- ▌ Generate MCP App UI · microsoftGenerate a single-file MCP App widget for an MCP tool, with either bundled runtime code or user-approved public CDN imports. Describe the visual and provide a plain structured payload or a full tool result with content, structuredContent, and meta.
- ▌ Add Localization · microsoft bundleAdds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.
- ▌ Migrate Bootstrap · microsoft bundleMigrates a non-SPA (classic) Power Pages site from Bootstrap 3 to Bootstrap 5. Downloads the site, runs the pac pages bootstrap-migrate engine, reviews the change report, applies AI-assisted fixes for the residual hierarchy/CSS changes the engine only flags, uploads the migrated site (which auto-enables the Bootstrap 5 runtime flag), verifies the flag, and validates. Use when the user wants to upgrade an older Bootstrap-3 portal to Bootstrap 5. NOT for SPA sites (React/Vue/Angular/Astro) — those are never Bootstrap-3.
- ▌ Setup App Insights · microsoftConfigure optional customer-owned Application Insights telemetry for a Power Apps mobile app — enable it against an existing Azure resource, change the resource, or disable it. Standalone, and invoked by /edit-app.