菜单
Generates an HTML report identifying repeat ServiceNow incidents that are NOT yet covered by a knowledge base article, ranked by reduction opportunity. Use when the user asks for a "knowledge gap report", "self-service opportunity analysis", "deflection candidates", "shift-left report", or "where should we write KB articles next".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Creates procurement leadership assets from Coupa data, especially supplier performance PowerPoint decks, category manager briefs, IT hardware order reviews, demand risk summaries, and ServiceNow-to-Coupa flow analysis. Use when the user asks to "create a supplier performance deck", "prepare a procurement review", "show category manager insights", "make a Coupa PowerPoint", "brief LSEG procurement", "analyze IT hardware suppliers", "review open hardware orders", or "turn Coupa data into an executive presentation".
Builds an HTML backlog-grooming report: stale issues, unestimated items, items missing acceptance criteria, oldest items, items with vague titles, and a recommended grooming shortlist for the next refinement session. Use when the user asks for a "backlog grooming report", "refinement prep", "backlog hygiene report", "grooming dashboard", or "backlog health check".
Builds a daily HTML "Standup Brief" dashboard for an engineering manager or scrum master: what each team member is working on today, blockers, sprint burndown, items at risk of slipping the sprint, and a "for your standup" markdown summary above the dashboard. Designed to be scheduled before the daily standup. Use when the user asks for a "standup brief", "daily delivery brief", "team standup dashboard", "scrum standup pack", or "what's my team doing today".
Creates a PowerPoint release-readiness pack for a Jira fix-version: scope summary, completion % by epic, open blockers, items at risk of missing the release, dependencies across teams, and go/no-go recommendation criteria. Use when the user asks for a "release readiness pack", "release deck", "fix-version readiness", "go/no-go deck", or "release status pack".
Creates a PowerPoint pack for a sprint review or retrospective covering scope changes, burndown, velocity vs prior sprints, completed vs committed, blockers timeline, and per-engineer contribution, using Jira data. Use when the user asks for a "sprint health deck", "sprint review pack", "retrospective deck", "end-of-sprint deck", or "velocity deck".
Builds an Adaptive Card 1.5 for posting a weekly engineering-delivery update into a Microsoft Teams channel: sprint progress, completed and shipped this week, blockers, ask-of-the-business, and what's next. Public-information only. Use when the user asks for a "weekly delivery update card", "engineering update card", "ship-it card", or "post our team update to Teams".
| name | knowledge-gap-report |
| description | Generates an HTML report identifying repeat ServiceNow incidents that are NOT yet covered by a knowledge base article, ranked by reduction opportunity. Use when the user asks for a "knowledge gap report", "self-service opportunity analysis", "deflection candidates", "shift-left report", or "where should we write KB articles next". |
| license | MIT |
| compatibility | Copilot Cowork Frontier with the ServiceNow MCP connector in this package. |
| metadata | {"author":"ESS MCP Demo","version":"1.0.0","demo-audience":"Knowledge Manager / Service Desk Lead"} |
| cowork.category | IT Operations |
| cowork.icon | BookOpenFilled |
Builds a shift-left analysis: which clusters of repeat incidents currently have no published KB article the agent could have used, and which would deliver the largest deflection if a KB were written. Renders as a printable HTML report.
list_incidents (last 30 days, paged)search_knowledge (per cluster keyword)get_knowledge_article (only when needed for verification)search_knowledge with the cluster keywords. If zero published
articles match, mark the cluster as a gap.incident_count × avg_resolution_minutes / 60. Higher is more valuable.<!doctype html>
<html lang="en"><head><meta charset="utf-8">
<title>Knowledge Gap Report — {{date}}</title>
<style>
body { font-family:-apple-system,"Segoe UI",system-ui,sans-serif; color:#1F2328; margin:0; background:#F6F8FA; }
.wrap { max-width:1100px; margin:0 auto; padding:24px; }
h1 { margin:0 0 4px; font-size:22px; }
.sub { color:#656D76; font-size:13px; margin-bottom:18px; }
.gap-grid { display:grid; grid-template-columns:repeat(2,1fr); gap:12px; margin-bottom:20px; }
.gap { background:white; border:1px solid #D0D7DE; border-left:4px solid #62D84E; border-radius:10px; padding:14px 16px; }
.gap h3 { margin:0 0 6px; font-size:15px; }
.gap .meta { color:#656D76; font-size:12px; margin-bottom:8px; }
.gap .why { font-size:13px; }
table { width:100%; border-collapse:collapse; font-size:13px; background:white; border:1px solid #D0D7DE; border-radius:10px; overflow:hidden; }
th, td { text-align:left; padding:8px 10px; border-bottom:1px solid #D0D7DE; }
th { background:#F6F8FA; color:#656D76; font-weight:500; }
.score { font-weight:600; }
</style></head>
<body><div class="wrap">
<h1>Knowledge Gap Report</h1>
<div class="sub">{{from}} → {{to}} · {{total_incidents}} incidents reviewed · {{cluster_count}} clusters · {{gap_count}} gaps</div>
<h2 style="font-size:14px;text-transform:uppercase;color:#656D76;letter-spacing:.04em;">Top deflection opportunities</h2>
<div class="gap-grid">
{{cards_top_gaps}}
</div>
<h2 style="font-size:14px;text-transform:uppercase;color:#656D76;letter-spacing:.04em;">All gaps</h2>
<table><thead><tr>
<th>Cluster</th><th>Incidents</th><th>Avg resolve (min)</th><th>Top assignment group</th><th class="score">Score</th>
</tr></thead><tbody>{{rows_all_gaps}}</tbody></table>
</div></body></html>
Each card uses this snippet for cards_top_gaps:
<div class="gap">
<h3>{{cluster_title}}</h3>
<div class="meta">{{incident_count}} incidents · avg {{avg_resolve_min}} min · top group {{top_group}}</div>
<div class="why">Sample incidents: {{sample_inc_numbers}}. Suggested KB title: <em>{{suggested_kb_title}}</em>.</div>
</div>
search_knowledge returned zero published articles whose title or topic overlaps
with the cluster keywords.Analytical, knowledge-management voice. Frame outputs as opportunities, not failings.