it-operations-reporting

Generates evidence-based IT operational digests, SLA reports, and service reviews from ticket and monitoring data.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill it-operations-reporting-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-operations-reporting
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/it-operations-cowork/skills/it-operations-reporting
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill it-operations-reporting-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? IT operations teams spend hours manually compiling incident, change, SLA, and security data into status reports, often producing stale numbers, hidden exceptions, or metrics that disagree with source systems. This Skill turns current operational records into decision-ready reporting with clear priorities, owners, and data-quality caveats. ## Core Features & Use Cases - Priority Digests: Leads with active P1/P2 incidents, SLA breaches due soon, pending change approvals, and unowned work, each with owner, next action, and due condition. - Core Metrics: Calculates incident volume, MTTR, SLA compliance, change success rates, vulnerability aging, and asset/license coverage using defined denominators and business calendars. - Data Integrity Guardrails: Records extraction time and source coverage, reconciles counts against source totals, and separates observed facts from forecasts. - Use Case: An IT manager needs a Monday morning operations briefing. The Skill queries ticket, monitoring, and change systems, then produces an executive green/amber/red summary with immediate actions, queue exceptions, and coverage gaps. ## Quick Start Generate a weekly IT operations report for last week covering incidents, SLA compliance, changes, and security exceptions, with an executive summary and prioritized action list.

Frequently Asked Questions about it-operations-reporting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a weekly IT operations report?▼

Provide the reporting period, audience, in-scope services, and access to ticket, monitoring, and change data. The Skill extracts records, calculates SLA and incident metrics, and returns a prioritized digest with executive status, exceptions, and action items.

What metrics does an IT service review report include?▼

Typical metrics include incident volume by priority, mean and median time to acknowledge and resolve, SLA compliance, change success and rollback rates, vulnerability aging, and asset or license coverage. Metrics are only calculated when definitions and data support them.

Can I generate IT reports without live system access?▼

Yes, the Skill works with user-provided or authorized exported data when real-time tools are unavailable. It preserves data dates and marks any scope that cannot be verified in real time as a coverage caveat.

Why does my SLA metric disagree with the ITSM tool?▼

Discrepancies usually come from differing business calendars, pause conditions, or SLA definitions. The Skill reconciles by using the configured calendar and pause rules, then documents the definition used so results match the source system.

How are duplicate or parent-child incidents handled in reporting?▼

Records are deduplicated only through explicit linkage or stable identifiers, preserving potentially distinct records. Parent-child incident linkage is reported explicitly to avoid double-counting business impact.