Operations
Optimize business operations — vendor management, process documentation, change management, capacity planning, and compliance tracking. Keep your organization running efficiently.
9 skills · version 1.3.0
Install
hrida-agent-sdk plugin install operations@knowledge-work-skillsOr, inside a session: /plugin install operations@knowledge-work-skills. See Installation for scopes and updates.
Connectors
Skills work on their own with files you share, and get more useful when these tools are connected (configured in the plugin's .mcp.json):
Slack, Google Calendar, Gmail, Notion, Atlassian, Asana.
Skills
| Skill | What it does | Use case | How to use |
|---|---|---|---|
| capacity-plan | Plan resource capacity — workload analysis and utilization forecasting. | When heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have. | /operations:capacity-plan <team or project scope> |
| change-request | Create a change management request with impact analysis and rollback plan. | When proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout. | /operations:change-request <change description> |
| compliance-tracking | Track compliance requirements and audit readiness. | Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities. | /operations:compliance-tracking |
| process-doc | Document a business process — flowcharts, RACI, and SOPs. | When formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done. | /operations:process-doc <process name or description> |
| process-optimization | Analyze and improve business processes. | Trigger with "this process is slow", "how can we improve", "streamline this workflow", "too many steps", "bottleneck", or when the user describes an inefficient process they want to fix. | /operations:process-optimization |
| risk-assessment | Identify, assess, and mitigate operational risks. | Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision. | /operations:risk-assessment |
| runbook | Create or update an operational runbook for a recurring task or procedure. | When documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong. | /operations:runbook <process or task name> |
| status-report | Generate a status report with KPIs, risks, and action items. | When writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative. | /operations:status-report [weekly | monthly | quarterly] [project or team] |
| vendor-review | Evaluate a vendor — cost analysis, risk assessment, and recommendation. | When reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off. | /operations:vendor-review <vendor name or proposal> |
Example
Ask in plain language and the right skill loads automatically, or call one directly:
/operations:capacity-plan <team or project scope>