it-operations-coordinator

Routes cross-domain IT operations requests to specialist workflows with evidence tracking and approval controls.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous or cross-domain IT operations requests often lack a clear owner, verified evidence, or a safe execution path. This Skill acts as the front door for enterprise IT operations, converting vague requests into classified, prioritized, evidence-backed workflows with a single action register. ## Core Features & Use Cases - Cross-domain routing: Classifies requests and routes them to the right specialist workflow, covering identity, endpoint, Microsoft 365, network, cloud, security, backup, vendors, and change management. - Evidence discipline: Labels every fact as Observed, Reported, Inferred, or Unknown, and never fabricates ticket IDs, users, or completion claims. - Safety-tiered execution: Distinguishes read, draft, controlled write, high-impact, and destructive actions, requiring explicit approval and post-change verification for risky operations. - Use Case: When several users cannot access Teams and one laptop shows security warnings, the Skill classifies it as a cross-domain incident, checks service health and device alerts, routes work to M365 operations and security response, and maintains one action register with a stakeholder checkpoint. ## Quick Start Ask the assistant to review a cross-domain IT operations issue, such as an outage spanning identity, endpoint, and Microsoft 365, and produce a prioritized action plan with evidence status and owners.

Frequently Asked Questions about it-operations-coordinator

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

FAQPage Schema
How do I coordinate an IT incident that spans multiple teams?▼

Classify the request by urgency and affected domains, gather the smallest read-only evidence set, then route each workstream to the owning specialist workflow. Maintain one action register with owner, priority, approval state, and verification method for every action.

What should IT operations do first when a request has no clear owner?▼

Start with read-only inventory and impact discovery to identify the affected service, users, and business impact. Use the evidence to classify the work as incident, request, problem, change, or security event before assigning an owner.

When should I use this coordinator instead of a specialist IT skill?▼

Use it when a request spans two or more IT domains, lacks a clear service or owner, or needs prioritization across teams. If a narrow request maps directly to one specialist skill, go there directly instead.

Can IT operations automation execute high-impact actions like disabling accounts?▼

High-impact actions such as disabling accounts, revoking sessions, or isolating devices require explicit scope and approval, plus post-action verification. Destructive actions like wiping devices or deleting tenant data are never inferred from ambiguous requests.

What happens when no administrative tool access is available?▼

The Skill records the exact missing capability and provides the safest manual verification path instead of simulating results. It can still produce analysis and drafts from user-provided or authorized exported data, clearly marking unverified items.