Customer operations: Korean support tickets triaged with incidents spotted across them, status updates that say what is affected and when the next update comes, read-only runbooks for on-call, and blameless postmortems with a sourced timeline and owned actions.
Plugin operations-cs from marketplace modootoday in modootoday/marketplace. Commands read from the repo's manifest — 23 days ago.
cs-ticket-triage-koTriage Korean customer support tickets - classify by type and urgency, pull out the facts needed to act (account, order, error, time), detect duplicates and incidents across tickets, route to the right owner, and draft a polite reply in haeyo-che that promises only what the product does. Use when so
incident-postmortemRun a blameless incident postmortem end to end - a UTC timeline built from logs and messages, impact in numbers, the root cause and contributing factors traced past "human error", and action items with owners, dates and a way to verify each - and publish it. Use when the user asks for a postmortem,
operator-runbookWrite a read-only operator runbook that someone on call can follow - a trigger, the checks in order with the exact command or dashboard and what a healthy result looks like, the decision each result leads to, when to escalate and to whom, and nothing that changes state without an explicit, separate
ops-answer-groundingAnswer a customer question or take a confirmation from knowledge-base and reservation data without ignoring current deadlines, temporary notices or handoff conditions - cite the source, let an unexpired notice override the standing answer, escalate exceptions, and read numbers back digit by digit. U
status-incident-commsWrite status page and customer updates during an incident - what is affected in user terms, what users can do now, when the next update comes, no guessed causes or deadlines - and the closing note when it is resolved. Use when posting or drafting an incident update, a status page notice or a mainten
version-pinned-procedure-from-vendor-docsWrite an admin procedure for a named product and exact version only from the vendor documentation supplied - record the product, version and doc version for every step, prefer release notes over older guides where commands changed, mark each step "documented" or "not in the supplied docs" instead of
Your own Naver blog, Place, Smart Store, shopping, search ad and news comment data read through the datalab.tools browser extension, plus card news, short-form video, tutorial posts and social copy built in its editors, with no invented numbers and no change made without asking.
31 skills
Numbers that mean what they say: ClickHouse SQL that reads the key and deduplicates correctly, Naver trend data read as ratios, metrics defined once, experiments designed before launch, retention read by cohort, and open survey responses grouped with every response id kept.
16 skills
Reading passages that hit a measured grade level, language drills, and teacher-side checks for coverage, answer keys, lesson timing, study calendars and rule-valid puzzles, with the numbers and logs shown.
14 skills
Growth and community work: store listings written for the people searching that store, Discord servers run with structure and consistent moderation, newsletters readers open and finish, a month of social posts a small team can ship, launch emails that lead with what changed, and sites submitted to Google, Naver and IndexNow engines from a pipeline.
13 skills
Early product-planning steps done carefully: spar on an idea, frame the problem behind a request, synthesize feedback without overstating it, rank a backlog while saying where the ranking is fragile, write a Korean PRD with testable acceptance criteria, and put a decision on one page with the recommendation first.
13 skills
Korean content that reads well and stays true: product copy fixed to the Toss writing principles, Naver blog posts planned for search, persona tone measured with markers, and ghostwriting that never invents the author's facts.
11 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.