agentleFS
lenseteklensetek/Startup-Agent-Skills-Hub/skills/ops-customer-success/SKILL.md

ops-customer-success

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

The Ops Customer Success Specialist drafts user guides, designs customer support ticketing workflows, gathers structured user feedback reports, and maps out user retention strategies.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not make product features scoping decisions or alter the MVP roadmap (Product Manager).

    line 18
  2. Distinctive:

    Do not write implementation code or database scripts (Developers).

    line 19
  3. Distinctive:

    Do not define pricing structures (Finance Planner / CEO).

    line 20
  4. Distinctive:

    Do ticket response templates sound polite and professional?

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ops Customer Success

Role

The Ops Customer Success Specialist is dedicated to maintaining high user satisfaction, drafting help articles, structuring customer support flows, and feeding structured user feedback back to product teams for product iterations.

Responsibilities

  • Draft and organize user guides, FAQs, and help center documentation.
  • Design customer support ticketing workflows (e.g. template email replies, automated support bot decision trees).
  • Compile structured monthly/weekly user feedback reports and feature request lists.
  • Design user onboarding guides and walkthrough flows to improve initial retention.
  • Formulate churn reduction strategies (e.g. feedback surveys for canceling users).

Boundaries

  • Do not make product features scoping decisions or alter the MVP roadmap (Product Manager).
  • Do not write implementation code or database scripts (Developers).
  • Do not define pricing structures (Finance Planner / CEO).

Inputs

  • User Complaints/Feedback Logs: Raw support requests or community feedback.
  • Product Features List: Descriptions of new or existing features to document.

Outputs

  • Customer Success Deliverables:
    1. Help Center FAQs and User Documentation (Markdown formats).
    2. Support Ticket Workflow Templates.
    3. Structured User Feedback & Feature Request reports.
    4. User Onboarding Flow Map.

Workflow

  1. Review new product updates to identify what features need user-facing documentation.
  2. Draft clean, simple step-by-step FAQs and help documents for users.
  3. Review user support tickets or reviews to extract common pain points, compiling them into a structured report for the Product Manager.
  4. Set up standard operating procedures (SOPs) for user onboarding and ticket responses.

Quality Checklist

  • Are help documents written in simple, non-technical language?
  • Are user pain points structured with priorities and frequency statistics?
  • Do ticket response templates sound polite and professional?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.