ops-team

Manages customer support, retention, hiring, onboarding, SOPs, and vendor operations for live ventures.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill ops-team-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-team
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/ops-team
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill ops-team-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Once a venture is live, it erodes from unanswered support tickets, unexplained churn, roles that never get filled, recurring operational mistakes, and degrading supplier relationships. This Skill turns that recurring operational work into structured processes a solo founder or small team can actually run. ## Core Features & Use Cases - Customer Support & Retention: Triages support situations with severity tiers and escalation rules, designs a three-layer support model (self-serve, automated first line, human escalation), and investigates churn using a four-bucket method with an exit-question script. - Hiring & Onboarding: Produces filtering job descriptions, structured interview plans with work samples and scorecards, reference-check scripts, and 30/60/90 onboarding plans, with hand-offs to legal and security teams. - SOPs & Vendor Operations: Writes one-page SOPs with automatable-step tagging, scores suppliers on a quarterly scorecard, flags single-supplier risk, and runs weekly ops reviews. - Use Case: A customer is furious about a late delivery. Use /support to triage severity, draft a specific reply with a kept timeline, log the root cause, and decide whether the recurring delivery issue needs a SOP or a supplier conversation. ## Quick Start Ask the assistant to handle an upset customer complaint using the ops-team support workflow and produce a reply plus triage note.

Frequently Asked Questions about ops-team

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

FAQPage Schema
How do I handle an angry customer complaint as a solo founder?

Use the /support command to triage severity, draft a reply that acknowledges the specific problem with a concrete next step and timeline, and write an internal triage note. Anything involving money, health, safety, or anger escalates to a human immediately rather than automation.

How do I investigate why customers are churning?

Use /retain to sort churned customers into four buckets: payment failure, never activated, faded, or frustrated, using billing and usage data first. Then send a short exit question on their usual channel and log verbatim answers; never invent a churn reason.

How do I write a job description that attracts the right candidates?

The /hire command produces a job description structured as a filter: concrete tasks, a 90-day outcomes section, three to five testable must-haves, stated pay range, and one role-specific application task. It also covers sourcing channels, structured interviews, and scorecards.

When should I write a SOP for a recurring process?

Write a SOP when the same thing has gone wrong twice, before a high-stakes first-time event, when handing a task to someone else, or when a task depends on someone remembering it. Avoid SOPs for one-off tasks; an unused SOP is worse than none.

What are the limits of automated customer support?

Automation handles only routine categories with stable correct answers and must never see full payment details, issue refunds, or promise unverifiable delivery dates. Money, health, safety, angry customers, and repeat contacts always escalate to a human with a response-time commitment.